Configure an Azure Connector in LCS

-

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

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 rbansode@microsoft.com.

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!

Comments

Post a Comment

Popular posts from this blog

Using Notifications in Business Central via AL

-
Image
Introduction Notifications in Business Central are alerts that appears in the Notification bar based on User actions. Notifications stack up from top to bottom, lasting until the user dismisses them, including those from sub-pages.  Validation errors are prioritized and shown before other notifications. We can use this to alert the user regarding something without taking all the user's notification towards it, in the way messages or errors do. They also have the option to allow Users to make a corrective action by embedding the action button directly into the notification. Let's see how it works. Source Code Pre-requisites Business Central OnPrem/Cloud. References Notification - Business Central Docs Configuration Here, for an example, I've created one simple page which takes two inputs. 1. The message that is to be shown in the notification. 2. The message to be shown after the User clicks on the action embedded in the notification.     And I have two actions which I'l...
Read more

Actionable Error Messages in Business Central

-
Image
Introduction Error handling is an important concept in every technical field.  It helps programs deal with unexpected problems and mistakes smoothly.  It makes sure software works reliably and doesn't crash unexpectedly.  Error handling also helps developers find and fix issues quickly, making the software better for users. Plus, it gives users clear messages when something goes wrong, making their experience smoother. It shows that the team has considered the scenario and has measures in place for it indicating a well designed solution. Microsoft has an amazing document which lists the things to keep in mind for writing resilient code. In Business Central, we have try functions to handle errors and error function to show those errors to the Users.  In this blog, we'll learn how we can enhance the error messages so that the Users can resolve the errors themselves or at the very least we can point them towards where the error is. Pre-requisites Business Central OnPrem...
Read more

Configure Gmail SMTP service in Business Central without "Allow Less Secure" setting

-
Image
 Introduction Business Central has great email features like sending email, editing it with Rich Text, adding attachments, etc, but to send emails, you'll need to connect it with services like Outlook or Gmail. There is no outlook side configuration that is to be done if you are using Microsoft Outlook however if you are using Google's Gmail then there's a litte change that has happened on the configuration end. Starting May, 2022, Google has removed the "Allow Less Secure Apps" settings from the Google Accounts, which was essential is using Gmail to send emails from Business Central. However, to replace that we have "App Passwords" which we can use instead. Also, just something to keep in mind, Google is going to remove this from the "Google Workspace" accounts as well by Sept, 2024 so it would be wise for you to migrate your configurations to use app passwords. Reference 1.  How to Setup Email in Business Central 2.  Google Support - Less sec...
Read more