This post will not cover the requirements of having the prerequisites in terms of an Azure AD app registration or using the default Microsoft Intune PowerShell enterprise app, but I recommend reading the following post to get a better understand of what’s required:Ĭreate an Azure AD App Registration for accessing Microsoft Intune Graph APIĭepending on if you’ve read the post mentioned above, or are already familiar with the requirements of accessing Graph API with an app registration or enterprise app, it’s important to know the ClientID (also referred to as the ApplicationID) of your app. Some time back, I wrote a couple of blog posts on how to get started with Microsoft Intune and PowerShell. In this post we’re meant to cover the subject of setting up unattended automation workflows with the capability of running and/or scheduling PowerShell scripts built for Microsoft Intune using Azure Automation and how to handle storing of credentials for authentication. However, this post is not about the general availability of this new API. Microsoft is keeping a change log for what’s new and has changed for both API’s, available here: Once a new feature is made general available in the monthly update cycle of Microsoft Intune, and its Graph API resource is made available in the v1.0 API, you should update the resource reference for your script. The main differences between these two are that v1.0 is meant for production and beta is meant for testing and verifying new functionality being made available in Microsoft Intune. This means that we now have two set of API’s that we can use to access resources in Microsoft Intune, the beta and v1.0 API’s.
Microsoft has recently announced the general availability of the Microsoft Graph Intune API’s.
0 kommentar(er)
