管理多地理位置环境Administering a multi-geo environment

下文描述了 Microsoft 365 服务在多地理位置环境中的工作方式。Here's a look at how Microsoft 365 services work in a multi-geo environment.

可以从 Microsoft 365 审核日志搜索页中找到所有附属位置的统一审核日志A unified Audit log for all your satellite locations is available from the Microsoft 365 audit log search page. 你可以查看跨地理位置的所有审核日志条目,例如,NAM 和 EUR 用户的活动将显示在一个组织视图中,然后你可以应用现有筛选器,查看特定用户的活动。You can see all the audit log entries from across geo locations, for example, NAM & EUR users' activities will show up in one org view and then you can apply existing filters to see specific user's activities.

BCS、安全存储、应用BCS, Secure Store, Apps

BCS、安全存储和应用在每个附属位置都具有单独的实例,因此,SharePoint Online 管理员应从每个附属位置单独管理和配置这些服务。BCS, Secure Store, and Apps all have separate instances in each satellite location, therefore the SharePoint Online administrator should manage and configure these services separately from each satellite location.

电子数据展示eDiscovery

默认情况下,电子数据展示管理员或多地理位置租户的管理员将只能在该租户的中心位置执行电子数据展示。By default, an eDiscovery Manager or Administrator of a multi-geo tenant will be able to conduct eDiscovery only in the central location of that tenant. Office 365 全局管理员必须分配电子数据展示管理者权限,以允许其他人员执行电子数据展示,并在其适用的合规性安全筛选器中分配“Region”参数,以便将要进行电子数据展示的区域指定为附属位置,否则,不会对该附属位置执行任何电子数据展示。The Office 365 global administrator must assign eDiscovery Manager permissions to allow others to perform eDiscovery and assign a "Region" parameter in their applicable Compliance Security Filter to specify the region for conducting eDiscovery as satellite location, otherwise no eDiscovery will be carried out for the satellite location. 若要针对区域配置合规性安全筛选器,请参阅配置 Office 365 多地理位置电子数据展示To configure the Compliance Security Filter for a Region, see Configure Office 365 Multi-Geo eDiscovery.

Exchange 邮箱Exchange mailboxes

如果更改了用户的 PDL,则会自动转移用户的 Exchange 邮箱。Users' Exchange mailboxes are moved automatically if their PDL is changed. 创建新邮箱时,如果没有为用户的 PDL 设置值,则会将新邮箱预配到用户的 PDL 或中心位置。When a new mailbox is created, it is provisioned to the user's PDL or to the central location if no value has been set for the user's PDL.

信息保护 (IP) 数据丢失防护 (DLP) 策略Information Protection (IP) Data Loss Prevention (DLP) Policy

可以在“安全性和合规性”中心内为 OneDrive for Business、SharePoint 和 Exchange 设置 IP DLP 策略,并根据需要将策略的适用范围设置为整个租户或适用的用户。You can set your IP DLP policies for OneDrive for Business, SharePoint, and Exchange in the Security and Compliance center, scoping policies as needed to the whole tenant or to applicable users. 例如:如果你希望为附属位置中的某个用户选择策略,请选择将策略应用于特定 OneDrive,并输入用户的 OneDrive url。For example: If you wish to select a policy for a user in a satellite location, select to apply the policy to a specific OneDrive and enter the user's OneDrive url. 有关创建 DLP 的一般指南,请参阅数据丢失防护策略概述See Overview of data loss prevention policies for general guidance in creating DLP policies.

DLP 策略将基于每个地理位置的适用性自动同步。The DLP policies are automatically synchronized based on their applicability to each geo location.

在 UI 中,无法为地理位置中的所有用户实施信息保护和数据丢失防护策略,你必须为策略选择适用的帐户,或将策略全局应用于所有帐户。Implementing Information Protection and Data Loss prevention policies to all users in a geo location is not an option available in the UI, instead you must select the applicable accounts for the policy or apply the policy globally to all accounts.

Microsoft FlowMicrosoft Flow

为附属位置创建的流程将使用位于租户的默认地理位置中的终结点。Flows created for the satellite location will use the end point located in the default geo location for the tenant. Microsoft Flow 不是多地理位置服务。Microsoft Flow is not a Multi-Geo service.

Microsoft PowerAppsMicrosoft PowerApps

为附属位置创建的 PowerApp 将使用位于租户的中心位置中的终结点。PowerApps created for the satellite location will use the end point located in the central location for the tenant. Microsoft PowerApps 不是多地理位置服务。Microsoft PowerApps is not a Multi-Geo service.

OneDrive 管理员体验OneDrive Administrator Experience

OneDrive 管理中心的左侧导航栏中有一个“地理位置”选项卡,其中包含地理位置地图,你可在其中查看和管理地理位置。使用此页面可添加或删除租户的地理位置。The OneDrive admin center has a Geo locations tab in the left navigation which features a geo locations map where you can view and manage your geo locations. Use this page to add or delete geo locations for your tenant.

安全与合规管理中心Security and Compliance Admin Center

还有一个多地理位置租户的中央合规中心:Microsoft 365 安全与合规中心There is one central compliance center for a multi-geo tenant: Microsoft 365 Security & Compliance Center.

SharePoint 存储配额SharePoint storage quota

默认情况下,多地理位置环境中的所有地理位置具有相同的可用租户存储配额。By default, all geo locations of a multi-geo environment share the available tenant storage quota. 也可通过为特定地理位置分配特定配额来管理存储配额。You can also manage the storage quota by allocating a specific quota for a particular geo location. 有关详细信息,请参阅 多地理位置环境中的 SharePoint 存储配额For more information, see SharePoint storage quotas in multi-geo environments.

共享Sharing

管理员可以为他们的每个位置设置和管理共享策略。Administrators can set and manage sharing policies for each of their locations. 每个地理位置中的 OneDrive 和 SharePoint 站点将只遵循对应的地理位置特定共享设置。The OneDrive and SharePoint sites in each geo location will honor only the corresponding geo specific sharing settings. (例如,你可以为中心位置允许外部共享,但不能为附属位置允许外部共享,反之亦然。)请注意,共享设置不允许配置地理位置之间的共享限制。(For example, you can allow external sharing for your central location, but not for your satellite location or vice versa.) Note that the sharing settings do not allow configuring sharing limitations between geo locations.

分类Taxonomy

我们支持跨地理位置为企业托管的元数据使用统一分类,并将主分类托管在公司的中心位置中。We support a unified taxonomy for enterprise managed metadata across geo locations, with the master being hosted in the central location for your company. 我们建议你通过中心位置管理全局分类,并仅向附属位置分类中添加特定于位置的术语。We recommend that you manage your global taxonomy from the central location and only add location-specific terms to the satellite location's Taxonomy. 全局分类术语将同步到附属位置。Global taxonomy terms will synchronize to the satellite locations.

有关附加详细信息及开发人员指南,请参阅管理多地理位置租户中的元数据See Manage metadata in a multi-geo tenant for additional details and for developer guidance.

用户配置文件应用程序User Profile Application

每个地理位置都有一个用户配置文件应用程序There is a user profile application in each geo location. 每个用户的配置文件信息都托管在其地理位置中,并可供该地理位置的管理员使用。Each user's profile information is hosted in their geo location and available to the administrator for that geo location.

如果你有自定义配置文件属性,建议跨地区使用同一配置文件架构并在所有地理位置或所需的位置填充自定义配置文件属性。If you have custom profile properties, then we recommend that you use the same profile schema across geographies and populate your custom profile properties either in all geo locations or where needed. 有关如何以编程方式填充用户配置文件数据的指导,请参阅批量用户配置文件更新 APIFor guidance regarding how to populate user profile data programmatically, please refer to the Bulk User Profile Update API.

有关附加信息及开发人员指南,请参阅在多地理位置租户中使用用户配置文件See Work with user profiles in a multi-geo tenant for additional details and for developer guidance.

视频门户Video Portal

在多地理位置租户中,O365 视频门户仅从默认地理位置中获取服务,所有用户都将重定向到该中心门户 url。In a multi-geo tenant, the O365 Video Portal is served only from default geo and all users will be redirected to that central portal url. 因此,将根据你所在的中心位置使用适用于该地区的远程媒体服务 (RMS) ,如下所示。Hence, the Remote Media Service (RMS) for that region will be used, as follows based on your central location.

Stream 当前可在以下地区使用:Stream is currently available in the following regions:

  • 北美地区(托管在美国)North America, hosted in the United States
  • 欧洲Europe
  • 亚太地区Asia Pacific

但是,Stream 尚不支持在以下目前支持 Microsoft 365 视频的地区中使用,因此对于这些本地实例,我们将使用最近的受支持地区中的 RMS。However, Stream is not yet available in the following regions that are currently supported for Microsoft 365 Video, therefore for these local instances, we will use the RMS that is in the closest supported region.

  • 澳大利亚Australia
  • 加拿大Canada
  • 印度India
  • 英国United Kingdom

YammerYammer

Yammer 不是多地理位置工作负载。Yammer is not a Multi-Geo workload. Yammer 中存储的 Yammer 线程将放置在租户的中心位置。Yammer threads stored in Yammer will be placed in the tenant’s central location. Yammer 正在推出文件存储更改,它将在 SharePoint 中存储 Yammer 文件。Yammer is rolling out a file storage change which will store Yammer files within SharePoint. 存储在 SharePoint 中的 Yammer 文件将置于与 Yammer 组关联的 SharePoint 网站。Yammer files stored in SharePoint will be placed the SharePoint site associated with the Yammer group. SharePoint 组网站基于 SharePoint网站和组中列出的 PDL 逻辑。SharePoint group sites are based on PDL logic as outlined in SharePoint Sites and Groups.