Update AD B2C Cusom Policy without impacting production

Question

Update AD B2C Cusom Policy without impacting production

NigelW61 41

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.

Answer 1

AmanpreetSingh-MSFT 55,406

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.

NigelW61 41 Reputation points

2020-12-14T09:41:44.28+00:00

Thanks for the reply but that's not quite what I meant.

I was referring to an update to the production policies, i.e. when adding a new feature or modifying a user journey.

We have a lower environment which is where we test the changes prior to promoting to production.

We can't have different names or else the RPs would need to change too which would require an outage.

Thanks
AmanpreetSingh-MSFT 55,406 Reputation points

2020-12-14T13:41:30.803+00:00

@NigelW61 · As you already have a separate Dev tenant to test the policies, If you want to be sure that the policies are compatible with the production tenant as well, you can have a complete chain of files (RP > Extension > Base) for Dev as well as for Prod in the same tenant and test the Dev chain of custom policy before updating the prod one.

Unfortunately, there is no other easy/convenient option available for this purpose.

Update AD B2C Cusom Policy without impacting production

1 answer

Activity