Feedback by UserVoice

I suggest you ...

Allow PowerShell ClientID to consume Office 365 Usage Reports

It would be great if we could access the Office 365 Usage Report without creating an Azure App like explained here : https://blogs.technet.microsoft.com/dawiese/2017/04/15/get-office365-usage-reports-from-the-microsoft-graph-using-windows-powershell/

Indeed, it's kind of a showstopper for consultants who want to assess a client's Office 365 tenant.

There is a PowerShell ClientID that is already available to consume other GraphAPI feature like this :
https://blogs.technet.microsoft.com/paulomarques/2016/03/21/working-with-azure-active-directory-graph-api-from-powershell/

But if we use it, it fails with:
Invoke-RestMethod : {
"error": {
"code": "InvalidAuthenticationToken",
"message": "Access token validation failure.",
"innerError": {
"request-id": "82702d75-723c-4725-be89-b0bc3a1e95ee",
"date": "2017-04-19T13:10:27"
}
}
}

157 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Emmanuel shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base