This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 89%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESK%3C/text%3E%3C/svg%3E)
Hi, I am using the free trial for azure ad b2c and using custom policies for sign up and sign in flows. As the free trial period is only for a month, so what will happen after a month? As I have observer normal user flows works even after the trial period is ended. Similarly, will the custom policy works which is already uploaded?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 23%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
After the trial period ends, Azure AD B2C typically reverts to the free tier, which is available indefinitely. This free tier includes basic functionality.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(80, 13%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBB%3C/text%3E%3C/svg%3E)
Hello Sonam K
Thank you for posting your query in the Microsoft Q&A Community.
Please be informed basic user flows will continue to work after the trial period , but custom policies typically require a paid subscription to continue functioning. When your free trial period ends, several things will happen depending on whether you choose to upgrade to a paid subscription or not. Here's what you can expect:
Azure AD B2C includes a free tier that provides 50,000 monthly active users (MAUs) and basic functionality without a time limit.
If your usage is within this free tier, you can continue to use Azure AD B2C without any cost even after the trial period ends. However, If your usage exceeds the free tier limits, you will need to upgrade to a paid subscription to continue using the services without interruption.
Custom policies also known as Identity Experience Framework policies are more advanced features that are not included in the basic free tier.
During the trial, you have access to these advanced features to test and implement your custom sign-up and sign-in flows.
After the trial period, if you are within the free tier limits, basic user flows will continue to work. However, custom policies may be restricted unless you upgrade to a paid subscription that supports advanced features.
Also, custom policies that were uploaded and used during the trial may stop working unless you upgrade to a paid subscription that includes support for custom policies.
Lastly, you will still have access to the portal and can see your configurations, but the execution of custom policies will be restricted.
Let me know if further assistance is required.
Babafemi
Hi, Thank you for the response. I am observing another issue where if I am using the application which i created for my use using normal user flows. In this case, it's working if I am using my gmail account or personal account for SSO microsoft. But when I am trying to use my work email address, it's not working and throwing error. So for this custom policy is required or it's achievable through user flows as well?
As per my understanding, when using "Microsoft" as the identity provider, we need to configure the Client ID and client secret. However, this configuration will redirect to the login.live.com portal, which only allows personal Microsoft accounts. If we are configuring any custom IDP, we have to provide the metadata URL with the tenant ID. In that case, it will only allow users available in that specific tenant, as it does not permit the use of the metadata URL "https://login.microsoftonline.com/common/v2.0/.well-known/openid-configuration".