Windows Azure team posted three important announcements related to the Access Control Service:
Extension of the promotional period of Access Control Service to December 1, 2012
“We are extending the promotional period and will not charge for the use of the Access Control Service (both ACS 1.0 and ACS 2.0) until December 1, 2012,” stated Windows Azure team.
Availability of the Access Control Service 1.0 Migration Tool
Customers now have an easy way to migrate ACS 1.0 namespaces to ACS 2.0 and try out the new ACS 2.0 features without adversely affecting their existing solutions. Available today is a new “Access Control Service 1.0 Migration Tool” that allows ACS 1.0 namespace owners to do the following.
This tool can be used to migrate regular ACS 1.0 namespaces, in addition to the ACS 1.0 namespaces used by the Service Bus:
- “Copy the data from an ACS 1.0 namespace to a different ACS 2.0 namespace. This enables inspection and testing of the migrated settings on a different ACS 2.0 namespace without affecting the original ACS 1.0 namespace or applications that rely on it.
- Migrate the DNS name from the original ACS 1.0 namespace to the new ACS 2.0 namespace with no service downtime, after any optional testing and verification has completed,” revealed Azure team.
Deprecation of Access Control Service 1.0
ACS 1.0 will be officially taken offline on December 20, 2012. “This 12 month period along with the ACS 1.0 Migration Tool allows customers with ACS 1.0 namespaces to proactively migrate to ACS 2.0,” said the Azure team.
“All customers with ACS 1.0 namespaces are encouraged to migrate to ACS 2.0 in advance of December 20, 2012 to avoid potential service interruptions.”
You can download the Access Control Service Migration Tool here, and read the MSDN Guidelines for Migrating an ACS 1.0 Namespace to an ACS 2.0 Namespace.
Also, the team announced that as part of the December 2011 Labs of Service Bus, Microsoft is adding a brand-new set of “Enterprise Application Integration” (EAI) capabilities which includes bridges (commonly referred to as pipelines), transforms, and hybrid connectivity.
“One can configure a bridge using a simple UI designer surface provided as part of Microsoft Visual Studio,” the team informs.
“To enable this experience download the SDK from here. After installing the SDK go to Visual Studio and create a new EAI project which you can find under Visual C# -> ServiceBus. After this follow the steps mentioned here (for XML One-Way Bridge) or here (for XML Request-Reply Bridge) to configure and deploy a bridge,” the team said.