Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
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 | Talent TechTalks | Upcoming TechTalks
ACS is an Azure service that provides an easy way to authenticate users to access web applications and services without having to add complex authentication logic to code. While SAS is used to access resources in storage account which includes both primary and secondary keys.
Azure Account should be added in PowerShell with respective User’s Credentials.
Note: For Adding account In Microsoft Azure PowerShell refer to following link:
ACS Key can be created using Azure PowerShell following command,
New-AzureSBNamespace GravityDocument -Location “Southeast Asia” -CreateACSNamespace $true -NamespaceType Messaging
Command requires Service Bus Namespace Name, Location and Messaging type.
This ACS Key information can be seen on Microsoft Azure Account with that corresponding service bus namespace provided in the command above.
Once the Namespace is created the corresponding Connection Information is available at the bottom under Connection Information.
Here for SAS Key we have created Queue inside the namespace.
Now Queue can be created inside this specified Namespace, for that follow the below screenshots
Specify the required details i.e. the Queue name under the specified namespace.
Now since the queue is created SAS key can also be generated with different permissions like Manage, Listen & Send.
So under Configure option, under Shared Access Policies specify the name and permission to be given for that particular queue.
Now SAS key for that particular queue can be obtained from Connection Information of Queue with SAS key.
Thus, we can Create ACS and SAS requests as per requirements using Microsoft Azure PowerShell and Azure Portal.
The post Creation of ACS and SAS appeared first on CloudFronts - Microsoft CRM | AX | BI | Azure.
Business Applications communities