Im trying to configure a Azure connector on LCS but its failing

Question

Im trying to configure a Azure connector on LCS but its failing. When I try to add "DD Dynamics Deployment Services [wsfed-enabled] (pme)" in the role assignment its not showing.

Answer 1

Hello @VishTrial D365FO,

Thank you for posting your query on Microsoft Q&A.

Based on your description, I understand that you are trying to add an Azure subscription to a Lifecycle Services (LCS) project. However, when attempting to provide Dynamics Deployment Services access to your Azure subscription, it does not appear in the role assignment.

According to the documentation, this issue can occur if the authorization process has not been completed fully. In such cases, the Dynamics Deployment Services [wsfed-enabled] role will not appear under role assignments.

To resolve this, I recommend re-running the Authorize workflow to ensure it is visible in your environment.

The administrator of the tenant must complete the following procedure.

1. In LCS, on the Project page, in the Environments section, select Microsoft Azure settings.
2. On the Project settings page, on the Azure connectors tab, in the Organization list group, select Authorize to start the Azure Resource Manager Contributor workflow. This workflow sets up permissions for the deployment service, so that it can deploy to your subscription on your behalf.
3. On the Grant admin consent page, select Authorize. Then sign in by using the administrator account of the Azure subscription that you must connect to, and select Accept. The authorization is now shown as completed.

Note: Ensure you complete the Grant admin consent prompt using a Global Administrator account in your tenant.

For detailed, step-by-step instructions on granting admin consent, refer to the following document: Add Azure subscription to LCS project

Ref: https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/deployment/arm-onboarding

I hope this information is helpful. Please feel free to reach out if you have any further questions.

Thanks,
Raja Pothuraju.