Blog

This Graph API PowerShell article will show how to create a self-signed certificate on a Windows machine and upload it to an App Registration using Graph API.

The Microsoft Graph PowerShell SDK application requires users to have domain knowledge of both the semantics and syntax of Microsoft Graph API permissions used to authorize access to the API. 

With the Microsoft Graph PowerShell SDK, you need to connect to the Graph API with a scope. The scope denotes what permissions you’ll need to execute your commands during the session.

There are a number of cmdlets that can be used to manage the different parameters required during authentication, for example, environment, application ID, and certificate. In this article, we’ll look at the different cmdlets that are associated with authentication.

This blog post will show how to create an Azure App Registration using Azure CLI for Microsoft Graph. Azure Graph API gives us access to all the Azure and Microsoft 365 services programmatic access. Graph API allows us to create, edit and view resources using API calls.

Connect-Graph is an alias of Connect-MgGraph. Connect-MgGraph is the connection command provided by current versions of the Microsoft.Graph.Authentication module. You can check it by Get-Alias cmdlet.

After Microsoft announced the deprecation of PowerShell modules, such as Entra ID and MS Online, the MS Graph PowerShell modules gained attention from admins. However, the Microsoft Graph module might not provide all the necessary attribute values or properties. So, admins utilize the beta profile of the PowerShell module to fulfill them.

In some cases, after roughly an hour into the script, it failed with a 401 Unauthorized error. The reason is that the access token granted to the app to allow it to run Graph requests to fetch data expired, meaning that the next time the app tried to request data, the Graph refused.