Just wondering if anyone has had success doing this?

Our organization is changing and most of are users will be on F3 licenses.

Most of our users cannot update the built-in Mail app on Win10/11 to Outlook New as we block the MS Store.

So the solution to that is we create a PWA for Outlook for each user that calls in but I would prefer to automate this and push out to all users or prefer to target ones that have F3 license only.

I did use some online resources but they do not appear to work for me.

Deploying Remote Apps with Intune | Remote Desktop > uses JSON I think to do this

Deploying Office WebApps (PWA) with file handlers via Intune – Andrew Taylor > this is the one I tried

I've created the Configuration Profile in Intune and used these settings for Microsoft Edge:

Microsoft Edge

------------------------------------------------------------------------

Configure list of force-installed Web Apps (User)

Enabled

URLs for Web Apps to be silently installed. (User)

[ { "url": "https://www.outlook.office.com/mail", "custom_name": "Outlook(PWA)", "create_desktop_shortcut": true, "default_launch_container": "window", "fallback_app_name": "Outlook PWA", } ]

Issue - I get the shortcut on the desktop but when I launch it I get a DNS error instead.

EDIT - I asked CoPilot to review my syntax and it found that I had an extra comma after the fallback_app_name so now I got it working. Unfortunately in order to auto-pin to task bar I would have to combine it with a Powershell script.

Correct JSON syntax when you make the profile should be like this:

[
  {
    "url": "https://outlook.office.com/mail/",
    "custom_name": "Outlook (PWA)",
    "create_desktop_shortcut": true,
    "default_launch_container": "window",
    "fallback_app_name": "Outlook PWA"
  }
]

Basically title.

For all its faults, including it lacking functionality as basic as reordering folders, the "New Outlook" has finally given me a search experience that is on par with gmail. This may be unpopular, but I really hope they can refine it in time as the lack of local caching from this web based client could really take some pressure off my L1 type requests. The truth is most users are just used to web apps and being plugged directly into their cloud data.

And don't get me started with users who "lost all their contacts" because they've never actually made a contact before and their autocomplete list didn't export from their last device. This was such a problem during our O365 migration that I made a VB script to convert all their sent recipients to contacts.