Connect-MgGraph: try - catch not consistent

[i5513]

See #3582

That is a feature request about timeout option in Connect-MgGraph.

But I think the current behaviour should be fixed or documented

date; try {
      Connect-MgGraph -ErrorAction stop -ContextScope Process -TenantId 'xxx' -ClientId 'yyy' }  catch {
       Write-Warning 'Cannot Connect'
} finally { 'Esto sí se ejecuta!' }

lunes, 20 de abril de 2026 12:32:47
ADVERTENCIA: Note: Sign in by Web Account Manager (WAM) is enabled by default on Windows. If using an embedded
terminal, the interactive browser window may be hidden behind other windows.

[proceso terminado con el código 1 (0x00000001)]
Ahora puede cerrar este terminal con Ctrl+D o presionar Entrar para reiniciar.
Windows PowerShell
Copyright (C) Microsoft Corporation. Todos los derechos reservados.

Instale la versión más reciente de PowerShell para obtener nuevas características y mejoras. https://aka.ms/PSWindows

> date

lunes, 20 de abril de 2026 12:40:39

Expected behavior

try { connect-mggraph ... } catch { xxxx } finally { yyy } 

How to reproduce

1. try { Connect-MgGraph -ErrorAction stop -ContextScope Process -TenantId 'xxx' -ClientId 'yyy }  catch { Write-Warning 'Cannot Connect' }

2. Wait 7 minutes

SDK Version

2.35.1

Latest version known to work for scenario above?

No response

Known Workarounds

I tried

Start-Job { $now = Get-Date; sleep 120; Get-Process  Microsoft.AAD.BrokerPlugin -ErrorAction SilentlyContinue |? StartTime -gt $now | Stop-Process }
 try { Connect-MgGraph -ErrorAction stop -ContextScope Process -TenantId 'xxx' -ClientId 'yyy' }  catch { Write-Warning 'Cannot Connect' }

But It didn't work

Debug output

No response

Configuration

Windows 11
Name Value

---

PSVersion 5.1.22621.6931
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.22621.6931
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Other information

No response

[ramsessanchez]

@i5513 please provide more context and debug output. As mentioned in #3582 this try catch seems to work after the default timeout of 2 minutes expires. Please provide the full script you are running as it could help better reproduce the issue.

[i5513]

Thank you @ramsessanchez , I Will try to provide a script on thursday. Knowing about the two minutes of timeout will help me to develope It.

The diff between my example and yours is the -clientid parametef

But the example is the only thing that I do in the terminal when the issue happens

[ramsessanchez]

Hi @i5513 , I don't believe the clientId parameter would make a functional difference as it is only used for configuration. I'll keep this open and wait for further detail. The only other difference is I ran this in powershell version 7.6. Is it possible for you to run the script in a version 7 shell?

[i5513]

Hello @ramsessanchez , The same result in powershell 7. Launching Connect-MgGraph, and waiting 4 / 5 minutes

I'm attaching transcript and console output (not sure why debug output won't go to transcript :( )

• Powershell 7:

connect-mggraph-pw7.txt
transcript-connect-mggraph-7.log

• Powershell 5.1:
  connect-mggraph-pw5.txt
  transcript-connect-mggraph-5.1.log

png files are without -debug param, but *txt and *log is the result of execute:

date
powershell.exe -command {
        $DebugPreference = 'Continue'
        Start-Transcript c:\temp\transcript-connect-mggraph-X.log
         Connect-MgGraph -Debug -ErrorAction stop -ContextScope Process -TenantId 'xxx'
         Stop-Transcript
      }
date

With debug flag, png would start :

• powershell 7:

• powershell 5: