• Visual Studio Code. Recommendation: Set File->Auto Save to On in Visual Studio Code
• B2C Extensions
• An xml handling extension, e.g. Red Hat Xml
• (Optionally) make sure your VSCode settings.json file includes the following xml file association

    "xml.fileAssociations": [
        {
          "pattern": "**.xml",
          "systemId": "https://raw.githubusercontent.com/Azure-Samples/active-directory-b2c-custom-policy-starterpack/master/TrustFrameworkPolicy_0.3.0.0.xsd"
        }
      ],

• PowerShell 7.x
• IefPolicies, documentation
• SAML2 test ServiceProvider. Register an app in your B2C with this apps issuer id and rely url

If you have access to Github codespaces, copy the devcontainer folder into the root of your project. This codespace is configured as per above section.

• Register a web app (Token Viewer) with reply url https://oidcdebugger.com/debug; allow return of the access and id token in the Authentication tab
• Create a user (Users->New user->Create user) with B2C's upn, e.g. [email protected] - useful for experiemnting with MS Graph through the Graph Explorer.
• Using Invite user to add your corporate users who will manage B2C development. Give them Global Admin privilege (or other needed for their functions in B2C).
• Use B2C Setup tool to initialize B2C for IEF use.

1. Open VSCode
2. Select Terminal->New Terminal
3. Ensure your PowerShell terminal is using PS 7.x ($host.Version)
4. Create a new folder and change to it (e.g. mkdir myProject; cd myProject)
5. Enter New-IefPolicies
6. Select a starter pack, e.g. SL (Social and local accounts)
7. Enter Connect-IefPolicies <your b2c name; onmicrosoft.com not needed>
8. Followe displayed instructions to sign in
9. Enter Import-IefPolicies
10. The downloaded starter pack will be modified for use in your B2C and uploaded (you can see the modified files in the ./debug folder)
11. Use https://portal.azure.com B2C menus to execute your policies
12. Repeating import-iefpolicies will upload policies modified since the last import and any policies depending on it, e.g. modifying the TrustFrameworkBase.xml policy will result in import of all policies since they are all based on that file.

Use DisplayCntrols starter pack and the following override:

      <DisplayControl Id="emailVerificationControl2" UserInterfaceControlType="VerificationControl">
        <Actions>
          <Action Id="SendCode">
            <ValidationClaimsExchange>
              <ValidationClaimsExchangeTechnicalProfile TechnicalProfileReferenceId="AAD-UserReadUsingEmailAddress" />                  
            </ValidationClaimsExchange>   
          </Action>
        </Actions>
      </DisplayControl>