GET Onedrive activity reports using microsoft graph sdk

My requirement is to get details about OneDrive activity by user  using Microsoft Graph SDK.

I set the Graph permission “Reports.Read.All” as per the documentation. Being said that in case if you’re using delegated permissions then it needs to allow apps to read service usage reports on behalf of a user, the tenant administrator must have assigned the user the appropriate Azure AD limited administrator role. More info is given at the documentation.

Here’s the code sample that i used:

// create a get request for the period D7
var request = graphServiceClient.Reports
            .GetOneDriveActivityUserDetail("D7")
            .Request()
            .GetHttpRequestMessage();

// send the request to get the response
var response = await graphServiceClient.HttpProvider.SendAsync(request);
string csvReport = "";
if (response.IsSuccessStatusCode)
{
    // read the report
    csvReport = await response.Content.ReadAsStringAsync();
}
else
{
    // read the error status code and error message
    var code = response.StatusCode.ToString();
    var message = await response.Content.ReadAsStringAsync();
}

If the above API call is successful, then you will see this method returns HTTP 302 Found response that redirects to a preauthenticated download URL for the report. That URL can be found in the Location header in the response.

Alternately you can test the same with Microsoft Graph explorer or POSTMAN as well using the following API call:

GET https://graph.microsoft.com/v1.0/reports/getOneDriveActivityUserDetail(period='D7')

Hope this helps.

Investigate Microsoft Graph API call getOffice365ActiveUserDetail(period=’D7′) error HTTP 403 with Microsoft Graph explorer

One of my developer customer updated me that he tried calling reports from his custom application, using the Microsoft Graph API call “getOffice365ActiveUserDetail(period=’D7′)”, but receive HTTP 403. In order to isolate the issue, i tried repro the issue using Microsoft Graph Explorer and i can repro so. HTTP 403 – Forbidden!!

Being said that, Graph explorer updated me that i need to consent to the permissions on the “Modify Permissions” tab; in another words in order to run the reports i need the permissions. 
How cool is this new feature introduced in new MS Graph explorer?

Ok, I followed the steps in Graph explorer:

Just hover over the description. It provides a info clearly (see the below snapshot):

In order to make the permissions (admin consent required) to effect with my app (in this scenario, it will be MS Graph explorer), it thrown the dialog box to confirm:

On successful of the above, i made the same API call with Microsoft Graph explorer and it worked as i expected…!!

Happy Microsoft Graphing

Graph API : How to get the specified profile photo programmatically?

This is one of the regularly asked queries by the Azure/Office 365 developers, how they can get/retrieve the specified profile photo programmatically using Microsoft Graph API.

You can use the userphoto API call to do it. You can get the specified Profilephoto or its metadata (profilephoto properties).

What it does?

• A GET photo operation first attempt to retrieve the specified photo from Office 365.
• If the photo is not available in Office 365, the API attempts to retrieve the photo from Azure Active Directory.
• If the Profilephoto API call is successful, this method returns a 200 OK response code and binary data of the requested photo. If no photo exists, the operation returns 404 Not Found.
• If the ProfilePhoto API’s get metadata call is successful, this method returns a 200 OK response code and profilePhoto object in the response body.
• When you use the /photo/$value endpoint to get the binary data for a profile photo, you’ll need to convert the data into a base-64 string in order to add it as an email attachment.
• In case, if you wish to display the image on a web page, create an in-memory object from the image and make that object the source of an image element.
• Also whenever you use APIs under the /beta version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported.

Supported Sizes of photo:

The supported sizes of HD photos on Office 365 are as follows: ’48×48′, ’64×64′, ’96×96′, ‘120×120’, ‘240×240’, ‘360×360′,’432×432’, ‘504×504’, and ‘648×648’. Photos can be any dimension if they are stored in Azure Active Directory.

You can get the metadata of the largest available photo, or specify a size to get the metadata for that photo size. If the size you request is not available, you can still get a smaller size that the user has uploaded and made available. For example, if the user uploads a photo that is 504×504 pixels, then all but the 648×648 size of photo will be available for download. If the specified size is not available in the user’s mailbox or in Azure Active Directory, the size of ‘1×1’ is returned with the rest of metadata.

 

Programmatically test the API call with Microsoft Graph Explorer:

First we try to get metadata, GET https://graph.microsoft.com/beta/me/photo/

 

Then, let me try to get the photo, GET https://graph.microsoft.com/beta/me/photo/$value

 

Hope this helps.

Microsoft Graph API : How to get the specified profile photo programmatically?

This is one of the regularly asked queries by the Azure/Office 365 developers, how they can get/retrieve the specified profile photo programmatically using Microsoft Graph API. You can use the userphoto API call to do it. You can get the specified Profilephoto or its metadata (profilephoto properties).

What it does?

• A GET photo operation first attempt to retrieve the specified photo from Office 365.
• If the photo is not available in Office 365, the API attempts to retrieve the photo from Azure Active Directory.
• If the Profilephoto API call is successful, this method returns a 200 OK response code and binary data of the requested photo. If no photo exists, the operation returns 404 Not Found.
• If the ProfilePhoto API’s get metadata call is successful, this method returns a 200 OK response code and profilePhoto object in the response body.
• When you use the /photo/$value endpoint to get the binary data for a profile photo, you’ll need to convert the data into a base-64 string in order to add it as an email attachment.
• In case, if you wish to display the image on a web page, create an in-memory object from the image and make that object the source of an image element.

Please note that whenever you use APIs under the /beta version in Microsoft Graph are subject to change. Use of these APIs in production applications is not supported.

Supported Sizes of photo:

The supported sizes of HD photos on Office 365 are as follows: ’48×48′, ’64×64′, ’96×96′, ‘120×120’, ‘240×240’, ‘360×360′,’432×432’, ‘504×504’, and ‘648×648’. Photos can be any dimension if they are stored in Azure Active Directory.

You can get the metadata of the largest available photo, or specify a size to get the metadata for that photo size. If the size you request is not available, you can still get a smaller size that the user has uploaded and made available. For example, if the user uploads a photo that is 504×504 pixels, then all but the 648×648 size of photo will be available for download. If the specified size is not available in the user’s mailbox or in Azure Active Directory, the size of ‘1×1’ is returned with the rest of metadata.

Programmatically test the API call with Microsoft Graph Explorer:

First we try to get metadata, GET https://graph.microsoft.com/beta/me/photo/

Then, let me try to get the photo, GET https://graph.microsoft.com/beta/me/photo/$value

Hope this helps.