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.
Why Void Linux specifically?
Probably that Microsoft Windows in its current form makes you want to crawl into a void.
Recommendation by my gf mostly. But i can see where she comes from. The OS is very lean and runit is easy to deal with.
A disadvantage i see though is the lack of Calamares installer and XBPS. The void-installer isn't that intuitive, however it's not as tough as installing Arch manually (SomeOrdinaryGamers made a fun video about it). XBPS isn't as intuitive as APT either but apparently it's much more solid and has less potential to break the Void install. Some packages are also not available in the void repos because they are either merged into other packages for simplicity or they are simply not available. In the latter case i recommend using flatpak.
Another caveat is that while Void has an established userbase, there are so much more resources for Ubuntu and other distros. So Void isn't exactly good for a computer novice like my mom. Void has a good website with resources for common use-cases, so you're not left to your own devices entirely.
Once you're done setting up Void, you have a very snappy system. It boots fast and uses little resources. It uses 800 megabytes of RAM on my GPD Win 2, 200 of which think are from KDE. It is lean! It is so lean and it boots fast! It has a properly working standby mode which is not a given anymore these days! I can open up my GPD and it powers up reliably! Back on Windows ifound myself mashing the power button!
I installed it on another laptop, specifically a Sony VAIO Flip 15. I wanted to test it first but the VAIO didn't like booting twice from an external drive. HOLY CRAP, BLUETOOTH IS WORKING AGAIN! I KNEW WINDOWS BROKE BLUETOOTH! FUCK THEIR "muh pci powerup failed" EXCUSE! Although i had to replace the Qualcomm Atheros AR9462 with my Intel Wireless AC-7260 because Atheros cards are iffy on Linux in general. I had the Intel one laying around because i was trying to ix the Bluetooth issue caused by a Windows Update.
And Void can be loud! Both of my systems i installed Void on are louder now! Holy crap! Not sure whether it's specifically because of Void but damn! I love an OS that makes the very core stuff that i don't usually think about work better! Except for some WiFi slowdown on my Win 2 but a config tweak later it's gone. And the Atheros thing.
I initially thought Windows gaming on Linux was still not good, however it turned out that a few games i have don't like being just plonked on a system without a proper install. There is a caveat remaining but that isn't exclusive to Void and that is some weirdness when it comes to old physical Windows games. Multi-CD games aren't properly supported and some CDs aren't working too well for some reason. For example CD 2 of SimCity 4 isn't read correctly.
Thank you! Nice thorough explanation.