Placeholder for content...
---title: 'Release notes for Azure Active Directory B2C custom policy public preview | Microsoft Docs'description: A topic on Azure Active Directory B2C custom policiesservices: active-directory-b2cdocumentationcenter: ''author: jorojamanager: krasskeditor: joroja ms.assetid: 4d29e30c-c510-482d-ac2a-4ad7da7ade5fms.service: active-directory-b2cms.workload: identityms.tgt_pltfrm: nams.topic: articlems.devlang: nams.date: 04/28/2017ms.author: joroja
The custom policy feature set is now available for evaluation under public preview for all Azure Active Directory B2C (Azure AD B2C) customers. This feature set is targeted at advanced identity developers building the most complex identity solutions.
The new features introduced in the public review allow developers to perform the following tasks: 1. Author and upload custom authentication user journeys using custom policies - Describe user journeys step-by-step as exchanges between claims providers - Define conditional branching in user journeys 2. Integrate REST API-enabled services in your custom authentication user journeys3. Add federation with identity providers compliant with the OpedIDConnect standard4. Add federation with identity providers adhering to the SAML 2.0 protocol
1. Use of the new features is encouraged for evaluation purposes only2. The new features are not intended for use in a production environment3. Service level agreements (SLAs) do not apply to the new features4. Support requests can be filed through the regular support channels5. There is no promised date for general availability 6. At our discretion, and for any reason, Microsoft may flag and reject or restrict scenarios and user journeys that exceed the scope of the Azure AD B2C product charter to serve as a customer identity and access management (CIAM) platform
Manual policy configuration grants lower level access to the underlying platform of Azure AD B2C and results in the creation of a unique, fully customizable trust framework. The near infinite permutations of custom identity providers, trust relationships, integrations with external services and step-by-step workflows place greater demands on the advanced developers consuming them. In order to fully benefit from the public preview, we suggest that developers consuming the custom policy feature set adhere to the following: - Become familiar with the configuration language of the Identity Experience Engine (IEE) and key/secrets management- Take ownership of scenarios and custom integrations - Perform methodical scenario testing - Follow software development and staging best practices with a minimum of one development/testing and one production environment - Stay informed about new developments with the identity providers and services you integrate with, for example, keep track of changes in secrets, scheduled/unscheduled changes to the service and so on- Set up active monitoring and monitor the responsiveness of their production environments- Keep contact emails current and stay responsive to the Microsoft live-site team emails- Take timely action when advised to do so by the Microsoft live-site team