Just got this right before midnight in my MS Admin app alerts. If you dont configure the policy, in September it defaults to opening web links in Edge regardless of OS default browser setting.
I woke up this morning to One Drive doing its usual thing being HOT GARBAGE, now I'm going to bed with Teams becoming HOT GARBAGE.
Full Excerpt:
--
Web links from Microsoft Teams chats to open in Microsoft Edge; Teams chat will open side-by-side with link
MC669480
Plan for change
Published date: August 21, 2023
Affected services
Microsoft Teams
Tag
MAJOR UPDATEADMIN IMPACTNEW FEATUREUSER IMPACT
The Microsoft Teams desktop app for Windows will open web links from Teams chats in Microsoft Edge to enable a new web and chat side-by-side experience.
By opening web links in Edge, users will be able to see those links side-by-side with their Teams chats—web links will open as new browser tabs and the Teams chats will open next to them in the Edge sidebar. This new, single-view Teams experience in Edge is designed to minimize switching between windows and to help users stay in the flow of work while referencing web links.
This message is associated with Microsoft 365 Roadmap ID 126334.
This change to use Edge to open web links from Teams chats follows a similar, previously announced change in the Outlook for Windows app. Customers impacted by this change in Outlook were notified via MC541626, MC545904, or MC548092.
Admin controls are available as detailed below.
Read more about how we’re optimizing the experience between Microsoft 365 and Microsoft Edge:
What's New in Teams | Microsoft Inspire 2023 Notes:
This change does not affect a device’s default browser setting in Windows.
This only affects commercial users signed into Teams with Azure Active Directory (Azure AD) accounts.
The policy described in the following section configures which browser is used to open web links for both Teams (chat) and the Outlook for Windows app (email), or, if you did not receive an Outlook for Windows app Message center notification, this policy will only apply to Teams (chat).
When will this affect your organization:
Timing:
Microsoft Teams desktop app for Windows: This change will start rolling out late September.
Outlook for Windows: Roll out in progress. If this change affects your users, you will have received either MC541626, MC545904, or MC548092, and can refer to them for specific timing.
Note: Depending on your Outlook for Windows update channel, you may experience the change in Teams first. Action:
Use the Choose which browser opens web links policy to configure which browser will be used to open web links and to set whether users will be able to make changes to which browser opens web links in both the Teams desktop app for Windows (chat) and the Outlook for Windows app (email).
If you did not receive a message center notification for the Outlook for Windows app (email), then the setting only applies to Teams (chat).
If you did receive a message center notification for the Outlook for Windows app (email), then the setting applies to both Teams (chat) and Outlook for Windows app (email). You will not be able to manage each app individually using this policy. If you’ve previously configured this policy for the Outlook for Windows app and wish to maintain that configuration, no action is required.
Note: There are no Microsoft 365 subscription restrictions in using this policy to configure which browser opens web links in Teams.
Use of the policy to manage the change in the Outlook for Windows app depends on your Microsoft 365 subscription. If you received the Outlook for Windows app Message center notification, please refer to MC541626, MC545904, or MC548092 for details on whether configuring this policy will apply.
If you have not configured the policy, or wish to change it, find the details below. How this will affect your organization:
Links from Teams chats will open based on the browser configuration in the Choose which browser opens web links policy. If no configuration is selected using the Choose which browser opens web links policy, web links from Teams chats will open in Microsoft Edge.
Only links set to open via a web browser are affected. Links that are set to open in a client app or within Teams itself will continue to do so. User experiences will vary by policy configuration; please see the next section.
You can manage this experience at any time. What you need to do to prepare:
If you’ve previously configured this policy for the Outlook for Windows app and wish to maintain that configuration, no action is required.
Use the Choose which browser opens web links policy to configure which default browser will be used to open web links and to set whether users will be able to manage which browser opens web links in both Teams (chat) and the Outlook for Windows app (email). You will not be able to manage each app individually using this policy.
The Choose which browser opens web links policy is available using the Cloud Policy service for Microsoft 365 (formerly the Office Cloud Policy Service) or as part of the Administrative Templates for Microsoft 365 Apps.
Enabled: Configures which browser opens web links from the Teams desktop app for Windows (chat) and the Outlook for Windows app (email):
Microsoft Edge
Web links will open side-by-side with users’ chat or email in Edge.
Default browser
Users will not be able to change this from the respective apps’ settings menus.
Disabled/Unconfigured: Web links from the Teams desktop app for Windows (chat) and the Outlook for Windows app (email) will open in Microsoft Edge.
Web links will open side-by-side with users’ chat or email in Edge.
Users can manage the browser change: Via the in-product notifications explaining the side-by-side experience.
At any time via the Teams settings menu: Settings > Files and links > Link open preferences
Note: If you want to manage this change for your entire organization so that Teams only opens web links using the device’s system default browser, you will need to configure the policy to Enabled and select Default browser.
Additional Information
Read more about how we’re optimizing the experience between Microsoft 365 and Microsoft Edge with this feature in our blog: https://www.microsoft.com/en-us/microsoft-365/blog/2023/02/16/discover-new-ways-to-multitask-with-microsoft-365-and-edge/
We always value feedback and questions from our customers. Please feel free to submit either feedback or questions via Message Center.
That's one of my main problems with Microsoft at this point. They can make improvements to the underlying technologies (WSL, better security sandboxing, FDE by default on supported hardware, etc) and develop actually decent software (Edge) but then they keep doing things to piss off the users like forced online account logins, the mess they made of the default app selection going from 10 to 11, pre-installed junk, and now this. They just need to get out of their own way and focus on making decent products: ones people want to use, instead of ones they're coerced to use.
Edge was my main browser until about six months ago, then they pushed that obnoxious UI change that added a load of buttons to my toolbar that I can't move or disable, and that irritating sidebar that jumps up whenever it can even when the button is disabled, and I went back to Firefox again.
That's part of the annoyance I was mentioning; but you can turn it off. I just wish it wasn't so obnoxious by default.
On the partner portal tech side of things they force a UI change roughly every 6 months, then have a forced “See what’s new!!” Pop up that WONT GO AWAY every time you log in no matter how many times you click through its bubble chase game across the screen so you can just get to fucking work.
Then for some reason the partner portal oauth or whatever cookies expire wayyyy before the office.com user cookies. So you’ll go to access the portal and be told it’s expired, only to have to close the window and click the partner button again. Not even having to actually reauthenticate.
Why do some preview handlers in file explorer lock the file? Why user logon not more verbose? Or able to be verbose on selected problem machines? Why does Windows driver installer uninstall AMD adrenaline sometimes when it feels like turning itself back on? In place upgrades are a recovery option if the machine is still working, but why not if the machine isn’t booting and as a full recovery option with user and application data intact and only reinstalling OS files like Linux and MacOS? Why are all the built-in troubleshooters so fucking useless, especially with SaRA exists? Printer server on Windows server… WTF? Windows app troubleshooting, especially built in apps, the repair options in settings don’t work 90% of the time. You want people to use your storefront? Make it make sense! Quit. Changing. The. Fucking. Names. Of. Shit. You. Fucks. AzureAD was fine. Entra? Who fucking cares. Does some guy get paid to come up with names there? You want me to come smear shit on the walls and call it art? I’m sure I can convince some egghead of that if this is how you work.
I better stop before I have an aneurysm. I hate Microsoft.
If you think that them forcing a browser on you, or forced telemetry, or web-based logons are bad just wait until they enforce desktop in the cloud and remove any option to install Windows locally. Then you'll truly have no control over what you do, what you install, you'll be completely monitored, permenantly. There's a reason workers (with some degree of integrity) are leaving MS as it's crap like this thats on their roadmap.