With the deprecation of Azure Access Control Service (ACS), we have to modify our SDK authentication code by removing all references to ACS. Effective from versions Microsoft Dynamics CRM Online 2016 Update 1 (v8.1.1) and Microsoft Dynamics 365 (v8.2), we removed Live ID support and ACS dependencies on the server-side.
We also removed Microsoft.Xrm.Client from the CRM 2016 (8.x) SDK client because it was not compliant with the OAuth changes, and replaced it with Microsoft.Xrm.Tooling.Connector. You can use the current Microsoft Dynamics 365 Software Development Kit (SDK) to access Microsoft Dynamics CRM back to version 6.x for both auth and messaging.
When upgrading to Dynamics 365, make sure you use the latest Microsoft Dynamics 365 Software Development Kit (SDK). The following outlines the current supported matrix for other SDK clients:
| .NET Framework | SDK Client | Dynamics CRM versions | Description |
| .net 4.0 | CRM 2013 (6.x) (released as version 6.0 – 6.1.1 on nuget)
| v6.x, v7.x, v8.0 & v8.1.0(only) | Supported* *v8.1.1 + is not supported by this SDK, update 6.1.2 will add support
|
| .net 4.0 | CRM 2013 (6.x) (will be released as 6.1.2 on nuget) | v6.x, v7.x, & v8.x | Coming soon |
| .net 4.5.2 | CRM 2015 (7.x) Download here | v6.x, v7.x, v8.0 & v8.1.0 | Supported* *v8.1.1+ is not supported, Move to SDK version 8.x for support for CRM version 8.1.1+ |
| .net 4.5.2 | CRM 2016 (8.x) Download here | v6.x, v7.x, & v8.x | Supported |
See Also:
Software Development Kit for Microsoft Dynamics 365 (online) and Dynamics 365 (on-premises)
Updates to the CRM SDK assemblies
Connect to Microsoft Dynamics 365 web services using OAuth
Visual Studio and the .NET Framework
– Paul Liew