Microsoft.Graph `GraphServiceClient` initialisation results in No operations defined in spec!

Describe the issue Initialising Microsoft.Graph GraphServiceClient anywhere in a function app that uses OpenAPI results in No operations defined in spec!

To Reproduce Steps to reproduce the behavior:

1. Create a new Function App v4 .net 6, with an HttpTrigger with OpenAPI extension
2. Install Microsoft.Graph v4.21.0 (You may also need Azure.Identity v1.5.0 if you plan to make a working example)
3. Start function app
4. Notice that the swagger UI and swagger JSON has no operations

Expected behavior Operations should be listed as per normal

Example code:

ClientSecretCredential credential = new ClientSecretCredential(
                    tenantId,
                    clientId,
                    clientSecret,
                    new TokenCredentialOptions
                    {
                        AuthorityHost = AzureAuthorityHosts.AzurePublicCloud
                    });
            string[] scopes = new[] { "https://graph.microsoft.com/.default" };

            graphClient = new GraphServiceClient(credential, scopes);

commenting out the final line solves the issue. It seems that somehow GraphServiceClient’s constructor disturbs something on the OpenAPI side.

Environment (please complete the following information, if applicable):

• Version: Microsoft.Azure.WebJobs.Extensions.OpenApi 1.2.0

Additional context I am writing a function app to manage B2C users via the GraphAPI. I’m using OpenAPI to maintain and share the documentation.

[justinyoo]

It was #381 and #387

[KholofeloMoyaba]

Yes, there’s the change log in the release-notes directory.

None of the PR reference this issue. So I can’t really tell what this issue was. But it’s really out of interest now, I’ll dig around the PRs and try and see. Thank you once again for the help.