Install Microsoft Graph PowerShell and connect

What you need before step 1

Applies to: Microsoft Graph PowerShell SDK (Microsoft.Graph and Microsoft.Graph.Beta modules) on PowerShell 7 for Windows and macOS, and Windows PowerShell 5.1, as documented by Microsoft

11 steps

1. 1

   Check your PowerShell version

   Where: Windows: Start menu > PowerShell 7 (or Windows PowerShell). Mac: Terminal, then type pwsh

   Microsoft recommends PowerShell 7 or later on all platforms because it needs no extra prerequisites. An install only applies to the PowerShell version you ran it in.

   $PSVersionTable.PSVersion

   You should see: Major 7 for PowerShell 7, or Major 5 Minor 1 for Windows PowerShell.
2. 2

   Install PowerShell 7 if you need it

   Where: Windows Terminal on your admin PC, or a browser and Terminal on your Mac

   Windows: run the winget command below, or download the MSI from Microsoft's install page. macOS: download the .pkg for your processor from Microsoft's macOS install page, double-click it, then type pwsh in Terminal.

   winget install --id Microsoft.PowerShell --source winget

   You should see: Windows shows a PowerShell 7 item in the Start menu. On a Mac, pwsh opens a PS prompt.
3. 3

   Set the execution policy

   Where: PowerShell on your admin computer

   Check the policy and, if it is stricter than RemoteSigned, set it for your user account.

   Get-ExecutionPolicy
   Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

   You should see: Get-ExecutionPolicy returns RemoteSigned (or a less restrictive value).
4. 4

   Install the Microsoft.Graph module

   Where: Same PowerShell window (run as administrator only if you choose AllUsers)

   Install for your account. The module pulls in dozens of submodules, so allow a few minutes. Use the AllUsers line instead if everyone on the computer needs it. Install Microsoft.Graph.Beta only if a task needs beta endpoints; Microsoft recommends v1.0 for scripts.

   Install-Module Microsoft.Graph -Scope CurrentUser -Repository PSGallery -Force
   Install-Module Microsoft.Graph -Scope AllUsers -Repository PSGallery -Force
   Install-Module Microsoft.Graph.Beta -Repository PSGallery -Force

   You should see: The prompt returns with no red error text.
5. 5

   Confirm the install

   Where: Same PowerShell window

   Check the installed version. It should match the latest version on the PowerShell Gallery.

   Get-InstalledModule Microsoft.Graph

   You should see: One line showing Version, Name Microsoft.Graph and Repository PSGallery.
6. 6

   Find the scopes your command needs

   Where: Same PowerShell window

   Ask the SDK which permissions a cmdlet needs, then request only those.

   Find-MgGraphCommand -command Get-MgUser | Select -First 1 -ExpandProperty Permissions

   You should see: A list of permission names such as User.Read.All and Directory.Read.All, with an IsAdmin column.
7. 7

   Connect with the scopes you need

   Where: Same PowerShell window

   Run Connect-MgGraph with a comma-separated list of scopes. A sign-in page opens. Sign in with your admin account.

   Connect-MgGraph -Scopes "User.Read.All","Group.ReadWrite.All"

   You should see: After sign-in PowerShell shows Welcome to Microsoft Graph!
8. 8

   Grant consent

   Where: The browser sign-in window that Connect-MgGraph opened

   Microsoft Graph PowerShell permissions are not pre-authorised, so the first time you request a scope a permissions request appears. Review the list and accept. Scopes that need admin consent must be accepted by an account with Application Administrator or Cloud Application Administrator. To add more scopes later, run Connect-MgGraph again with the extra scopes.

   You should see: The browser says you can close the window, and PowerShell shows the welcome message.
9. 9

   Use device code sign-in if the browser will not open

   Where: PowerShell on a server, jump box or remote session

   Use device code flow and complete sign-in on another device. If the sign-in pop-up hangs on Windows, turn off Web Account Manager sign-in and try again.

   Connect-MgGraph -Scopes "User.Read.All","Group.ReadWrite.All" -UseDeviceAuthentication
   Set-MgGraphOption -DisableLoginByWAM $true

   You should see: PowerShell shows a code and a URL; after you sign in elsewhere, the welcome message appears.
10. 10

    Check who you are signed in as

    Where: Same PowerShell window

    Show the session details, then list every scope you have consented to, one per line.

    Get-MgContext
    Get-MgContext | Select -ExpandProperty Scopes

    You should see: Account shows your admin UPN, TenantId shows your tenant GUID, AuthType shows Delegated and AppName shows Microsoft Graph PowerShell. The second command lists scopes such as User.Read.All.
11. 11

    Sign out when finished

    Where: Same PowerShell window

    You stay signed in until you disconnect. Disconnect clears the cached token.

    Disconnect-MgGraph

    You should see: Get-MgContext returns nothing.

Expert tips

How to confirm it worked

• Get-InstalledModule Microsoft.Graph returns a version from PSGallery.

• Get-MgContext shows your Account, TenantId and the Scopes you asked for.

How to reverse it

Errors you might see

Questions

Official sources

Vendors change menus and requirements. Confirm on the source before you rely on a detail. Last checked 4 Nov 2026.