Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 release wave 1Discover the latest updates and new features to Dynamics 365 planned through September 2020
Release overview guides and videos Release Plan | Preview 2020 Release Wave 1 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
following question? What is the right way to create the ACS Namespace for the companion apps within azure?
Taken from the whitepaper:
Configure the Microsoft Dynamics AX environment for companion apps (Version from February 2015)
Create a new Windows Azure Service Bus namespace with a companion ACS namespace
There is a note:
Note: As of August 2014, you cannot use the Azure Management Portal to create the service bus namespace for use with Microsoft Dynamics AX companion applications. You must use Azure PowerShell to create the service bus service namespace.
You should instead launch the following PowerShell command:
New-AzureSBNamespace –name “InsertNameHere” –location “InsertRegionHere”
Will this create an ACS namespace or an SAS namespace?
According to another post in the community (newer)
there is a note that you have to add the -CreateACSNamespace $true to the commandline
Is the -CreateACSNamespace $true missing within the whitepaper? Or do I have to create the namespace without the -CreateACSNamespace parameter?
In my opinion, omitting this one will create an SAS namespace.
Can someone clarify.
Yes, I think it's missing in the whitepaper.
Things are constantly changing in Azure, therefore whitepapers get outdated really quickly.
these were my thoughts.
Business Applications communities