There are so many ERP or Enterprise Resourcing Planning Software in the market today. You need to pick the best one out of all the available options if you want your company to be successful in every stream of the operations. Dynamics 365 for Finance and Operations is one of the best ERP software that you can find. Companies do benefit a lot when they deploy Dynamics 365 Operations Environment. When employees put in enough time in learning how to use the software, things can become easy for them. It will help your staff to become a lot efficient in their duties. Their performance is also going to increase drastically over a period. Companies desire to unify both the operations and finance functions in their organization to make better and informed decisions quickly. Of course, there are so many options that are out there in the market. But, Microsoft Dynamics 365 for Finance and Operations is one software that you need to pick if you want to streamline your business. Businesses will get to enjoy so many benefits when they select this particular option over all other options. Many people do not know how to set up this software, nor do they know how to navigate through the application. Don’t worry — that is fine. In this article, we will take look at the post configuration setting for Finance and Operations environment. You can login to your LCS environment and check whether D365 Operations environment deployed or not. 2. Once you click on the deployed environment you’ll see the screen that shows the network configuration, storage details, environment details, service account use to deploy the environment and administrator details. We are not going into all this details, we’ll click on the login to the environment to configure the setting for AX development. 3. Once we click on the Log on to environment we’ll see the following D365 finance and operation environment screen. For now only the Admin who deployed the environment is able to access the environment so we need to add some user to the environment. Click here and scroll down to module section.   4. Once we click on the Users we can see list of the users with role, Click on the import users link, We can then see the list of users in the tenant we have if we are D365 tenant then we’ll have all the user from the organisation. 5. From the list of user we can add the users and assign the role for the user for the D365 development. We can also set the configuration for the different tools that Microsoft offer as a part of the development like Power BI integration. So, in this blog we see how to set up the post configuration setting for the LCS and how to add users to environment for D365 development.

In this blog article, we will see how we can create a project and deploy a dynamic 365 operations environment using Lifecycle services. Prerequisites: Azure Subscription Lifecycle Service Account Step by Step approach: Environment Setup  Azure Subscription: Login to the Azure portal using credential use below URL and buy Pay-As-You-Go subscription as LCS will consume more resource and if we choose start free option it will give error later when we deploy the VM. “https://portal.azure.com/” Once we done with the subscription go to the subscription tab and select the Access Control option and create a role select the role as the Contributor and Add a user select the user as the “Dynamic Deployment Services.” We can now login to the Lifecycle Services remember we should login in LCS using the account which has the admin access to the subscription. After login we can see the following screen. The first step in LCS is to create new project so click on (+) sign to create new project.  Once we click on (+) sign we’ll have different option the option may vary as per the version of LCS you are using, here we are setting up environment for development and learning purpose select the “Migrate, Create Solutions, and Learn” option. Enter the project details and click on the create option. All the information is related to the how you want your project settings to show and the methodology option let you select what you want to shows up on the default project information that shows up in lifecycle services so the migrate and create dynamic 365 for operation solution give you these options.  Once we click on create we’ll land to the life cycle project homepage Access the Azure subscription:- Scroll to the right and click on the project settings We are accessing the azure subscription so click on the Azure connectors options we’ll see the following screen. The first step is to authorize your organisation in the LCS click on the authorize link. Linking LCS to Azure subscription click on the Add option and set the required option make sure the subscription id is same as you have in the azure portal as we may have multiple subscription set so keep in mind to use correct subscription. Once we fill the required details click on the next. Once we click on next we’ll required to authorize the user to the subscription or we can download the certificate and upload to the azure portal by going to the Subscription > Management Certificates > Upload then upload the certificate that we have downloaded. Select the server environment region for LCS. Now we can see the azure connection in the project setting we got Azure subscription id that is showing . Deployment for the virtual machine In newly created environment go to the Project and in environment tab click on the (+) sign Once we click on (+) sign we’ll application platform option choose the latest application and platform version. Select the environment topology here we are selecting Demo environment Specify the Deploy environment setting by clicking on the Advance setting option Choose the below option and leave the other settings as default Click on the next. We can set size of the virtual machine of our choice it’s fine to keep the default settings and go ahead. Once confirm and deploy the VM deployment will start, usually deployment will take 3 hr. So, this will create the D365 Operation Environment for us. In next blog we’ll see how to setup the post deployment configuration setting for the environment