It would be great if we could easily monitor our workflows running (or not) in the cloud.

PortBridge and Reverse Web Proxy allow publishing of legacy services (and applications) via Service Bus, without altering their endpoints.
An example can be found here ( http://blogs.msdn.com/clemensv/archive/2009/11/18/port-bridge.aspx ).

The nameidentifier claim containing a made up ID unique to my application is not sufficient for authenticating a user. With no way to get additional user identifiable information, a user could authenticate with Live and then fill out a local profile on my application for whomever they wanted. They could claim to be Bill Gates, I would have no way of verifying that based on the nameidentifier claim coming from LiveID.

$45/mo for 128MB cache is cost prohibitive.

May be useful for developers to have an AppFabric Cache emulator, for instance.

Currently, I guess there is no WS-* support in ACS for us to do multi-tenant federation from Web role.
I have seen examples for REST services but how about web role?
We can do this on premise by ADFS adding whr parameters to the querystring etc.. but how to do it on azure using ACS and web role.

This is must for any SaaS application

When selling software applications we are often at the mercy of a customer in regards to what platform they want to run on. Some customers will want internally hosted Win Server solutions, others will want Azure and others will prefer other Cloud solutions. Having to maintain different code bases for different platforms adds a maintenance overhead and level of duplication we could do without. It would be nice if the AppFabric libraries were unified so that the same code could be deployed to Windows Server or Azure

Currently, only the primary administrator for a subscription can access the ACS portion of the portal for namespaces. Co-administrators receive an error message when trying to do so. Co-administrators should have the same ability as the primary administrator.

In my case, the owner of the company I work for is the administrator for the subscription. However, among other things I am in charge of all configuration of Azure. To facilitate this, he made me a co-administrator. Currently I cannot configure ACS when logged in under my own account.

The ACS authentication system does not implement widely used anti-hacker HTTP headers.

Please see the following links for a list of missing HTTP headers:

http://security.stackexchange.com/q/8480/396
and

http://social.msdn.microsoft.com/Forums/en-US/windowsazuresecurity/thread/eab4b53e-438b-4b20-8933-ae88e2f3610f?prof=required

Federated security being so important, it should be possible to enable federation through the service bus, using TCP relay to allow for direct connection. There should be a binding for this that works. Or ,at least a sample that works.

Provide native security services in AppFabric such as XML firewalling (structure, grammar, semantics, algorithms, injections, etc), similarly like other XML virtual appliances .
Ideally, it would great if interception can be implemented between client and the end service by calling Worker / Web Role on Azure to perform this functionality (an possibly policy enforcement) – Customer may or may not to choose to deploy this solution at their own cost. The firewall can be reference implementation on codeplex and / or fully managed service provided by Microsoft.

It would be nice if code did not even require recompiling to be hosted on premise or in cloud

Idea created Sep 8, 2010 by Lars W. Andersen

It is a problem operating the Azure account, when only one admin have access to it. In case of emergencies, vacation, etc. it is needed to share access to one account.

[moved from Windows Azure Feature Voting]

In fact, WCF in the n.NETCF needs a complete overhaul to include all the bindings and formatters/encoders.

I'd like to see a single Issuer store for both ACS configuration and the service bus configuration. SInce you already have to grant issuers specific rights for the service bus I don't see why I need to maintain two stores of issuers for both access to the service bus AND for my own services. I should be able to define an issuer once, then grant them rights to my service bus and/or ACS from there.