7

I tried to get the content of the user's profile picture and I found out that I had to call the Beta version because the current version gives the following error message:

"code": "GetUserPhoto", "message": "The operation is not supported."

So, I tried to switch to Beta, and here is the code that I wrote in C# to do it, but it doesn't work:

Microsoft.Graph 1.6.2

List<QueryOption> options = new List<QueryOption> { new QueryOption("$api-version", "beta") }; var pictureStream = await graphClient.Me.Photo.Content.Request(options).GetAsync();

I got the same error message.

I tried the same request in the Graph Explorer. The 1.0 doesn't work, but Beta works.

Improve this question

3 Answers 3

Reset to default
12

The api-version query parameter is used by the Azure AD Graph API. This is a different API than Microsoft Graph. There is a lot of functional overlap (Azure AD Graph is slowly being migrated over to Microsoft Graph) but they use entirely different entities and calling conventions.

In order to call the /beta endpoint using the Microsoft Graph .NET Client Library, you need to change the BaseUrl of the client:

graphClient.BaseUrl = "https://graph.microsoft.com/beta"; var pictureStream = await graphClient.Me.Photo.Content.Request().GetAsync();

Some important notes about the /beta endpoint:

  1. It isn't supported and isn't suitable for production. So don't do that. Or at least don't tell anyone and don't call Support if it stops working. ;-)

  2. The .NET Client uses objects constructed off the production metadata. This means that any entities, actions or properties that were added in /beta don't exist in the models shipped with the SDK.

  3. The .NET Client will ignore any values returned by Microsoft Graph that it doesn't expect to see. So if an endpoint returns a property that wasn't included in the production metadata (see #2), it will simply be ignored.

    So long as you're only using a /beta to gain functionality but still expecting /v1.0 results, it should work okay. Photos for example only look at Exchange in v1.0 but look in both Exchange and Active Directory but still return the same result. In theory this means you should be able to swap /beta for /v1.0 without a problem.

Improve this answer
Sign up to request clarification or add additional context in comments.

Comments

1

I think you are still calling V1 endpoint. In fact, the Beta endpoint is not currently supported in the Microsoft Graph .NET Client Library. More info here.

Improve this answer

Comments

0

There is an official beta client for Graph API now: https://github.com/microsoftgraph/msgraph-beta-sdk-dotnet

Improve this answer

2 Comments

Install-Package Microsoft.Graph.Beta using PM in Visual Studio 2019 in my Net Core 3.0 project doesn't seem to work. Returns Install-Package : Unable to find package 'Microsoft.Graph.Beta'
@CMorgan You have to add the parameter -IncludePrerelease to get the package installed.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.