Hi everyone, George Moore as well as Neelamadhaba Mahaptro here from a Live Services team. For a past multiform months a Live Framework as well as Windows Live ID teams have been operative together to capacitate warden formation of Windows Azure with Windows Live ID, Active Directory as well as OpenID. This work shipped as a partial of a CTP releases during PDC2008. The formation is done probable by a multiple of a Azure Services Developer Portal, Microsoft Federation Gateway, as well as a Microsoft Services Connector.
This formation enables a following temperament scenarios “out of a box” with Windows Azure:
- Easily soak up Live services in to Windows Azure applications
- Data portability: entrance interpretation from Windows Azure that belongs to Live users (contacts, Mesh data, etc)
- Accept hundreds of millions of Windows Live IDs in to Windows Azure apps – users do not need a brand brand brand brand brand brand new ID
- Accept federated commercial operation users in to Windows Azure applications:
- Microsoft has a warden resolution for Active Directory-based businesses
- Non-Active Directory businesses can combine with a small additional work
- Accept federated identities around OpenID providers
In addition, a Windows Live Tools as well as a Cloud Computing Tools for Visual Studio were written to yield seamless formation in to this altogether process, together with a auto-provisioning of a compulsory temperament bindings in to a ASP.NET controls.
This blog post visually walks by a altogether developer lifecycle knowledge in adding Windows Live ID or Active Directory authentication in to a Windows Azure application, followed by a end-user knowledge in immoderate such an application. For a finish demo for how to set up a Federation Gateway as well as a Services Connector, greatfully watch a Connecting Active Directory to Microsoft Services display from a PDC.
Developer Life Cycle Experience
Step 1: Developer visits a Azure Services Developer Portal to emanate their brand brand brand brand brand brand new Azure project.
Developer presses “New Project” in a top left, as well as afterwards selects “Hosted Services for Windows Azure”:
Step 2: Developer selects a tab for their project, along with an discretionary description, as well as presses “Next”:
Step 3: Developer selects a self-centredness DNS name of their brand brand brand brand brand brand new use that will crop up inside of a cloudapp.net domain for Windows Azure:
Step 4: The portal right away automatically creates an dull hosting project, registers a brand brand brand brand brand brand new domain name with LiveDNS, as well as creates a compulsory temperament bindings for after connectivity to Windows Live ID. These bindings embody a Application ID, Secret Key as well as Return URL.
The developer was not compulsory to manually come in these temperament bindings – they were combined as well as purebred automatically by a portal in to a Windows Live ID service, as well as have been right away ready for after use:
Step 5: Now a developer contingency writer as well as sustenance their application. They launch Visual Studio as well as name File: New Project: Blank Cloud Service:
Step 6: Add a brand brand brand brand brand brand new Web Role to a project:
Step 7: Choose Windows Live for a brand brand brand brand brand brand new template:
Step 8: The developer is afterwards since a vacant engineer page inside of Visual Studio. The Windows Live use controls for ASP.NET crop up upon a left (MessengerChat, IDLoginView, IDLoginStatus, Contacts, Silverlight Streaming as well as Virtual Earth).
These have all been mutated to work with a Windows Azure certitude model:
Step 9: Developer drags as well as drops a IDLoginStatus ASP.NET carry out for Windows Live ID web authentication onto their web page. Note a Visual Studio intelligent tab charge industrialisation object entitled “Configure Application ID”:
Step 10: When a developer selects a “Configure Application ID” menu object for this ASP.NET control, we automatically begin a Trident browser window inside of VS that points to a Azure Services Developer Portal.
This requires a developer login to collect a temperament bindings that were automatically combined in Step 4.
Step 11: The portal, regulating inside of a Trident window inside of Visual Studio, presents a made easy list of all formerly combined Azure projects. Windows Azure projects have been shown with a Hosting Service icon, whilst Live Services projects have been shown with a Live icon.
When a developer selects a scold plan as well as presses “Ok”, a portal transmits a compulsory Application ID as well as a Secret Key to Visual Studio. This creates a treble contracting in between a ASP.NET control, a Windows Azure DNS name, as well as a Microsoft Federation Gateway:
Step 12: The developer afterwards compiles a plan in Visual Studio (via a Windows Azure SDK) as well as uploads it to Windows Azure (via a portal).
Once a focus has been promoted to Production by a developer, a focus is afterwards regulating underneath a domain name purebred for a temperament bindings as well as will be means to entirely experience in any of a Windows Live ID temperament services:
End User Authentication Experience regulating Active Directory
Step 1: The finish user visits a website hosted by Windows Azure configured in a stairs above. The finish user presses a “Sign In” couple to substantiate this site opposite their corporate Active Directory credentials:
Step 2(a): When a “Sign In” symbol is pressed, a user is taken to a customary Windows Live ID sign-in page.
In this Step 2(a) example, Mary has never prior to sealed in to this site regulating her Active Directory credentials. Because a “fabrikam2.com” domain has been formerly purebred as well as administered by a Microsoft Services Connector, Mary is since a event to name “Partner ID” in a Windows Live ID menu, sort her email address, as well as afterwards press a “Go there” button. Windows Live ID knows a place of a Fabrikam AD authentication page around MSC:
Step 2(b): In pick Step 2(b), Mary had formerly real to a Fabrikam site, as well as so Windows Live ID remembers her ID. When she presses her name, she is rught away taken to a Fabrikam corporate site for authentication:
Step 3: Redirection occurs to Fabrikam’s Active Directory authentication page upon their corporate network.
Mary sorts her AD credentials:

Step 4: Once a Fabrikam site has scrupulously certified Mary’s credentials, a redirection happens behind to a strange Windows Azure-hosted site with a singular user ID provided. This site can right away without delay implement Fabrikam corporate resources around Mary’s certification regulating a Federation Gateway:
Questions? Comments?
If we have any questions or comments, stick on us in a Windows Azure forum.
