| title | description | ms.custom | ms.date | ms.reviewer | ms.suite | ms.tgt_pltfrm | ms.topic | applies_to | ms.assetid | caps.latest.revision | author | ms.author | search.audienceType | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Dynamics 365 Customer Engagement (on-premises) Integration with Office 365 (Developer Guide for Dynamics 365 Customer Engagement (on-premises))| MicrosoftDocs |
Learn how Dynamics 365 Customer Engagement (on-premises) customers that are subscribed to Office 365 can have single sign-on access through integration of Dynamics 365 Customer Engagement (on-premises) with Office 365 |
03/29/2019 |
pehecke |
article |
|
24a41d45-e8dc-47f0-8faf-65cb01ab7f3c |
48 |
JimDaly |
jdaly |
|
This documentation applies to customers who access Dynamics 365 Customer Engagement (on-premises) through the [!INCLUDEpn_ms_online_services_environment]. Through integration of Dynamics 365 Customer Engagement (on-premises) with [!INCLUDEpn_MS_Office_365], Dynamics 365 Customer Engagement (on-premises) customers that are subscribed to [!INCLUDEpn_Office_365] have single sign-on access, through identity federation, to any [!INCLUDEpn_Office_365] supported application, such as [!INCLUDEpn_Microsoft_Exchange_Online]. Similarly, when provisioned, [!INCLUDEpn_Office_365] customers have access to Dynamics 365 Customer Engagement (on-premises). In addition, by federating [!INCLUDEpn_Active_Directory] domain accounts in [!INCLUDEcc_Microsoft] cloud services, businesses can manage a single set of user identities in both their [!INCLUDEpn_Active_Directory] domain and Dynamics 365 Customer Engagement (on-premises).
This topic provides information about where users’ identities are created and managed, and how they relate to Dynamics 365 Customer Engagement (on-premises).
When accessing the Dynamics 365 Customer Engagement (on-premises) web services, your applications should know the identity provider associated with the logged on user’s Dynamics 365 Customer Engagement (on-premises) account. Configuration of the user’s authentication credentials for accessing the web services through SDK calls is slightly different for each provider. The details on how to configure user credentials for each identity provider and access the Dynamics 365 Customer Engagement (on-premises) web services is discussed in the topic Access the Dynamics 365 Customer Engagement (on-premises) Services.
There are two identity providers supported by Dynamics 365 Customer Engagement (on-premises) and provisioned through [!INCLUDEpn_MS_Online_Services]: User ID, and [!INCLUDEpn_Active_Directory] (through cloud federation). The following discussion provides an overview of these identity services and how they relate to Dynamics 365 Customer Engagement (on-premises)].
User ID represents user identities provisioned by customers in [!INCLUDEcc_Microsoft] cloud services and is the identity provider for all customers who have subscribed to the [!INCLUDEpn_Office_365] collaboration environment. User ID enables you to have access to all [!INCLUDEcc_Microsoft] online services such as [!INCLUDEpn_Microsoft_Exchange_Online] and Dynamics 365 Customer Engagement (on-premises). Customers with a User ID have their account credentials and policies managed through [!INCLUDEpn_MS_Online_Services].
For the sake of this discussion, User ID users are referred to in this documentation as “managed” or “non-federated” users.
Federation allows customers to use [!INCLUDEpn_Active_Directory]-based domain user accounts to access [!INCLUDEpn_MS_Online_Services] such as [!INCLUDEpn_Office_365] or Dynamics 365 Customer Engagement (on-premises). After federation is configured by an administrator, [!INCLUDEpn_Active_Directory]-based system user accounts can be locally managed, made available to [!INCLUDEpn_MS_Online_Services], and kept in sync with changes made to the on-premises [!INCLUDEpn_Active_Directory] identities. The benefit of federation is a single sign-on experience across Dynamics 365 Customer Engagement (on-premises) and Dynamics 365 Customer Engagement (on-premises) systems. This type of identity management is useful for large corporations that have hundreds or thousands of established users.
For more information about how to configure identity federation, see Single sign-on: Roadmap.
[!INCLUDEpn_Windows_Live_ID] continues to be a supported identity provider for Dynamics 365 Customer Engagement (on-premises). However, [!INCLUDEpn_Windows_Live_ID] is not supported for Dynamics 365 Customer Engagement (on-premises) organizations when provisioned through [!INCLUDEpn_MS_Online_Services]. Dynamics 365 Customer Engagement (on-premises) customers that are not subscribed through [!INCLUDEpn_Office_365] can access Dynamics 365 Customer Engagement (on-premises) through their [!INCLUDEpn_Windows_Live_ID].
Connect with Microsoft Office 365
Access the Dynamics 365 Customer Engagement Web Services
xref:Microsoft.Xrm.Sdk.Client.AuthenticationCredentials
Active Directory and Claims-Based Authentication
Active Directory Federation Services
Access Control Service 2.0
[!INCLUDEfooter-include]