Currently ServiceBus is billed monthly per connection, with prices that can go lower with packs, but nevertheless far too expensive for some low traffic/usage scenario.
In my scenario the connection is between client applications and the Azure services, must be active all the time the application is working (normally 8 hours a day) and "real" communication between the two, interaction and data transfer, happens unfrequently and move little data.
In this scenario the current pricing strongly limit the chance to use the ServiceBus, even if it is an enabling feature.
A pricing model more proportional to time and usage would really help

Provide out of box support for Identity Federation using ACS. Justin Smit already posted a sample "ACS integration with Windows Live ID & Facebook Connect" on his blog and ServerSideWebIdentities.zip is also available for download.

AppFabric team should generilize this sample and expose endpoints like FaceBookFederation.aspx, GoogleFederation.aspx, MicrosoftActiveDirectoryFederation.aspx right inside AppFabric, not as a sample.

We want Content Based Routing in Azure App Fabric. How can you take it out of it? A service Bus is not complete without one. I suggest we have it for XML/JSON type messaging, and it must be durable!

I mentioned to customer that we can host their services in App Fabric, and we can leverage Content Based Routing. I am somewhat dissapointed when I worked on the SDK, that this is not their! So what do I do? I do not think using BizTalk just for the routing capabilties is suffucient, App Fabric MUST have this built in, if it is to surivive and beat the competitors. It is application driven and shouls therefore be able to intrinsically route certain message types based on type or content!

Currently, wreply is not supported. When an ADFSv2 user signs out they get a dead end page like this:

https://tlsadmin.accesscontrol.windows.net/v2/wsfederation?wa=wsignoutcleanup1.0&wreply=http://localhost:2600/Account/SignIn

The wreply parameter is an industry standard and should be implemented:
http://social.technet.microsoft.com/wiki/contents/articles/ad-fs-how-to-invoke-a-ws-federation-sign-out.aspx

http://msdn.microsoft.com/en-us/library/bb608217.aspx
http://download.boulder.ibm.com/ibmdl/pub/software/dw/specs/ws-fedpass/ws-fedpass.pdf

The second ( related )issue I’m having is that I’m trying to deauth ADFS and Facebook. I need to use the wreply parameter to redirect the user off the ACS host, and back on some “normal” user page.

You might ask why am I redirecting to the ACS? It’s because Facebook is requiring me to. And since the Facebook TOS requires me to implement sign out features (that actually log someone out of facebook, not just my RP) then I have to redirect them to the ACS signout page.

The issue is that the user experience is horrible. They dead end at a page that tells them to close the browser windows. This is a no-go for me since my application is used in Kiosks where it’s not possible to close the browser window, or navigate using the url. Plus it’s bad design.

Hi,
Cloud Drive is very helpful for those who are using standard NTFS APIs like us.

Actually we are working on application which will run both on cloud and on local machine. We need to store and use our large amount of data which will be used by our application to azure storage. and both local and cloud running application have to save and retrieve data from one location. Initially we are concentrated on blobs but looking at cloud drive we want to shift on to it.

In terms of Cloud Drive and our application running in cloud its awesome.
But But the application running in local environment have no access to cloud drive.

So Cloud Drive functionality shoud be available Locally in future ??

Sorry to be a bit snarky here. I initially was extremely excited that Microsoft was adopting uservoice, this is a great step forward, but without showing activity in accepting ideas people may turn elsewhere. In the same time competitors such as Amazon have added considerable new features, I'm hopeful that Azure will be a great player in the market.. seeing some action here would certainly help.

Managed Services Engine is a wonderful capability that allows MS stack to have a native SOA intermediary. What is great about it built up on WCF, it does work with the AppFabric and more importantly allows non WCF applications to be integrated to AppFabric out of the box.
Microsoft is really bad in promoting it and very few people know about it.
Please add one or two labs to the SDK how to expose an existing endpoint via AppFabric + MSE (cut and paste Arron’s article if you wish) and start promoting it! It is very useful (and missing block) that you need to promote more!