Issue with Multi-Tenancy Flag Always Returning Enabled on Azure App Service Deployment #12444

Issue with Multi-Tenancy Flag Always Returning Enabled on Azure App Service Deployment Description: We are experiencing an issue with the multi-tenancy behavior in our ASP.NET Zero-based application after deploying to an Azure App Service (Linux-based). Observations:

• We have explicitly set the MultiTenancyEnabled = false in our codebase.
• We have enabled Microsoft Entra ID authentication.
• When running the application locally, if the user is unauthenticated:
  • They are redirected to the Entra ID login screen as expected.
  • After successful login, they are redirected to the correct default page ( /search).
  • The tenant selection modal does not appear, which is correct behavior for single-tenant mode.

However, when we deploy the same codebase to Azure App Service (Linux):

• The frontend Angular app still behaves as if multi-tenancy is enabled.
• The /AbpUserConfiguration/GetAll API call returns multiTenancy.isEnabled = true.
• After login, the user is shown a modal popup to select a tenant, which should not happen in single-tenant mode.

Additional Steps Taken:

• We verified that the correct setting (MultiTenancyEnabled = false) is present in the deployment.
• We also attempted recreating the database from scratch, but the issue persists on the deployed environment.
• The issue is reproducible locally only if we toggle the flag to true, which confirms the frontend is reading the incorrect state post-deployment.

Code change to set Multi Tenancy off. Response we get on front end on local = “False” – which is correct Same code deployed on App service we get the response as = “True” – which is not correct. The Switch tenant modal we get on deployed app after login is successful.