Azure Application Registry with Graph API produce different applications with RequestedAccessTokenVersion properties

Question

we've been using Azure graph API Microsoft Graph APIs to create new Azure applications for months, but since last week we found the new created applications contain different RequestedAccessTokenVersion value from past months. In the past months we've created thousands of applications, and all of them have "RequestedAccessTokenVersion " with 2, accessTokenAcceptedVersion:2 while since last week, there are several applications created, the value was null. accessTokenAcceptedVersion:null which will affect the access token generation.

We don't change any related code about the creation for the application. Do you know what is happening?

We tried to find if we've ever changed the code, while we didn't.

Answer 1

We don't change any related code about the creation for the application. Do you know what is happening?

As you did not change anything, the change must have happened on Microsofts end. The API Reference still lists the expected return value to be:

...
    "api": {
        "requestedAccessTokenVersion": 2,
        "acceptMappedClaims": null,
        "knownClientApplications": [],
        "oauth2PermissionScopes": [],
        "preAuthorizedApplications": []
    },
...

Additionally, I could not find anything in the known limitations (https://developer.microsoft.com/en-us/graph/known-issues/?search=application)

So I would recommend to create an issue / create a support ticket: https://portal.azure.com/#view/Microsoft_Azure_Support/HelpAndSupportBlade/~/overview