The best possible solution would be using a dynamic domain value (either by parsing the username claim or by using a dedicated domain claim). Something like below helps:
<provider>
<name>Azure OpenID</name>
<enabled>true</enabled>
<discovery-url>https://login.microsoftonline.com-id/v2.0/.well-known/openid-configuration</discovery-url>
<client-id>8888-8888-888888-8888888</client-id>
<client-secret>REDACTED</client-secret>
<domain-claim>some_claim_containing_the_domain_name</domain-name>
<username-claim>sAMAccountName</username-claim>
<id-token-signature-verification-disabled>true</id-token-signature-verification-disabled>
<display-properties />
<domain-option>use_domain_claim</domain-option>
</provider>
or perhaps (if the value of UserPrincipalName, or a similar claim, is something like username@domain):
<provider>
<name>Azure OpenID</name>
<enabled>true</enabled>
<discovery-url>https://login.microsoftonline.com-id//v2.0/.well-known/openid-configuration</discovery-url>
<client-id>9999-9999-9999999-9999</client-id>
<client-secret>REDACTED</client-secret>
<username-claim>UserPrincipalName</username-claim>
<id-token-signature-verification-disabled>true</id-token-signature-verification-disabled>
<display-properties />
<domain-option>parse_username_claim</domain-option>
</provider>