- Coming up,
I will introduce you to Multi-Geo capabilities
in Office 365 SharePoint Online,
now generally available.
This allows you to configure
where SharePoint's site data is stored
and where individual users' OneDrive files reside.
And if you're already using Office 365 Multi-Geo,
I will show you how to do content moves
and point you to some updates along the way.
Multi-Geo in Office 365 is all about
controlling data residency in regions
or countries of your choice.
In SharePoint on-premises Multi-Geo deployments
typically setting up sharing, search, taxonomy
and profile services,
is an extensive and resource-intensive undertaking.
To solve this, you may have set up separate data centers
to meet your local data residency needs,
which results in data silos and limited collaboration.
With Office 365 Multi-Geo capabilities
for SharePoint Online,
we help you work as one organization
with simple setup and management of where your data resides,
while controlling how your data is shared and searched.
In the last Mechanics episode,
I showed you how easy it is,
to extend your Office 365 tenant to Multi-Geo
for OneDrive and Mailbox experiences.
Today, we look at how easy it is
to set up Multi-Geo capabilities for SharePoint Online
in the satellite locations you care about.
Since March 27, 2019,
any new satellite locations that you create
will have SharePoint capabilities enabled by default.
Here I am in a Multi-Geo tenant,
in the SharePoint Admin Center.
As you can see in this global map,
this Multi-Geo tenant is already extended
to North America,
Canada,
Europe,
Japan,
and Australia.
Let's say, for example, my business needs have evolved.
And we need a subsidiary in France.
I can add a Geo location for France
by simply clicking Add location.
Select France.
Next in the domain field,
I have chosen our company name.
Followed by an abbreviation of the satellite location name:
ContosoEnergyFRA.
This will be the SharePoint root URL
for my new Geo
and all sites created in France
will land under this root URL.
One caveat here:
If you have satellite locations set up
before March 27, 2019,
you will need to use the SharePoint Powershell cmdlet
'Set-SPOMultiGeoExperience'
to enable SharePoint capabilities, in those Geo locations.
Optionally, if you want to confirm the success of the setup,
you can follow up
by using the 'Get-SPOMultiGeoExperience' cmdlet.
Now, let's dive into some of the typical
SharePoint administration activities.
First off,
each Geo has it's own SharePoint Administration Center.
Here I am in the European satellite location.
I have all the controls
of my Central SharePoint Admin Center,
but scoped to my location in Europe.
If I click on the Sharing settings,
I can also set policies for sites
and users' OneDrives in Europe.
One thing to note here.
For internal sharing, by default,
sharing with everyone is disabled,
as it creates a potential for data oversharing.
For external sharing, you can configure
specific external partner domains per Geo.
For example,
by going to Advanced Settings for External Sharing,
I can add a domain.
In this case,
fabrikamwindmills.com,
and establish that as the only allowed external domain
for Europe.
It's that simple.
Now, let us switch gears and take a look at
how to manage Taxonomy.
Here I am in my Central Admin Center in the U.S.
And I have navigated to the Taxonomy Term Store.
This is the place
where I can manage enterprise-wide taxonomy beta data.
Any terms that I apply here,
will trickle down to all my satellite locations.
And notice,
no customizations are required.
Like Taxonomy,
search configuration requires no customizations.
When users search for content,
so long as they have permissions,
it's now a lot easier
to serve up search results from across the Geos.
Here I am logged in as Adriana,
an European user in the SharePoint Home experience
which is the single place for all things SharePoint sites
in the organization.
I will search for the term 'energy.'
As you can see, in the search results,
Files, Sites, People and News,
from across the Geos, in my enterprise, are shown.
And you can see that the search results are served up
based on the content relevance,
regardless of where the content resides.
Notice too,
that the URL for this SharePoint Home experience
is served from Europe location,
which is where I am located.
Your search indexes along with your content still reside
where they need to, at the Geo level.
But, the content is more discoverable now.
Now, let me switch gears,
showing what happens when you create a new site.
I'm going to click, 'Create site.'
Select Team site template.
And pick a name.
Here Solar Panels in Europe.
And you notice that because I'm in Europe,
this site will be located in Europe
and subject to European policies.
To take it one step further,
I can make any site powered off my hub site,
which resides in North America,
using the standard hub site association process.
By doing so,
I also get a unified search experience
across all the sites connected to this hub,
regardless of where a given site may reside.
I can see the results and view the content
that I have permission to.
It just works.
Lastly, let's look at the sharing experience.
I'm going to share a document with Bob,
who is an external partner from Fabrikam Windmills,
which is one of the domains that we allowed earlier.
I will click Send.
And you can see,
it just went through without any issues.
Now, let's try to share the same document
with a user from an unauthorized domain.
You will see I am stopped.
Which is a result of the sharing policy
that was set for European content.
One more thing I want to show you,
is what happens when a site moves to a different Geo.
For example, from Europe to the U.S.
Bob received this email prior to a site move.
If I hover over CarbonGlass, the site name,
the link points to a site in Europe.
But the site has already been moved to the U.S.
So let's see what happens when I click on the link.
You will see that the link persists
and if you look at the address bar,
you will see that the link
redirects to the site's new location in the U.S.
As an admin,
triggering a site move is pretty straightforward too.
As a global admin,
I can use the new SharePoint Powershell module
and the new cmdlet 'Start-SPOSiteContentMove'
specifying the sole site URL
and the destination data location parameters
to trigger the site move.
Optionally, if you want to schedule the move,
at a specific time such as the weekend,
then you can add the additional parameter,
PreferredMoveBeginDate.
It's that simple.
Now, even if a syncline has been set up
for this site content,
it will automatically get relinked to the new location.
No user action is required.
And Bookmarks and Favorite Links will persist.
And a few more things I want to point out.
First, all Multi-Geo activities are logged and audited
for future review.
Second, you can review and manage all security settings
in the Security Center,
and compliance policies in the Compliance Center.
Third, eDiscovery management can be done on a per-Geo basis.
And lastly, coder for SharePoint sites
is managed automatically
as the global control across our entire tenant.
And you can also set a specific code on limits per Geo.
So, that was a quick walkthrough of
the Multi-Geo capabilities in SharePoint Online.
SharePoint Online and Groups Multi-Geo
is generally available now.
To learn more,
check out the link shown
and contact your Microsoft accounting.
Thanks for watching.