'%3e%3cpath%20d='M8%200C12.4183%200%2016%203.58172%2016%208C16%2012.4183%2012.4183%2016%208%2016C3.58172%2016%200%2012.4183%200%208C0%203.58172%203.58172%200%208%200ZM11.6162%204.38379C11.2257%203.99337%2010.5927%203.99338%2010.2021%204.38379L8%206.58594L5.79785%204.38379C5.40732%203.99334%204.77429%203.99329%204.38379%204.38379C3.99331%204.77429%203.99335%205.40733%204.38379%205.79785L6.58594%208L4.38379%2010.2021C3.99348%2010.5927%203.99341%2011.2257%204.38379%2011.6162C4.77426%2012.0066%205.40734%2012.0065%205.79785%2011.6162L8%209.41406L10.2021%2011.6162C10.5927%2012.0066%2011.2257%2012.0067%2011.6162%2011.6162C12.0067%2011.2257%2012.0066%2010.5927%2011.6162%2010.2021L9.41406%208L11.6162%205.79785C12.0066%205.40735%2012.0066%204.77429%2011.6162%204.38379Z'%20fill='%23080E17'%20fill-opacity='0.46'/%3e%3c/g%3e%3cdefs%3e%3cclipPath%20id='clip0_3761_713'%3e%3crect%20width='16'%20height='16'%20fill='white'/%3e%3c/clipPath%3e%3c/defs%3e%3c/svg%3e)
How to Fix the Unsupported Browser Error in Exchange Online PowerShell
Question details
Users encounter an unsupported browser error when running the Connect-ExchangeOnline command in PowerShell.
- Product
- Exchange Online PowerShell
- Device & OS
- not provided
- Scenario
- Attempting to connect to Exchange Online via PowerShell using modern authentication.
- Observed behavior
- PowerShell opens an outdated embedded browser or Internet Explorer instead of the default modern browser, failing the authentication process with an unsupported browser message.
Ensure that Microsoft Edge is updated to the latest version and temporarily verify that it is set as your default system browser.
Pre-authenticate via Microsoft Edge
Bypass the embedded legacy browser by logging into your account directly in Microsoft Edge before running the PowerShell command.
The Connect-ExchangeOnline module sometimes incorrectly triggers legacy Internet Explorer components for its authentication popup. By initiating an active session in a supported browser first, PowerShell can often piggyback on the existing modern authentication token.
Launch the latest version of Microsoft Edge on your computer.
Navigate to the official Microsoft 365 sign-in page and securely log in using your Exchange administrator credentials.
Close the embedded PowerShell authentication window that is currently displaying the 'unsupported browser' error.
Return to your PowerShell window and execute the Connect-ExchangeOnline command again. The system should now detect your active Edge sign-in session.
Use Device Code Authentication
Force the authentication process to happen entirely outside of the PowerShell embedded browser using a device code.
Looking for a Reliable and Free Office Suite?
While troubleshooting Exchange Online and PowerShell issues can be highly technical, managing your everyday documents shouldn't be. WPS Office offers a completely free, lightweight, and user-friendly alternative to Microsoft Office.
- 1. Download the installer: Visit the official WPS Office website and click the free download button.
- 2. Install the application: Run the downloaded installer file and follow the simple on-screen instructions.
- 3. Start creating: Open WPS Office to instantly view, edit, and create Word, Excel, PowerPoint, and PDF documents.
Frequently Asked Questions
Why does Connect-ExchangeOnline open Internet Explorer instead of Edge?
Some older versions of the Exchange Online Management module or specific Windows configurations rely on legacy embedded web controls (.NET WebBrowser control) that default to the Internet Explorer engine, even if Edge is your default browser.
How do I update the Exchange Online Management module?
Open an elevated PowerShell window (Run as Administrator) and execute the command: Update-Module -Name ExchangeOnlineManagement. This ensures you have the latest Microsoft fixes for modern authentication.
Will changing my default Windows browser fix this PowerShell error?
Not always. Because the error is often tied to the hardcoded web components within the PowerShell module's authentication library, simply changing your default browser to Edge or Chrome in Windows settings might not prevent the legacy popup from appearing.
