Deprecation of Office365 authentication type and OrganizationServiceProxy class for connecting to Dataverse

Deprecation of Office365 authentication type and OrganizationServiceProxy class for connecting to Dataverse

WHY and WHEN - Deprecating Office365 Integration

This is fully documented for a while here Important changes (deprecations) coming in Power Apps and Power Automate - Power Platform | Microsoft Docs

Impacted customers are those who still use username/password (the old legacy Dynamics 365 integration) and have not enabled OAuth authentication yet.

Provided below - how to resolve the issue depending on different scenarios.  

NOTE: It is strongly advised that you take action NOW and have your integration ready before 1st April 2022 deadline.  

~

Dynamics 365 Business Central SaaS 

Move to OAuth2.0 authentication.

User must change the authentication type to connect to Dataverse. 

1. Open Microsoft Dynamics 365 Connection Setup page
2. In the action pane choose Connection > Use Certificate Authentication
3. When prompted to sign in via https://login.microsoftonline.com, sign in as the Administrator of your Dataverse organization
4. Wait for the task to be accomplished (it should take about 30/40 seconds).

In the end, you should get an information message that you have successfully upgraded your connection to Dataverse to a service-to-service (S2S) connection with a certificate, and that you got a new integration user.

NOTE: SaaS customers will benefit of further communications from product group about how to proceed considering their environment and integration types.

 ~

Dynamics 365 Business Central On-Premise 19.x, 18.x, 17.x and 16.x 

Move to OAuth2.0 authentication.

For Business central SaaS, Microsoft has registered its own app for OAuth2 connection, whereas in Business Central OnPrem, the OnPrem owner has to register the app. Follow this OnPrem specific documentation: https://docs.microsoft.com/en-us/dynamics365/business-central/admin-how-to-set-up-a-dynamics-crm-connection#connecting-on-premises-versions  

NOTE: 16.0 and 16.1 needs to be updated to 16.2 or higher in order to enable OAuth2.0 authentication With 16.0 and 16.1, only OAuth authentication could be enabled. In this situation, it is warmly recommended to upgrade to 16.2 or later. 

 ~

Dynamics 365 Business Central On-Premise 15.x 

NOTE: This version is out of support as per lifecycle since April 2021. See more Software lifecycle policy and on-premises updates - Business Central | Microsoft Docs 

Move to OAuth authentication.

See how to do it here (99+) How to enable OAuth authentication in Dynamics 365 Integration for Dynamics NAV and Dynamics 365 Business Central - Dynamics 365 Business Central Forum Community Forum 

NOTE: both application (objects) and platform need to be updated, at least, to December 2020 CU (15.13) https://support.microsoft.com/help/4583552 or higher to enable OAuth authentication. 

You can also upgrade to a higher version before April 2022 deadline and enable OAuth2.0 authentication. This is the recommended solution by Microsoft.

 ~

Dynamics 365 Business Central On-Premise 14.x 

Move to OAuth authentication.

See how to do it here (99+) How to enable OAuth authentication in Dynamics 365 Integration for Dynamics NAV and Dynamics 365 Business Central - Dynamics 365 Business Central Forum Community Forum

NOTE: both application (objects) and platform need to be updated to January 2021 CU 20 (14.21) https://support.microsoft.com/help/4595149 or higher to enable OAuth authentication. 

 ~

Dynamics 365 Business Central On-Premise 13.x 

NOTE: This version is out of support as per lifecycle since April 2020. See more Software lifecycle policy and on-premises updates - Business Central | Microsoft Docs 

This version does not support OAuth authentication with Dynamics 365 integration feature.

The solution is to upgrade to a higher version before April 2022 deadline and enable OAuth authentication. 

 ~

Dynamics NAV 2018 

 Move to OAuth authentication.

See how to do it here (99+) How to enable OAuth authentication in Dynamics 365 Integration for Dynamics NAV and Dynamics 365 Business Central - Dynamics 365 Business Central Forum Community Forum

NOTE: both application (objects) and platform need to be updated to June 2021 CU 41 or higher to enable OAuth authentication. 

 ~

Dynamics NAV 2017 

NOTE: This version is out of mainstream support as per lifecycle since January 2022. See more Dynamics NAV 2017 - Microsoft Lifecycle | Microsoft Docs

Move to OAuth authentication.

See how to do it here (99+) How to enable OAuth authentication in Dynamics 365 Integration for Dynamics NAV and Dynamics 365 Business Central - Dynamics 365 Business Central Forum Community Forum

NOTE: both application (objects) and platform need to be updated to July 2021 CU 55 or higher to enable OAuth authentication. 

 ~

Dynamics NAV 2016 

NOTE: This version is out of mainstream support as per lifecycle since April 2021. See more Dynamics NAV 2016 - Microsoft Lifecycle | Microsoft Docs

Move to OAuth authentication.

See how to do it here (99+) How to enable OAuth authentication in Dynamics 365 Integration for Dynamics NAV and Dynamics 365 Business Central - Dynamics 365 Business Central Forum Community Forum

NOTE: both application (objects) and platform need to be updated to July 2021 CU 67 to enable OAuth authentication. 

IMPORTANT: see also Modifying Dynamics 365 Sales Code for Technical Upgrade to Dynamics NAV 2016 | Microsoft Docs