Using PowerShell to talk to the Office 365 Service Communications API

Cam, did you ever figure out how to leverage the new V2 APIs with PowerShell?   The V1 APIs are a lot easier to use, but the V2 APIs look like they would offer more capabilities.   Also, the V2 APIs have been in preview for over a year and a half, so I wonder how much longer the V1 APIs will be supported.  

VasilMichev, Anne Michels, cammurray Thank you all. 

First, I was able to use Cam's script to produe a spreadsheet.  My PowerShell looks like this:

$cred = get-credential
$jsonPayload = (@{userName=$cred.username;password=$cred.GetNetworkCredential().password;} | convertto-json).tostring()
$cookie = (invoke-restmethod -contenttype "application/json" -method Post -uri "https://api.admin.microsoftonline.com/shdtenantcommunications.svc/Register" -body $jsonPayload).RegistrationCookie
$jsonPayload = (@{lastCookie=$cookie;locale="en-US";preferredEventTypes=@(2)} | convertto-json).tostring()
$events = (invoke-restmethod -contenttype "application/json" -method Post -uri "https://api.admin.microsoftonline.com/shdtenantcommunications.svc/GetEvents" -body $jsonPayload)
$events.Events | export-csv -LiteralPath "C:\temp\2017-04-03-Messages.csv" -NoTypeInformation

It works.  It still needs some tweaking because one of the columns, with the message details, comes up containing objects.  But it's good enough for this week.  I'll improve on it next week when it is time for me to review the message center messages again.  What I did after I produced the CSV is save it as an XLSX and format the data as a table. I deleted a few empty or not helpful columns and re-ordered the rest.  I then added two columns, "Governance Assessment" and "Notes".  I then filled in those columns as needed, documenting which Messages require further work on my part.  For example, some changes "user will just figure out". Others might be something I have to discuss with a larger audience, such as the SharePoint Governane Team, the other O365 Admins, or Corporate Communications.   In other words, I've solved my business need for this week, but incurred technical debt to do so.

Looking ahead, I want to use the new APIs.  This means I will have to create an app registration in Azure AD.  Anne Michels, are there newer instructions than https://msdn.microsoft.com/en-us/office-365/get-started-with-office-365-management-apis that show how to do that registration in the new Azure Admin Portal UI?  Since this is a script that is calling the APIs rather than a web app, guidance on property values like Sign-On URL and App ID UI and Reply URL would be helpful. 

Also, what permissions should it be granted if it just needs to read Message Center messages?  I did not see a permission that provides that access.

cammurray it would be great if you could update your article to use the new API.  As you can see from above, guidance on app registration in Azure AD is needed too.  Do you know of any PowerShell examples for using the MSAL to get the token? Are the MSAL libraries something I need to install locally before I can reference them and use them in PowerShell?  Where do I get them from?

Thanks,

Michael