microsoftgraph / microsoftgraph/msgraph-sdk-powershell

Connect-MgGraph is using an unsupported browser

Open
#2,732 10 comments 0 reactions 1 assignee View on GitHub

@Ndiritu is already working on this.

Since May 23, 2024.

type:bug
Dominant language
C#
Stars
898
Forks
230
Avg merge
2d 5h
Merged PRs (30d)
31

Description

Describe the bug

Simply using Connect-MgGraph with an account that is in the periodic "Is this info up to date?" verification state causes Powershell to fail as it's tries to use an "unsupported browser". This is on any Win10 machine I try, all of which are fully patched and have Edge as their default (and only) browser.

Here's an example
1
2
3

This only happens for accounts in the info-verification state. If I manually browse to office.com then this is the page that Powershell is trying to display:
4

Expected behavior

Back in the days of IE, Powershell used to just display the "Is this info up to date?" page.

How to reproduce

Using an account that is in the periodic details verification state

Import-Module Microsoft.Graph.Authentication
Connect-MgGraph
Select the account
Click "next" on the "More information required" pop-up

SDK Version

ModuleType Version Name ExportedCommands ---------- ------- ---- ---------------- Script 2.19.0 Microsoft.Graph.Authentication {Add-MgEnvironment, Connect-MgGraph, Disconnect-MgGraph, G...

Latest version known to work for scenario above?

2.19.0

Known Workarounds

Clearing the "Is this info up to date" by manually browsing to a Microsoft site (i.e. office.com) and confirming details there will reset the state and then the user can go back to using Connect-MgGraph in Powershell without issue.
This is fine for admins and tech users but isn't satisfactory for average users where we use Connect-MgGraph in logon scripts.

Debug output
Click to expand log ```
</details>


### Configuration

$PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.19041.4291
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.19041.4291
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1


Multiple Windows 10 Enterprise x64 desktops running fully-patched 22H2

### Other information

_No response_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.