Server-Based SharePoint Integration issue

Hi @Jakob

Is there any update from you?

If yes, please feel free to let me know.

Hi @Michelle-N

In terms of "Please verify the current Microsoft prerequisites for Dynamics 365 Customer Engagement on premises with SharePoint Online. Microsoft now documents that, starting in March 2025, an Azure application with SharePoint application permissions is required. The app should have SharePoint Sites.FullControl.All application permission with admin consent, and the Dynamics on-premises organization must be configured with the Azure app ID and tenant ID in PartnerApplicationBase."

I understand the reasoning behind creating an App Registration. However, in the setup wizard, it doesn't seem possible to add the App Registration details.

When setting up the integration, you simply sign in as an administrator in Dynamics 365. After that, you complete a setup wizard where there doesn't appear to be any place to enter the App Registration values.

The only information you need to provide is the SharePoint tenant ID and the SharePoint URL.

Am I missing something?

Hi @Jakob

Thanks for the clarification. You are correct that the Enable Server-Based SharePoint Integration wizard itself does not provide a field where you manually enter the Azure App Registration ID or tenant ID. In the wizard, you normally only provide/select the SharePoint location, such as the SharePoint Online URL and tenant-related information.

The newer Azure App Registration requirement is configured outside of that wizard. Per the current Microsoft documentation, after creating the Azure app and granting the SharePoint Sites.FullControl.All application permission with admin consent, the app ID and tenant ID are added to the Dynamics 365 Customer Engagement on-premises organization database through the PartnerApplicationBase table. The Microsoft article provides a SQL script where you replace:

DECLARE @byoaAppId NVARCHAR(36) = '<appId>';
DECLARE @tenantId NVARCHAR(36) = '<tenantId>';

with the Azure Application (client) ID and Directory (tenant) ID.

The sequence is more like:

1. Apply the required Dynamics 365 CE on-premises update, such as Service Update 1.36 or later.
2. Create the Azure App Registration.
3. Add SharePoint application permission Sites.FullControl.All and grant admin consent.
4. Install/copy the required Microsoft.Identity.Client 4.11.0 files to the Dynamics CRM web application bin folder, as described in the documentation.
5. Add/update the Azure app and tenant information in PartnerApplicationBase.
6. Configure/upload the S2S certificate as required.
7. Then run the SharePoint integration wizard and validate the SharePoint URL.

For reference, please check this Microsoft Learn article: Create an Azure application for Dynamics 365 Customer Engagement on-premises with SharePoint permissions.

Hope this clarifies why the App Registration details do not appear in the wizard UI.

@Michelle-N Thanks for the update.

Just to make sure I understand the responsibilities correctly: as the Global Administrator and SharePoint Administrator, my role is to create the Azure App Registration, grant the required Sites.FullControl.All application permission, and provide admin consent.

Is it then the responsibility of the Dynamics 365 CE on-premises administrators to use the Application (Client) ID and Directory (Tenant) ID from the app registration, update the PartnerApplicationBase table by running the SQL script, and complete the remaining Dynamics-specific configuration?

Hi @Jakob

Yes, that understanding is generally correct.

From the Microsoft 365 / SharePoint side, the Global Administrator or SharePoint Administrator would typically be responsible for creating the Azure App Registration, adding the SharePoint application permission Sites.FullControl.All, and granting tenant-wide admin consent. After that, the Dynamics 365 Customer Engagement on-premises administrators would normally take over the Dynamics-specific configuration.

I would also recommend having the Dynamics 365 on-premises team validate the configuration end-to-end, because the SharePoint admin consent alone is not sufficient. The Dynamics organization database, certificate configuration, and required server-side components must also match the documented configuration.