A B2C Tenant Where Its Customer Directory Should Live, on the Tier the Features Need

An Azure AD B2C tenant created where its customer directory should live, on PremiumP1 or P2, linked to the subscription that pays per monthly active user. Data residency and the onmicrosoft.com name are chosen once and cannot change; user flows, policies and app registrations are configured inside the tenant with an azuread provider pointed at the exported tenant ID.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

terraformAzureSecurity & Identityv1.0.0static-validated

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

A DDoS Network Protection Plan with Its Price Written Down A Firewall that Blocks rather than Narrates A Managed AD Domain with Legacy Protocols Off and Its Prerequisites Created A Private Purview Account Without the Managed Event Hub, Granted Read on Its Sources A WAF Policy that Blocks rather than Narrates An NSG that Is Associated, Names Its Sources, and Ends in a Deny Azure Bastion + Hardened Jumpbox Defender Plans that Are Actually On

The same job on other clouds

Customer Identity on other providers. Useful when the cloud is still open, or when you are pricing a second one. How far a comparison like that can be trusted is covered in comparing clouds.

Cognito User Pool & App ClientAWS Customer Sign-In with Anonymous Accounts Off, MFA Offered and Sign-Ups ThrottledGoogle Cloud

Installing it

module "azure_b2c" {
  source  = "www.iac-bazaar.com/iac-bazaar/azure-b2c/azure"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.