Migrating Azure ACS namespaces to Google OpenID Connect
Published Sep 06 2018 07:59 PM 374 Views
First published on CloudBlogs on Mar, 05 2015
Howdy folks, (Short blog post today since my right arm is in an immobilizer.) A couple of weeks back I wrote about our plans for the Azure Access Control Service (ACS). Today we pushed out an update to ACS that will help you migrate your namespaces to use Google's OpenID Connect implementation. In order to assure no downtime, we need you to complete this migration by June 1 st 2015. So I'd like to urge you to get started right away! You'll find detailed guidance here: http://go.microsoft.com/fwlink/?LinkId=526240 . In all but one case, migration will not require code changes. In that one exception case, your application needs to be able to handle an additional claim type in the ACS token; this may not need code changes if the application can already can do this. We want to help to make your migration as seamless as possible, so if you have any questions, you can also post them on Stack Overflow with tag 'acs-google' and we will get right back to you. As always, we look forward to your feedback and suggestions.

Best Regards,

Alex Simons (Twitter: @Alex_A_Simons )

Director of Program Management

Microsoft Identity and Security Services Division

P.S.: Thanks to all of you who sent emails, texts and tweets wishing me a successful shoulder surgery. Everything went well and I'm propped up in a nice recliner at home.

Version history
Last update:
‎Sep 06 2018 07:59 PM
Updated by: