Some settings are not available or listed in Intune though Administrative template setting or device configuration polices for selection. In those cases Open Mobile Alliance Uniform Resource Identifier (OMA-URI) comes into play, OMA-URI are designed to add device settings and features that aren’t built in to Intune. But if the environment are configure as Hybrid Azure AD Join setup, this setting can be controlled by on-prem GPO ADMX templates setting “Prevent the First Run webpage from opening on Microsoft Edge”
In this scenario we test a OMA-URI setting on a Azure AD joined Windows 10 device that should prevent the first run webpage (welcome page) from appearing on the first time a user opens Microsoft Edge. The specific OMA-URI setting and general Edge settings can be found here -> https://docs.microsoft.com/en-us/microsoft-edge/deploy/available-policies
See this video on how to configure a OMA-URI setting that prevents the first run page on Microsoft Edge to appear and how to assign the custom device configuration profile subsequently to the Windows 10 device/s.
Or you can skip this video and follow the traditional blog post on how to configure and assign this setting to a Windows 10 device.
Note: Profile Type “Custom” is the only way to add OMA-URI settings in Intune.
Note: You can find the OMA-URI settings and values for Edge here -> https://docs.microsoft.com/en-us/microsoft-edge/deploy/available-policies
Note: Finally after a few minutes the agent connects to the client. This can take up til 10 min.