Planky

• Windows Azure Active Directory Cartoon

  Apr 05, 2013 at 3:29 AM

  Hi BraveStarr,

  Yes - that's exactly right. In federated environments, the authentication itself is performed by the "identity provider" (IP). It the creates a token which is signed and forwarded to the consumer who trusts it. It means the app and WAAD don't do the password management. That is done by the folks who know it best - the IT admins INSIDE your organisation. If somebody forgets their password, they get it changed in AD. If somebody leaves the org, when you disable their account in AD, they are automatically locked out of not only the AD-integrated environments, but also the environments that are federated with the local AD - such as WAAD based apps.

  There's a video which describes the process (using the "old" Ofice 365 directory and apps - exactly the same principles though) here:

  http://blogs.msdn.com/b/plankytronixx/archive/2011/01/25/whiteboard-video-how-adfs-and-the-microsoft-federation-gateway-work-together-up-in-the-office-365-cloud.aspx

   

• Windows Azure Active Directory: Control Access to Windows Azure

  Mar 13, 2013 at 2:40 PM

  Hi Dean,

  I can set you on the right track - email me a splank@microsoft.com. I just won't be able to get involved in detail - I'm in the UK. I can put you on to a partner who know this very well - UK based but they have international offices.. I don't know any swiss partners in this cloud/identity space...

• Windows Azure Active Directory: Control Access to Windows Azure

  Mar 13, 2013 at 2:37 PM

  Hi CodeGrue - I'd recommend you watch a video I made to explain possibilities between on prem AD and Office 365 (AKA Azure AD) Dirsync. The click-by-clikc screencast first: http://blogs.msdn.com/b/plankytronixx/archive/2011/01/24/video-screencast-complete-setup-details-for-federated-identity-access-from-on-premise-ad-to-office-365.aspx

  and the theory second:

  http://blogs.msdn.com/b/plankytronixx/archive/2011/01/25/whiteboard-video-how-adfs-and-the-microsoft-federation-gateway-work-together-up-in-the-office-365-cloud.aspx

• Windows Azure Active Directory: Control Access to Windows Azure

  Mar 13, 2013 at 2:32 PM

  Hi mrpaulb.

  You are describing a feature of IE (since IE8 I think) where if you have ANY instance of IE open, it maintains the authentication cookie across all instances. You could alternatively open private tabs.

• Windows Azure Active Directory: Control Access to Windows Azure

  Mar 08, 2013 at 11:33 AM

  Do you mean you had to try 3 different browsers to get the button to appear?

  Anyway I'm glad you have it all working now.

• Windows Azure Active Directory: Control Access to Windows Azure

  Mar 06, 2013 at 3:37 AM

  Hi mrpaulb,

  On re-reading your opening post I can see that you tried to log in to Azure using a standard LiveID.

  To get those new AD features enabled in the portal, you need to log in to the Azure portal using your WAAD account. That means you need to CREATE THE WAAD TENANT FIRST. Go to 11:18 in the video and be sure to follow that initial step. Some steps are not shown in that part because it was recorded on a pre-production system. You need to associate a WAAD tenant with the Azure subscription of the admin of the tenant. Right now, that means creating a new trial subscription. In the spring that restriction will be lifted and you'll be able to associate an existing Azure subscription with your tenant.

  I've created a short video with all the steps here http://aka.ms/WAADsubscription... Hope this helps you.

   

  Thanks for your enthusiasm Mike.

• Windows Azure Active Directory: Control Access to Windows Azure

  Mar 04, 2013 at 12:45 PM

  Give it a try now 

• Windows Azure Active Directory Cartoon

  Feb 09, 2013 at 2:00 AM

  Thanks Dave - I really appreciate your enthusiasm.

  Tony - Ha ha! I guess that's the "richness of humanity"

• Windows Azure Active Directory Cartoon

  Jan 03, 2013 at 1:06 PM

  Thanks Liam.

• Windows Azure Active Directory Cartoon

  Dec 24, 2012 at 3:23 PM

  1. Yes, that's exactly what you can do.

  2. It was recently announced that WAAD is free. Office 365 licenses, which you apply to WAAD users still have to be paid for, but the users you create in WAAD are free. To manage the users in Office 365 (remember the users are now in WAAD) go to activedirectory.windowsazure.com and log in using your Office 365 administrator account.

  Remember the difference between free users in the directory and Office 365 licenses that you have to pay for. A license is then "attached" to one of the free users in the directory. The users are free, the Office 365 services provided to any users are not free.

   

  You can have some users in your WAAD that have O365 licneses applied and some users that don't have them applied.

  Hope that explains.

   

  Planky

See more comments…