In previous article, we have looked at the possibility to connect Dynamics 365 on-premise directly with Azure AD, which is on one hand really cool, on the other, it doesn’t provide all the features like mobile apps integration. In this article, we are going to explore a production ready solution by leveraging Active Directory Federation Service and Azure AD as a Claims Provider Trust.
You may have used direct links to specific view in the past but you don’t see these sub areas now in your UUI App.
You could have achieved this by using a special URL in the sitemap sub area with the view’s parameters and Dynamics managed to detect your intent when rendering the application navigation.
This is still working but the format has changed for UUI Apps.
While Dynamics 365’s documentation is full of articles and tutorials about setting it up with Active Directory Federation Services, there is no mention of using Azure Active Directory for Single Sign On. Many replies in communities say that this is not possible, but today we are going to prove them wrong.
I came across a strange issue when trying to upgrade CRM deployment to Microsoft SQL Server 2017.
Important note: It is not listed as a supported version https://technet.microsoft.com/en-us/library/hh699754.aspx
And here is probably why.