Cannot see namespaces in AppFabric

Question

I am new to Azure, and learning a lot everyday by doing. Recently i needed to deploy a Microsoft Dynamics CRM plugin for our 2011 online. This required me to create a new namespace in our Azure subscription's AppFabric. While creating namespace, i could not see the subscription in the dropdown though I am the co-administrator in our subscription.

Can anyone help ?

 

Answer 1

Hi,

AFAIK, so far the "Co-Administrator" access is not extended to AppFrabric services so you can't do what you want. The "Service Administrator" is the one who can manage it.

You can only assign co-administrator to manage Hosted Services, Storage Accounts and CDN services. Please refer: http://msdn.microsoft.com/en-us/library/gg433112.aspx

HTH,

---

Mahesh Devjibhai Dhola [Please mark best and acceptable replie(s) as the ANSWER(S)]

Answer 2

Being a user, i reserve my right to say that this is NOT at all a sensible name for this role, absolute NON-SENSE. The term "Co-Administrator" would actually appear as a role having which one could also do things that an administrator could do.

Now we have it, lets accept it, BUT tell me how can we have multiple service administrators on a subscription, so if one of our administrators has fallen sick or out and away, we do not have to keep his / her password. What big is it a deal if there are multiple service administrators.

One basic thing that i fail to understand is that, if you have a team of developers who wish to work with AppFabric, is there any role besides the Service Administrator who could create namespaces ?. I understand that things need to be restricted from deployment on production until a specific kind of an approval from a person in administrator role is received, but that does not mean that development should be restricted. This role actually applies to deployment related tasks, like restricting deployment just to staging and not let to production.

 

Answer 3

Hi,

I am not from Microsoft so can't comment but here is my thinking,

It's not so long when even "Co-Administrator" feature was not available and introduced this change in Management Portal (new management portal) along with the Windows Azure SDK 1.3 release in Nov 2010. So seems like these services are evolving gradually and hopefully the Co-Administrator role would be extended to access other services as you wish but not for now.

I don't see any option other than sharing the Windows Live ID credentials of Service Administrator to access AppFrabric as of now even if it's not the advisable, secure and the desirous way.

One suggestion, give your vote to the following request for the same which you want to do on "Windows Azure Feature Voting Forum": http://www.mygreatwindowsazureidea.com/forums/34192-windows-azure-feature-voting/suggestions/1358849-access-control-for-co-sub-administrators?ref=title.

HTH,

---

Mahesh Devjibhai Dhola [Please mark best and acceptable replie(s) as the ANSWER(S)]

Answer 4

I believe this is being worked on. The same limitation extends to SQL Azure permissions. I believe part of the reason for this is that these products are developed by seperate product teams. Each team has their own list of features and schedules so unless a great deal of effort is expended to coordinate releases, these types of gaps are going to happen.

Call it a by-product of MSFT adopting a more agile and rapid product lifecycle. :)