How to setup Azure Service Bus Relay to use with ACS

By -


In August 2014 Microsoft decided to remove Microsoft Azure Active Directory Access Control (also known as Access Control Service or ACS) from the default Azure Portal setup when creating a new Service Bus Namespace.   Shared Access Signature (SAS) is now default.

Service Bus authentication through ACS is managed through a companion “-sb” ACS namespace and to create this we now need to do it from the Azure Power Shell command line (thanks Microsoft!)

To do this:

Download the PowerShell console
https://azure.microsoft.com/en-gb/documentation/articles/powershell-install-configure/#Install

Open up the Console and type

Add-AzureAccount 

and then type in the email address and password associated with your account (Work or Microsoft)

Once authenticated you need to create the Service Bus Namespace so it's good to go for ACS.

To do this you use the New-AzureSBNamespace command

Parameter Set: Default
New-AzureSBNamespace [-Name] <String> [[-Location] <String> ] [[-CreateACSNamespace] <Boolean> ] [-NamespaceType] <NamespaceType> [ <CommonParameters>]

As an example:

New-AzureSBNamespace "MyNamespace" "North Europe" -CreateACSNamespace $true "Messaging"
As long as the params are correct and the namespace hasn't already been taken then after a minute or two the command line should respond with information about your newly created Service Bus Namespace (you should also see this in the Azure Portal).

Once you have set this up you should be able to configure ACS via this URL

https://<your namespace name>-sb.accesscontrol.windows.net/v2/mgmt/web

As an example:

https://mynamespace-sb.accesscontrol.windows.net/v2/mgmt/web


You can remove the Namespace by typing the following into the PowerShell command line

Remove-AzureSBNamespace "<your namespace name">

 As an example:

Remove-AzureSBNamespace "MyNamespace" 


Links

New-AzureSBNamespace
https://msdn.microsoft.com/en-us/library/azure/dn495165.aspx

Service Bus Authentication and Authorization
https://msdn.microsoft.com/en-us/library/azure/dn170478.aspx

How to install and configure Azure PowerShell
https://azure.microsoft.com/en-gb/documentation/articles/powershell-install-configure/

Comments

  1. Laura Bush17 March 2021 at 23:41

    Lots of valuable data can be taken from your article about Microsoft. I am happy that you have shared great info with us, It is a gainful article for us. Thankful to you for sharing an article like this. What is Microsoft Azure

    ReplyDelete
  2. Laura Bush11 May 2021 at 04:09

    I always check this type of advisory post and I found your article which is related to my interest. This is a great way to increase knowledge for us. Thanks for sharing an article like this. ios app development company online in USA

    ReplyDelete

Post a Comment

Popular posts from this blog

Switching Xamarin Accounts on Mac and Windows

By -
I had a situation where one of our development Macs already had a Xamarin Indie license installed for iOS development.  We then needed to install a client's Business account onto the Mac but unfortunately Xamarin Studio got confused between the two accounts (it showed the new account name but it still said 'INDIE', when it should have said 'Business'). To do a clean switch over you need to do the following:  First make sure you've logged out of your first account.  And login with your new account.  In Xamarin studio you can do this by selecting Xamarin Studio -> Account from the menu bar. Then delete the entire folder listed below.  Windows %programdata%\MonoTouch\License\ %programdata%\Mono for Android\License\ You may need to startup Visual Studio as an Administrator. Mac ~/Library/MonoTouch ~/Library/MonoAndroid When you start up Xamarin Studio, and build the an app it should reset and pick up the new license and ...
Read more

Xamarin Forms - InitializeComponent does not exist in the current context

By -
Image
I was presented with this error whilst developing with Xamarin Forms For me it was simply down to copy and paste :-O.  I'd created a new Xaml Page, which fully qualified was MyNameSpace.MyPage. I then copied in some Xaml which had a different name in the Xaml x:Class attribute (x:Class="NotMyNameSpace.OrPage"). I then tried to compile with our fixing the x:Class attribute and got the 'InitializeComponent does not exist' error. Once I changed the Xaml to match my actual classname (x:Class="MyNameSpace.MyPage") I was back on track and the error went away. Hope this helps. For more information have a look at  forums.xamarin.com The other reason is that you may have created a Shared Xamarin Forms Project rather than a Xamarin Forms Portable project. From Craig Dunn at Xamarin (taken from  Xamarin Forms Forum ) You cannot use Xaml with the Shared Project template with iOS apps (in Xamarin Studio). It's a weird combination to rem...
Read more