In part 1 of this series I covered some of the planning considerations, in part 2 I covered deployment, and now it’s time to cover ongoing management. The main focus here is configuring Edge via Intune in the Microsoft Endpoint Manager admin center.
Get started by signing in at devicemanagement.microsoft.com and navigate to Devices, Windows, Configuration profiles and then Create profile.
Next choose Administrative Templates with Windows 10 and later as the platform.
Here you can see that we have a choice of Admin templates, including Edge, which we select.
At the time of writing there are 17 pages of settings, a mix of user and device settings. You can filter easily using the search field, as well as sorting by column including the settings are configured.
You can click on the settings to see more information on what each provides, or alternatively you can jump over to the Browser policy reference to browser through settings. Before I wrap up, I want to spend a moment on Edge Sync versus Enterprise State Roaming, in case you’ve been seeing behaviours different to what you expect..
Microsoft Edge Sync replaces Enterprise State Roaming for browser synchronisation on Windows 10, so there will be a few differences to be aware of.
Classic Edge supports
- Open tabs (sessions)
- Settings (preferences)
While the new Edge has a few that are still in development.
- Addresses and more (form-fill)
- Open tabs [Coming soon]
- History [Coming soon]
- Extensions [Coming soon]
Note that this information applies to Azure Active Directory based profiles, not to Microsoft Accounts. While the pre-requisites say AAD Premium or O365 E3 and above are required, if you keep reading you see that Azure Information Protection is also a supported license, dodging that “is it or isn’t it” scenario that tends to come up in Microsoft 365 Business discussions.
Why the move away from Enterprise State Roaming? This was very Windows focused, and with the new Edge being supported on Windows, MacOS, Android and iOS, changes were needed. Hopefully we see the feature gap in sync closing soon, and with the rapid update cycle I’m sure we’ll see these soon.