I am building several custom policies and I need to come up with a meaningful naming convention for the pack of files relates to a specific group of files come with Starter Packs
What are the rules and repercussions around PolicyId I need to define on top of each policy xml file (shown in the snippet below)
<TrustFrameworkPolicy xmlns:xsi="" xmlns:xsd="" xmlns="" PolicySchemaVersion="0.3.0.0" TenantId="yourtenant.onmicrosoft.com" PolicyId="B2C_1A_PasswordReset" PublicPolicyUri=""> 1 Answer
I have never come across any issue in terms of names.
If you don't add "B2C_1A_" to the name, it is added when you upload it.
I leave the base and extension files alone.
Then I have my own extension policy file where I add custom code (maybe overriding methods) and also have policy files for common themes e.g. API, federation, MFA etc. The name reflects the function.
The maximum depth for inheritance is 10 policy files.
5