search

Azure / azure-saas

The Azure SaaS Development Kit (ASDK) provides a reference architecture, deployable reference implementation and tools to help developers, startups, ISVs and Enterprises deliver their applications as a SaaS service. A platform for platform creators.
https://aka.ms/azuresaasdevkit
326 stars 239 forks source link

Deployment with wrong SKU - PremiumP1 instead of Standard #256

Closed leo-schick closed 5 months ago

leo-schick commented 5 months ago

Describe the bug I followed the guideline Deploying the Identity Foundation Services and changed during the inital setup the SKU for azureb2c in the config.json from PremiumP1 to Standard, as the documentation tells is possible. But the deployed SKU of the Azure AD B2C tenant is PremiumP1, not Standard.

To Reproduce Steps to reproduce the behavior:

  1. Go to Deploying the Identity Foundation Services
  2. Follow the guide until Running the script the first time
  3. edit the config.json file and change $.initConfig.azureb2c.skuName from PremiumP1 to Standard`
  4. run the ./run.sh script again
  5. take a look at the SKU at the newly deployed Azure AD B2B Tenant

Expected behavior The SKU should be Standard, but it is PremiumP1.

Screenshots image image

Desktop (please complete the following information):

leo-schick commented 5 months ago

I guess that the service plan "Standard" has been deleted and is automatically mapped by Azure to PremiumP1. If that is the case, the comment should be changed to not include Standard but only PremiumP1 and PremiumP2.

1iveowl commented 5 months ago

Thanks for reporting this @leo-schick.

Indeed it looks like the Standard SKU is no longer available and that the comment needs to be updated.

https://azure.microsoft.com/en-us/pricing/details/active-directory-external-identities/