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

Post a comment

Popular posts from this blog

System.UnauthorizedAccessException error with Visual Studio and Xamarin

By -
When you try and install Mono.Android in Visual Studio for the first time you may find that you're presented with an error similar to the one below: System.UnauthorizedAccessException: Access to the path 'C:\ProgramData\Mono for Android\License' is denied. at Xamarin.Components.Ide.Activation.ActivationService.GetErrorWorkflow(LicenseSyncResult[] results, Boolean ignoreSyncErrors) at Xamarin.Components.Ide.Activation.ActivationService.<GenerateFullWorkflowSequence>d__88.MoveNext() at Xamarin.Components.Ide.Activation.ActivationDialog.DisplayWorkflowStep(ActivationWorkflowStep step) at Xamarin.Components.Ide.Activation.ActivationDialog.<>c__DisplayClass13.<StartSpinnerTaskAndScheduleContinuation>b__12(Task t) If you close down VS and run it again as an Administrator it should sort the issue out. Remember activation of your Xamarin licenses doesn't actually kick off until you run the project for the first time. If you're still having activat
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