Important Information About Your Microsoft Dynamics CRM Online Service – ACS for authentication

error

Recently, a lot of our customers have been receiving a Microsoft email with the great title: “Important Information About Your Microsoft Dynamics CRM Online Service“. If you did not know better, you would suspect some kind of scam. But don’t delete the email as it might help you prevent a suddenly disruption of your services.

The email you might receive

We have detected an issue on your CRM online instance that we need your help to resolve. Action is required before September 30, 2017 to ensure your solution using ACS for authentication will continue to run as expected
Description of the issue:
Through internal monitoring and telemetry we have determined there are components authenticating to your Dynamics CRM service using Access Control Service (ACS). Mitigation steps must be taken before September 30, 2017 to ensure your connected components currently using ACS for authentication will continue to function as expected without failure. Please review each scenario given in the “Action to be taken” section and take appropriate action to update to a later version of the Microsoft.Xrm.Sdk.dll which does not rely on ACS authentication.

What is ACS? Windows Azure AppFabric Access Control Service (ACS) is a way to provide identity and access control to web applications and services while integrating with standards-based identity providers.
Action to be taken:
One or more of your components are still accessing ACS for authentication. Please review each scenario below and see if you are using any of them. If so, please perform the appropriate mitigation steps given below.

  • If you are using Microsoft.XRM.SDK.dll either through a custom application or custom portal, please follow the steps below:
    • Scan the folders on your server where the solution is running and look for: Microsoft.XRM.SDK.dll. If found, use the table given in the Team Blog site to determine which version of the SDK you need to download.
    • Using the table, determine which version of .NET that you have deployed against, and confirm the version of Dynamics 365 CRM service you are using. If you are uncertain which .NET version your solution is using, contact your development or engineering teams.
    • Once you have determined the correct SDK version to use simply replace the Microsoft.XRM.SDK.dll found in /bin folder with the latest version of the SDK dll.
  • If you are using a third-party product developed by a partner or ISV that relies on the Microsoft.Xrm.SDK.dll, please follow the steps below:
    • Scan the folders on your server where the solution is running and look for: Microsoft.XRM.SDK.dll. If found, and the version is older than 8.2.x, contact your ISV or third party product owner as soon as possible for guidance
    • If you are unable to reach your ISV or partner you may swap out the SDK DLL version using the blog article as a guide.
  • If you are currently using ADX Studio v7.* – The Adoxio team has provided the guidance for the fixes for ADX Studio and Dynamics 365 Compatibility for the community.
  • If you are currently using Unified Service Desk (USD) that is less than the latest version of USD 2.2, please upgrade to USD 2.2 or higher.
  • If you are currently using Email Router that is less than the latest version of Email Router 8.2 or Email Router 8.1 please update to the latest version by downloading and installing the update located here.
  • If you are using the Dynamics Connector solution to connect to an ERP system (GP/AX/NAV/SL), please use the step-by-step guide to update your version.
  • If you have developed custom fetch-based reports and are using Report Authoring Extension with version 8.0 or below, please apply CRM2016-Srs-KB3154952-LangID-amd64.exe from the December 2016 Update for Dynamics 365 to update to version 8.2.
  • If you are currently using Developer Toolkit to develop custom code that is using an older version of the Microsoft.Xrm.SDK.DLL (v8.0 or older), please update to the latest version of developer toolkit.

Solution: Update Dynamics CRM Client SDK version to avoid calls to ACS

Problem

With the deprecation of Azure Access Control Service (ACS), you should modify the SDK authentication code by removing all references to ACS. Effective from 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. It is required to update the references in all client side components by updating the SDK.

Impacted Versions

A client side component is either installed on your server or one of the machine that interacts with Dynamics CRM using Microsoft.Xrm.SDK.DLL. E.g. Email Router, Dynamics Connector, Unified Service Desk etc. For all client components list please refer the “Update the Client Component” section

Any client side component SDK (Microsft.Xrm.SDK.DLL) version 8.0 or lower should be updated to the latest version.Client-side component SDK

Update the Client Component

The following are the possible client side components that might use ACS

  • Custom Application(s) – If you have developed a Web/Windows/Console application that is interacting with Dynamics CRM
    • Scan the folders on your server where the solution is running and look for: Microsoft.XRM.SDK.dll. If found, use the table given in the Team Blog site to determine which version of the SDK you need to download.
    • Using the table, determine which version of .NET that you have deployed against, and confirm the version of Dynamics 365 CRM service you are using. If you are uncertain which .NET version your solution is using, contact your development or engineering teams.
    • Once you have determined the correct SDK version to use simply replace the Microsoft.XRM.SDK.dll found in /bin folder with the latest version of the SDK dll.Replace Microsoft.XRM.SDK.dll with latest version of SDK dll
  • Third-party product(s) –  If you are using a 3rd party products developed by a partner or ISV that interacts with Dynamics CRM, please follow the steps below:
    • Scan the folders on your server or machine where the solution is running and look for: Microsoft.XRM.SDK.dll. If found, and if the version is older than 8.1.x, contact your ISV or third party product owner as soon as possible for guidance
  • ADX Studio v7.* – If you are using ADX Studio V7.* for Portal development, the Adoxio team has provided the guidance for the fixes for ADX Studio and Dynamics 365 Compatibility. Please follow the instructions to update your
  • Unified Service Desk (USD) – If you are using USD client that is less than the latest version of USD 2.2 or USD 2.1, please upgrade to USD 2.2 or higher.
  • Email Router – If you are currently using Email Router that is less than the latest version of Email Router 8.2 or Email Router 8.1, please upgrade to the latest version by downloading and installing the update located here
  • Dynamics Connector – If you are currently using Dynamics Connector solution to connect to an ERP system (GP/AX/NAV/SL), please use the step-by-step guide to update your version
  • Report Authoring Extension – If you are developing custom fetch-based reports and use Report Authoring Extension of version 8.0 or below, please apply CRM2016-Srs-KB3154952-LangID-amd64.exe from December 2016 update for Dynamics 365 to update to version 8.2
  • Developer Toolkit – If you are currently using Developer Toolkit to develop custom code that is using older Microsoft.Xrm.SDK.DLL (v8.0 or older), please update to the latest version of developer toolkit

Leave a Reply

Your email address will not be published. Required fields are marked *