Dynamics 365 (online) provides you with isolation Dynamics 365 data and allowing users access options. For most companies, and increase with multiple instances can provide the right combination of features and manageability in subscription. Companies with different geographical locations with multiple tenants may consider separating Dynamics 365 (online) license. Multiple instances can be shared between the instances that the user; not multiple tenants.
The concept and operation of tenants and although similar examples, but the Dynamics 365 On-line and On-premis deployment is different. This theme is intended for those who manage Dynamics 365 (online) deployed.
the term
Tenant:
For Dynamics 365 (online), the tenant is registered in your Microsoft Online Services environment in a Dynamics 365 account (online) founded by subscription. Tenants include domain uniquely identified, so that users, security groups, and subscribe to, and can contain multiple Dynamics 365 (online) instance.
Tenant domain for your creation is .onmicrosoft.com. For example, contoso.onmicrosoft.com.
Instance:
When you sign up for a trial version or purchase using a Dynamics 365 (online) subscription, will create a Dynamics 365 (online) production instance. You add each additional production or non-production (sandbox) Dynamics 365 (online) will be in the creation of an independent instances of the same on a tenant Dynamics 365 organizations.
Examples have the URL format: https: //.crm.dynamics.com. For example, https: //contososales.crm.dynamics.com.
Multiregional instance:
With your Dynamics 365 different areas where tenants (online) instance. Examples which may be locally provided for faster data access allows the user area. More information: add and edit multi-regional examples
Subscription:
Subscribe Dynamics 365 accessories by your license and registration in Dynamics 365 (online) account or try to use a paid service included in the composition. Dynamics 365 subscriptions may differ license type, price and terms of the termination date.
For example, a subscription might be 100 Dynamics 365 (online) professional licenses and 10 Dynamics 365 (online) business license.
Identity:
Once the user account to log on to Dynamics 365 (online). You can also access Microsoft's online services with the rest of this identity, such as Office 365 or SharePoint Online. The administrator can decide whether you want to enable users to identify joint management between Dynamics 365 (online) and on-premises Active Directory.
User account:
Assigned by the organization (work, school, non-profit organizations) to its members (staff, students, users) of the user account, which provides for one or more Microsoft cloud service subscription (such as Exchange) organization's login access online or Dynamics 365 (online). Access to online services from a user account assigned to the license control.
The organization is stored in user accounts in the cloud Azure Active Directory directory, usually when the user deletes leave the organization. Organizational account with Microsoft accounts except that they are created and managed by the organization administrator, not founded and managed by the user.
Security group:
If your company has multiple Dynamics 365 (online) instance, you can use the example of security groups to which the license allows users to access a specific instance of control. More information: control allows the user to access the instance: security groups and licenses.
A plurality of instances
Dynamics 365 (online) example is conceptually similar to the business functions of the organization floor high-rise complex in accordance with the business. Each layer should be seen as using the program (sales / service / marketing, supplier management, wealth management) in the building, and each layer of each unit of production as a specific use, training, testing and development examples of the way.
When the need to isolate plug, or the workflow management resources, require multiple instances, these resources can not be easily isolated service unit 365 with the Dynamics.
A multi-instance deployment
Typical Dynamics 365 (online) deployment consists of only one tenant. It may comprise one or more tenants Dynamics 365 (online) Examples; however, Dynamics 365 (online) Example always associated with a single tenant.
This example uses two examples to three teams: sales, marketing and service.
Sales and marketing share an instance, so that both sides can be easily accessed Lead information. Service has its own instance, it can be managed separately from tickets and warranty and sales-related activities and the rest of the activities.
You can easily provide access to one or two instances. Sales and marketing so that users can be limited to instances of them, and have extended access service allows users to upgrade supports updating records related to these two examples of accounts.
Respect to a single tenant have multiple instances of:
- A tenant may contain 50 Dynamics 365 (online) production instance and 75 non-production (sandbox) instance.
- Each instance of tenants are receiving their own SQL database.
- Dynamics 365 data is not shared across instances.
- Examples of shared memory between the main and any remaining examples.
- All instances of a single tenant users will be set in the initial registration of their account geographic location. For all instances of tenant users to summarize and track storage consumption.
- You can set up a separate security group for all instances.
- Authorized Dynamics 365 (online) so that users can potentially have access to all Dynamics 365 associated with the tenant (online) instance. Access is controlled by the example security group.
- You can purchase the remaining instance by additional examples add-ons. Additional examples can only be increased "paid" subscription - rather than experimental or internal use rights (IUR). If you have purchased Dynamics 365 (online) through volume licensing subscription, then you must purchase additional instances through your large account reseller (LAR). More information: billing and subscription support
- You can not merge the existing experimental or subscribe to the remaining instance; instead, you will need to move data and customization.
Why use multiple instances?
Here is a common example of the use of multi-instance deployments. In determining the most appropriate type of company needs to deploy, consider these examples.
Master Data Management
In this scenario, the "main" data set providing central change management master data source. This method requires a central master data synchronization with all instances, so that each instance can access the latest version of the core information. Request for information changes can be made directly in the main system. Or by the user can access the main system explicitly or capture changes in the local instance, then those changes will be passed to the primary instance.
Requirements focus change can provide centralized change control. For example, you can perform anti-fraud checks to ensure that only changes by the central team, rather than the possible benefit from the change (such as changing credit limit) in a local team. This will provide a second-level changes authorized and validated, in order to avoid a single person or a group of people working closely collaborate to fraud. Push the request to a different, independent teams can prevent potential fraud.
Security and privacy
Regional differences, such as differences in the European Union (EU) or national legislation, may result in different regions or countries of the claimed data or maintenance data privacy vary during deployment. In some cases, the legislative / regulatory restrictions so that stored outside a country or region is illegal data, to address this challenge is particularly critical in a particular business sector.
For example, taking into account the health sector to limit sharing patient information. EU regulations require a small amount, all collected information about the health of people living in the EU can only be maintained and shared within the EU, but similar data were stored on Americans within the United States. Also consider limiting the banking sector to share user information. For example, in Switzerland, the law beyond its borders shared user information is illegal.
Scalability
One example though Dynamics 365 can be extended or expanded to support the growth of the business user, and have a very high level of complexity or the amount of data, but also the rest of considerations. For example, with great capacity and / or widely used service scheduling environment, expand SQL Server may require complex and expensive infrastructure, and the cost of these infrastructure prohibitively high, or are difficult to manage.
In many scenarios, the ability to demand the presence of natural functional separation. In this case, through the creation of a commodity infrastructure to provide higher capacity based on the extended scene delegate these functions to divide the workload can.
Multi-tenant deployments
With different regions or countries of the global business model can be used to consider ways of tenants, the market size or to comply with changes in the legal and regulatory restrictions.
This example includes a second tenant Contoso Japan.
无法在租户之间共享使用户帐户，身份，安全组，订阅，许可和存储。所有租户都可以拥有与每个特定租户相关联的多个实例。D365 数据不能跨实例或者租户共享。
关于多个租户：
- 在多租户方案中，与租户关联的许可Dynamics 365（在线）使用户只能访问映射到同一租户的一个或者多个Dynamics 365（在线）实例。要访问其余租户，使用户需要单独的许可证和该租户的一组唯一登录凭据。
- 例如，假如使用户A具备访问租户A的帐户，则他们的许可允许他们访问在租户A中创立的任何和所有实例 - 假如他们的管理员允许的话。假如使用户A需要访问租户B中的实例，他们将需要额外的Dynamics 365（在线）许可证。
- 每个租户都需要具备唯一登录凭据的租户管理员，并且每个租户关联企业将在管理员控制台中单独管理其租户。
- 假如管理员具备访问权限，则可以从Dynamics 365（在线）界面中看到租户中的多个实例。
- 您无法在租户注册之间重新分配许可。注册的会员可以在一次注册下用许可证减少，并将许可证增加到另一个注册表以促进此操作。
- 除非您具备需要与不同租户联合的顶级域（例如Contoso.com和Fabricam.com），否则无法用多个租户建立本地Active Directory联合。
为什么用多个租户?
功能定位
- 这种场景通常出现在功能需求重叠但又独立的组织中。少量常见的例子包括:
- 具备不同业务部门的组织，每个部门都有不同的市场或者运营模式。
- 具备区域或者国家模式的全球业务，因方法、市场规模或者遵守法律和监管限制的差异而有所不同。
- 在这些类型的业务环境中，组织通常具备公共的功能集，这些功能集允许特定的区域、国家或者具备肯定本地化程度的业务领域:
- 捕获的信息。例如，在美国捕获邮政编码将与在英国捕获邮政编码相关联。
- 表单,工作流。
物理分布
- For long distance must support the physical distribution service processing program allows the user, especially for the global deployment, a single instance may not be suitable, because it may significantly affect the user so that the infrastructure connection-related effects (for example delayed WAN) allows the user to experience. Examples of local distribution to provide more access to enable the user can reduce or overcome the problems associated with the wan, since the connection within a very short access network.
Multi-tenant deployments increase in volume licensing
For multi-tenant deployments, you need a multi-tenant amendment. Multi-tenant amendment is revised to use actual volume licensing agreement to purchase a license. Please contact your Microsoft sales representative or contact the dealer to get the amendment.
Multi-tenant bondage
Want to deploy and manage multiple tenants administrator should understand the following:
- The user accounts, identity, security groups, subscriptions, licensing and storage can not be shared between the tenants.
- Single domain only in conjunction with a tenant.
- Each tenant must have its own namespace; UPN or SMTP namespace can not be shared between the tenants.
- If the on-premises Exchange organization exists, the tissue is not split into multiple tenants.
- An integrated global address list will not be used, unless explicitly synchronize downstream.
- Cross-tenant joint collaboration will be limited to Lync and Exchange joint function.
- Cross-tenant access SharePoint may not be possible. Although this can be handled by partners to access, but the user experience will be disturbed, and should use licensing.
- In the on-premises Active Directory, you can not duplicate account between the tenant or partitions.
Source https://cloud.tencent.com/developer/article/1345436