OpenID Azure B2c The scope organisationid provided in the request is not supported

KODAVALLA, Sanjeev 0 Reputation points
2024-04-16T10:44:12.0233333+00:00

Getting error for receiving custom claim The scope organisationid provided in the request is not supported.

added scope for organisationid in api permission, added it as custom claim, modified the manifest,

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
19,548 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. James Hamil 21,851 Reputation points Microsoft Employee
    2024-04-19T22:13:07.1433333+00:00

    Hi @KODAVALLA, Sanjeev , it seems that you are trying to receive a custom claim named organisationid in your Azure AD B2C application, but you are getting an error that the scope is not supported.

    To receive a custom claim in your application, you need to make sure that you have configured the correct scopes and permissions. Here are some steps that you can follow to troubleshoot the issue:

    1. Make sure that you have added the organisationid scope to your API permission. You can do this by going to the Azure portal, selecting your application, and then going to the "API permissions" tab. From there, you can add the organisationid scope to your API permission.
    2. Make sure that you have added the organisationid claim to your custom policy. You can do this by adding the following code to your custom policy:
    <OutputClaim ClaimTypeReferenceId="organisationid" />
    
    1. Make sure that you have modified the manifest to include the organisationid claim. You can do this by adding the following code to the manifest:
    {
      "name": "organisationid",
      "source": "user",
      "essential": false,
      "additionalProperties": []
    }
    

    If you have followed these steps and are still getting the error, it is possible that there is an issue with the configuration of your custom policy. You can try to troubleshoot the issue by looking at the logs and error messages in the Azure portal. If you are still having trouble, please let me know and I can help you further. If this answer helps you please mark "Accept Answer" so other users can reference it.

    Thank you,

    James

    0 comments No comments