Question 1

Why do you use Invoke-MgGraphRequest instead of the Graph PowerShell commandlets?

Accepted Answer

We use Invoke-MgGraphRequest for several reasons: Browser Network Inspection - you can use F12 developer tools to inspect actual Microsoft Graph API calls in the Intune Portal; Minimal Dependencies - only requires Microsoft.Graph.Authentication module; Direct API Access - provides direct access to the raw Microsoft Graph REST API; Easier Troubleshooting - easily replicate and test the same API calls that the Intune Portal uses.

Question 2

What are the different ways to run these scripts?

Accepted Answer

You can run these scripts in two main ways: Local Execution - uses interactive authentication with Connect-MgGraph, manual execution from PowerShell ISE/VS Code/terminal, best for testing and development. Azure Automation Runbooks - uses Managed Identity authentication, scheduled execution for automation, best for production environments and recurring tasks. Our scripts automatically detect the execution environment and use appropriate authentication.

Question 3

How do I deploy scripts to Azure Automation using the Deploy to Azure button?

Accepted Answer

Click the Deploy to Azure button on any script page. This will open Azure Portal with a pre-configured ARM template. Fill in required parameters like Resource Group and Automation Account name, then click Create. The script will be automatically imported as a runbook in your Azure Automation account.

Question 4

What permissions do I need to run these scripts?

Accepted Answer

Required permissions vary by script, but typically include Microsoft Graph API permissions like DeviceManagementManagedDevices.Read.All, DeviceManagementConfiguration.Read.All, or User.Read.All. Each script lists its specific required permissions. For Azure Automation, grant these permissions to the Managed Identity.

Question 5

How can I contribute my own scripts?

Accepted Answer

We welcome contributions! Fork the GitHub repository, add your script following our template format, include proper metadata (title, description, required permissions), test your script thoroughly, then submit a pull request. We'll review and merge quality contributions.

IntuneAutomation

How It Works

Browse & Search

Copy or Deploy

Automate

Most Popular Scripts

Frequently Asked Questions

Other Tools and Projects

IntuneBrew

IntuneGet

IntuneRemote

IntuneAutomation

How It Works

Browse & Search

Copy or Deploy

Automate

Most Popular Scripts

Frequently Asked Questions

Why do you use Invoke-MgGraphRequest instead of the Graph PowerShell commandlets?

What are the different ways to run these scripts?

How do I deploy scripts to Azure Automation using the Deploy to Azure button?

What prerequisites do I need to run these scripts?

How do I authenticate with Microsoft Graph?

Are these scripts safe to use in production?

How are these scripts tested before release?

Can I modify these scripts for my organization's needs?

How often are the scripts updated?

What should I do if a script doesn't work?

Should I use the v1.0 or beta Microsoft Graph API endpoints?

Other Tools and Projects

IntuneBrew

IntuneGet

IntuneRemote