Jan 22 2021 02:12 PM
Jan 22 2021 02:12 PM
Today, we’re launching an experience experiment for sites or Progressive Web Apps (PWAs) that are installed as apps on your desktop. This is on by default if you are using Windows 10 version 2004 or newer.
If you install the same site or PWA on more than one Edge profile, we’ve introduced a profile switcher on the application title bar to switch between profiles from within your app. With this experiment, you’ll only see one application tile in Windows for that application. Also, when the application starts, it uses the last profile used by the application.
To switch between profiles in your application, perform the following steps:
1. Locate the profile icon on the title bar of your application, and select it.
2. Now, simply select the other profile to use.
3. Confirm that a second application window starts with the selected profile.
Note: The profile switcher in the title bar only displays when you have the same app installed on more than one profile.
We’re looking for feedback on this feature. Here are a couple of questions for you:
We’d love to hear from you. Please send feedback using the “Send Feedback” feature (Alt + Shift + I) from within Microsoft Edge.
Jan 25 2021 10:09 AM
Jan 28 2021 11:14 AM
I think PWA / Lite app is an awesome feature and makes work easier.
Some improvements suggested:
That's all for now.
A 1st year Undergraduate
Feb 02 2021 07:04 AM
@josh_bodner For me this is a case-by-case basis. I work with three O365 Tenants, so I have 3 separate installations of the Outlook Web App (one in each browser profile). And I need to (1) have all inboxes open separately and (2) be able to see incoming email from them all separately as well.
Oct 25 2022 01:22 PM
In a corporate environment, accountability is a must. So we would not have multiple PWA profiles created within a single Windows profile.
Our expectation is that every user is signed into Windows using their own credentials. On virtual desktops where we would use Outlook PWA, there would be one profile, associated with the logged in user.
What we need is a way to install the Outlook PWA on the default profile, without it being associated with an account. So when a new user logs into the virtual desktop, the Outlook PWA is already installed, and they need only provide their credentials to access their mail account.
We would use the same principal to build system images to deploy new workstations.
Is this possible?
Jul 24 2023 09:59 AM
Today this feature stopped working all the sudden.
Teams PWA now opened edge browser rather than the PWA app, even with removing profiles to the single one that is synced, this no longer works.
It would seem that adding in features to Edge that are not aligned with Teams reduces the functionality, rather than increasing it. Over the past months, this "edge features" integration is becoming more of a pain than anything else. The fact that edge prompts to "switch profiles" and then doesnt remember the selection, prompts many times as OAUTH redirects are going through shows this feature needs a lot more work.
As a result today, im back to Teams Browser version, having to remove all EDGE Profiles and still logging in manually, the worst part is the "Teams Service Status" continued to provide updates to duplicated Teams lists (a ticket open for months and months, yet there is nothing about the almost daily "downtimes" for the past two weeks anywhere to be found.