Microsoft Graph
A Microsoft programmability model that exposes REST APIs and client libraries to access data on Microsoft 365 services.
12,853 questions
Connecting to Microsoft Graph always leads to script error
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(134.4, 42%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELB%3C/text%3E%3C/svg%3E)
Leon Broer
10
Reputation points
Whenever we connect to Graph (via Powershell 'connect-mggraph') the popup to sign in appears, but when logging in we always get the following script error:
Under Permission classification (Enterprise Applications -> Consent and permissions) we have already defined the following APIs as low-risk:
User.Read , openid , profile , offline_access
But this still doesn't solve the issue.
{count} votes
-
CarlZhao-MSFT 44,846 Reputation points2024-11-26T09:34:30.0666667+00:00 I'm researching this issue and will reply as soon as possible.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 27%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDO%3C/text%3E%3C/svg%3E)
Danstan Onyango 3,821 Reputation points Microsoft Employee2025-01-08T09:51:37.5666667+00:00 How is this script being executed? I guessing the issue is the environment where the signin and consent screen is loaded. Have you tried this in a plain old PowerShell terminal which will load the system browser? The screenshot you shared seems like some other interface that is not standard is that correct?
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(32, 70%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBR%3C/text%3E%3C/svg%3E)
Brent Rhodarmer 5 Reputation points2025-01-21T22:08:38.8166667+00:00 Getting very similar error starting today. This occurs when I run my PowerShell script in both VS Code, Windows PowerShell, and Windows PowerShell ISE, all ran under Admin privileges.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(182.40000000000003, 0%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDP%3C/text%3E%3C/svg%3E)
David Parkin 0 Reputation points2025-01-23T09:13:23.5966667+00:00 Getting same error when trying to add PC via autopilot utilizing get-windowsautopilotinfo.ps1 script. Any fix for this as we are now unable to onboard new devices?
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 95%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKK%3C/text%3E%3C/svg%3E)
Karl Kranich 0 Reputation points2025-01-23T20:28:30.1766667+00:00 This workaround works for me: click "Yes" once or twice to the script error message, or click the "X" to close the error box. You'll see a blank dialog box, but there is an invisible password field on it. Click around until you're in the box - you'll know because you'll see the blinking vertical cursor bar. Type your password and hit "enter".
Sign in to comment
1 answer
Sort by: Most helpful
-
Deleted
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more