customize-ui | UI Customization plugin for vscode | Code Editor library

You need to set AllowBlobPublicAccess to true on your storage accounts. You can do this in the Portal under Configuration for the storage account by setting "Blob public access" to Enabled.

This behavior is "by design" and cannot be changed.

https://github.com/MicrosoftDocs/azure-docs/issues/47654

For localization, you can provide the query string parameter, ui_locales, from your application. When you call into Azure AD B2C, your page is translated to the locale that you have indicated. This type of configuration gives you complete control over the languages in your user flow and ignores the language settings of the customer's browser. You might not need that level of control over what languages your customer sees. If you don't provide a ui_locales parameter, the customer's experience is dictated by their browser's settings. You can still control which languages your user flow is translated to by adding it as a supported language. If a customer's browser is set to show a language that you don't want to support, then the language that you selected as a default in supported cultures is shown instead.

The {Culture:RFC5646} claim resolver works in the same way. Meaning If a customer's browser is set to show a language that you don't want to support, then the language that you selected as a default in supported cultures is sent to the HTML page instead.

The only case where an unsupported ui_locales will be sent to the HTML page, is when the app passes the missing ui_locales in the query string. In this case we consider that to be an application decision and allow it to override supported cultures configuration.

So, make sure your application sends only supported language in the ui_locales query string parameter.

The "Sign in with your social account" HTML is just sample HTML from B2C. To replace this, you can save your custom HTML page in Azure Blob Storage and then follow these steps:

1. Sign in to your tenant on the Azure portal and navigate to the B2C features blade.
2. Click Sign-up or sign-in policies, click your policy and click on Edit (for example, "b2c_1_sign_up_sign_in").
3. Click Page UI customization and then Unified sign-up or sign-in page.
4. Toggle the Use custom page switch to Yes. In the Custom page URI field, enter https://wingtiptoysb2c.blob.core.windows.net/b2c/wingtip/unified.html. Click OK.
5. Click Local account sign-up page. Toggle the Use custom template switch to Yes. In the Custom page URI field, enter https://wingtiptoysb2c.blob.core.windows.net/b2c/wingtip/selfasserted.html.
6. Repeat the same step for the Social account sign-up page. Click OK twice to close the UI customization blades.
7. Click Save.

For reference, see the full instructions here: https://docs.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-reference-ui-customization-helper-tool

You can do the same thing to customize your Sign Up/Profile Edit pages.

Register your reply url with HTTPS: https://.azurewebsites.net/signin-oidc. Azure app services hosted under the azurewebsites.net domain provide a built-in SSL certificate.

The page UI that is displayed is determined by the content definition.

E.g. In the custom policy starter pack, the api.selfasserted content definition that is used for the sign-up page UI is set to the 1.1.0 version:

Try enabling user interaction here for label,Worked for me, and please use UITapGesture instead of UIGesture And Textfield should be below uilabel because if the textfield is above label then uilabel's user interaction won't be considered