Introduction

In this blog, we’ll be looking into configuring the Azure Connector in LCS with the Azure Resource Manager so that LCS can deploy your resources to Azure.

Pre-requisites

An Azure subscription that you are a co-administrator in.

References

1. Azure Resource Manager overview – Microsoft Learn
2. Deploy a demo environment – Microsoft Learn
3. Deploy and access development environments – Microsoft Learn
4. Complete the Azure Resource Manager onboarding process – Microsoft Learn

Configuration

Go to Microsoft Dynamics Lifecycle Services and log in with your account.

In LCS, when we try to create a cloud hosted environment for the first time, it prompts us to create an Azure Connector first.

You can also access this by going to your Project Settings and the “Azure Connectors.”

Once, we reach this screen, we have to click on Authorize in the organization where we want to authorize.

Please do ensure your account has the necessary permissions for these actions. Once, this is done click on Microsoft Azure Portal as there are a few configurations we need to do in the Azure Portal.

Click on Subscriptions.

From the Subscriptions list, we can note down the Subscription ID as we will need it while creating the Azure Connector.

The “Subscription ID” is also available in the Overview section of the Subscription.

Then go to the Access Control (IAM) tab and click on Add and then Add Role Assignment.

Then go to Role -> Privileged Administrator Roles and then search for “Contributor”.

Click on it and then click on Next.

In the members tab, click on User, group or Service Principal and click on Select Members.

After that search for and add “Dynamics Deployment Services [wsfed-enabled]” and your own user to this role assignment.

Once that is done, we’ll get a confirmation message.

After that, we can move back to the LCS for configuring the Azure Connector.

We click on Add to create a new Azure Connector and get the following pop-up.

Here we add a name for the connector, Azure Subscription ID and the Domain Name.

Name can be anything that you want, the Domain Name in most cases is the part of your email address after the @. For e.g. it’d be “microsoft.com” in case of [email protected].

For the Azure Subscription ID, we have already stored that from the previous steps.

Once we add the necessary values and click on next we get the following pop-up.

We’ve already completed the necessary steps in the Azure Portal so we can simply click on Next.

After that, we get the following pop-up.

We’ve completed the steps mentioned in the Ensure you are a subscription user section.

If for some reason you are facing any difficulties in that you can also try the steps from the Apply a Subscription Tag section.

Apply a subscription tag

When you click on Get a Code you’ll get the following pop-up which includes a unique verification code. We copy this and head on to the Azure Portal.

Then go to your subscription in Azure Portal.

Head to the Tags section and create a new entry with name as “LifecycleServicesAuthCode” and the value as unique verification code from LCS.

If neither of those methods work, there is a soon to be deprecated method mentioned as well where you upload the certificate downloaded from LCS into the “Management Certificates” of your Azure Subscription.

Hopefully, one of these three methods work out for you and you’ll get the following pop-up.

Once you click on connect you’ll see an entry created in your Azure Connectors.

This indicates that your Azure Account has been linked and now LCS can utilize it to create resources in Azure on your behalf.

Side Note

If you see the following error message then that means there was an error with one of the three suggested approaches you choose. You can try with another approach and start over.

Conclusion

Thus, we saw how to configure the Azure Connector in LCS.

Happy Coding!