How to change Microsoft Dynamics 365 Instance URL in Portal


Customers sometimes want to change the URL once created for the Dynamics 365 instance. This blog is aimed to help fellow Dynamics 365’ers with getting the Dynamics 365 URL change in Portal with either a production / sandbox or trial dynamics 365 instance.

  • Admin Centre –>Dynamics 365 –> Click on Instance (Right Click) –>Edit





  • Edit the URL










  • Click Next
  • Click save after review.
  • Click on Admin Centre –> Dynamics 365 –> Applications tab –> Client Portal –> Manage



  • Click on Portal Actions


  • Click on Update Dynamics 365 URL


  • Click on Update URL


  • To reflect the changes instantly on Portal, restart the portal once as shown below.


  • Click to confirm the restart of the portal (keep in mind, by restarting the portal, the portal will go on inactive mode for few minutes, better to perform this action in off hours of the customer)


  • Navigate to Manage Dynamics Instance, you can see the updated Dynamics 365 URL here.


Introduction to Dynamics 365 Retail SDK & Overview of CRT Sample Extension

Overview of Dynamics 365 Retail SDK:

To start with, let’s discuss folders & its purpose which exist in retail SDK folder.

  1. Assets

Contains configuration files like commerceRuntime.config etc.

  1. BuildTools

Contains files like customization.settings which have all information regarding build.

  1. CommerceRuntime

Contain a visual studio solution commerceRutime.sln, all customized logic for retail POS can be written & tested here by extending this project.

  1. Database

Contains shared database scripts.

  1. Documents

Contains documentation for Retail SDK sample. A PDF file ‘AX7 Retail Sdk Handbook’ is here which have detailed information about retail SDK components & its customization.

  1. HardwareStation

Contain a visual studio solution HardwareStation.sln

  1. OnlineStore

Contain a visual studio solution OnlineStore.sln.

  1. Packages

Contains multiple projects for project creation.

  1. Payments

Contain visual studio solution PaymentSDK.sln. This folder have different samples to help with implementing different payment methods & payment SDK connectors.

  1. POS

Contains two visual studio solutions CloudPOS.sln & ModernPOS.sln

  • Cloud POS is a browser-based POS, can be used on mobiles & PCs.
  • Retail Modern POS(MPOS) can be used on clients such as PCs, tablets, and phones to process sales transactions, customer orders, and daily operations, and to perform inventory management.
  1. References

All dlls or binaries exist here that are being generated by Retail SDK. All related Projects dlls are found here.

  1. SampleExtensions

It contains sample extension of different components of SDK. I went through Commerce Runtime (CRT) sample extension which I will be discussing here.

  1. proj (File)

A file that directs build order 


Simplest & easiest way to get latest dlls/binaries of multiple solutions of retail SDK can be with simple msbuild command at retail SDK root. All new dlls would be then dropped to References Folder as discussed previously.


  1. Microsoft-version.txt

It contains Microsoft’s version information of SDK. This should not be edited.


CRT Sample Extension:

There are few sample projects provided in retail SDK among which I tried CrossLoyalty

Consider that there are 2 retailers, AdventureWorks and Contoso. As a part of a deal, Contoso retailer will accept loyalty points of AdventureWorks. The sample shows how to create a simple new CRT service and call it once a button in MPOS is clicked. It simulates the cross loyalty scenario. I will be give an insight of CRT service code here in this space.


Here is request class which expects a loyalty card number.



Here is response class which returns discount against loyalty card number.



Here is actual service which “CrossLoyalityCardServices.cs” returns discount as per card number.



CRT service can be tested here at host here without getting it through POS.


Once you are done with CRT  you need to register it in commerceruntime.config as higlighted.


Then you need to add CRT dll extension to customization.settings.


Then you can test code in CRT test host. Furthermore there are many steps ahead to get it through POS & simulate scenario which are mentioned at RetailSDK –> Documents –> SampleExtensionInstructions


AX7 Retail Sdk Handbook

Microsoft Dynamics AX 2012 code upgrade to Dynamics 365 part 1

Hey guys, Today I will be giving you a little bit info on how I am upgrading AX 2012 code to Dynamics 365 for Finance and Operations.

We know that development in D365  is quite different from AX 2012.

In AX 2012 I have a table called PRLParameters, with custom fields. This table is no longer used in D365, its called PayrollParameters. So how do I add my custom fields to it? Extensions!

Right click on the table in the application explorer and select “Create Extension”, this adds an extension of the table to the project.


You can add a new field by right clicking on the extension and selecting Open.


Right click on the fields node –> New –> Enum to add a new field to the extension.


Open the properties of the field to change its name.


Similarly I needed to add the field to the Field Groups. This time right click on the Field Groups node and click New Group.


Give the group a name and add the field you just added


I also need to add custom methods to standard class. I can use extensions in that too but this time I won’t be creating extension from the application explorer. What I do is I directly add a class in my project.

Right click on the project –> add –> new item –> class. Make sure the name of the class ends with _Extension.


How will AX know this is an extension of some class? Just add an annotation on the class: [ExtensionOf(classStr(“Class Name”))]. Now we can add our custom methods in here.


That’s it for this part guys. Hope this will be useful. I will be back with some new stuff as I keep exploring D365.


Integration of Microsoft Azure Blob Storage with Dynamics 365 (cloud) CRM

By integrating your Dynamics 365 Portal with Azure Blob Storage you can enjoy the quality of having a superior or more favorable position to save your files without using dynamics space. It have the same look and feel as you are utilizing the dynamics space. Files like: Web forms, web files, and entity forms are underpinned in its feature.

There will be a need of an account of Azure storage which will be created with the help of Resource manager in the deployment center. If you want to know that how to create Azure Storage Account? then click here.

Once you created the account of Azure Storage the next step is to configure your portal settings that will bind your Azure account with your Dynamics Portal. Here is the path of configuring the portal settings from Your Dynamics 365 CRM instance go to Settings -> Portal Settings 


Add New setting record by setting its name FileStorage/CloudStorageAccount.


To check and insert the Value: Go to your Azure Portal and get the connection string. Following are the steps to get the connection string from Azure portal:

Steps: Sign in to your Azure portal > Navigate to your Storage account > Select Access Keys


In resulting panel > Copy the value from a field named Connection String


Now paste it into the CRM (Portal Settings record) that has been created earlier:


Define Storage Location

For the first time there will be a need to create a Azure blob storage bucket in your Azure portal

In Microsoft Dynamics 365, go to Settings > Portal Settings, and add a new setting record labeled FileStorage/CloudStorageContainerName, applying the name of your bucket/container as the value:


Add Cross-Origin Resource Sharing Rule

Adding CORS rule is mandatory on the Azure Storage account that you are using by following the below mentioned codes. If the CORS rule will not get implemented then the cloud icon will get failed to see by the users and they will see the regular attachment icon:

  • Maximum age (seconds): Specify the max amount time for the browser shall cache the pref light OPTIONS request. For instance, 100.
  • Allowed headers: Specify the request headers that the origin domain may specify on the CORS request. For example, x-ms-meta-data*, x-ms-meta-target*.
  • Allowed origins: Specify your Dynamics 365 domain. For example,
  • Exposed headers: Specify the response headers that may be sent in the response to the CORS request and exposed by the browser to the request issuer. For example, x-ms-meta-*.
  • Allowed verbs: GET, PUT, DELETE, HEAD, POST

What is CORS Rule? Click here to know

By Applying above mentioned settings on Microsoft Dynamics 365 CRM Portal & Azure Blob storage account, you and your clients can enjoy the abilities to download or upload the files directly to/from Azure storage.

Hope this blog is informative for you guys so stay tuned for more exciting features of Microsoft Dynamics 365.

Power BI Configurations for D365 Demo VM (Enabling Tiles and Exposing Demo VM Data)

Today , i will share the Steps necessary  , to integrate power Bi with the DAX 365 Demo VM , so that we can Develop , test , and Demonstrate Power Bi Capabilities on the Demo VM , Without using any Azure Premium Subscriptions .

1) In Order to Make Power BI Tiles Visible on the Work Spaces Follow the Steps , mentioned in this LINK , Redirection URL Will be Devbox base URL , I.e  and Home URL Could be Any Thing , Once that configurations are done , you will successfully be able to pin Tiles From Account .

Note :- Power BI Embedded Content Wouldn’t be Visible with that , it requires a Azure service , that is only available through subscription for multi box Environments  , Although u can download all Embedded Content From LCS  Global Shared Project  Library and can configure for your Custom Work spaces .

2) Now in Order to Expose Demo vm data to Power account you need to Configure Data Gateway on you Demo VM  that can be downloaded from ,Log into your PowerBI account and download Data Gateway available in the Download Section , Left Corner,then follow these Steps

  • When installing the gateway choose the “on premises data gateway” option.
  • You will then be asked to log in to the PowerBI account you’ve created Earlier .
  • You will be prompted to name your gateway and create a gateway recovery key.
  • Log into your PowerBI account. Click on the gear icon and then on “Manage Gateways”.
  • Click on the “Test all connections” button. If the gateway computer is turned on the screen should display the “Online: you are good to go” message.
  • Add a data source to the gateway,Configure it to Point to your local Database , i.e AXDB , or AXDW , use basic as authentication method ,and AOSUser/AOSWebSite@123 username/password combination.
  • Do Refresh Aggregate measurements in Entity Store System Administration -> Entity Store: if you are using AXDW Database.
  • use power BI Desktop to Publish your Content to Power BI .com account .

so , that’s it , after this you would  be able to publish your BI Content on your PowerBI Account  ,and can pin tiles  to your Custom Work spaces With in D365 Environment , In my Next Post I will share how you can Configure Power Apps in Conjunction with Your Demo VM