Update AD B2C Cusom Policy without impacting production

NigelW61 41 Reputation points
2020-12-14T05:44:56.687+00:00

Does anybody have any recommendations about how to update B2C custom policies without potentially impacting customers using the service.

For instance, in a feature release you may change the Base policy and SignUp policy. Once you update the Base policy the currently deployed SignUp may not be compatible and cause errors for anyone trying to use the Sign Up user journey.

Hopefully the upload of the new SignUp policy would happen quickly so the window of potential failure would be short, however if the Signup policy upload failed for some reason you would have a full system outage.

How do people get around this.

Azure Active Directory External Identities
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. AmanpreetSingh-MSFT 55,531 Reputation points
    2020-12-14T08:08:50.98+00:00

    Hi @NigelW61 · Thank you for reaching out.

    Azure AD B2C supports maximum of 200 files to be uploaded to the Identity Experience Framework blade. So, you can have two separate sets of Base/Extension/RP files with same content but with different policy names - One for production and other for testing/dev purpose. You can use naming convention like TrustFrameworkBase-Prod and TrustFrameworkBase-Dev, for example.

    Always perform testing on the test/dev policies and once you are done with the testing and confirmed that the changes are not causing any issues, you can modify the production policies accordingly and then upload & override the files for production usage.

    -----------------------------------------------------------------------------------------------------------

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.