|Applies to: Intune in the classic portal|
|Looking for documentation about the Intune Azure portal preview? Go here.|
The managed browser is a web browsing application that you can deploy in your organization by using Microsoft Intune. A managed browser policy configures an allow list or a block list that restricts the websites that users of the managed browser can visit.
Because this app is a managed app, you can also apply mobile application management policies to the app. These policies might include controlling the use of cut, copy, and paste, preventing screen captures, and ensuring that links to content that users select open only in other managed apps. For details, see Configure and deploy mobile application management policies in the Microsoft Intune console.
If users install the managed browser from the app store and Intune does not manage it, the following behavior applies:
iOS – The managed browser app can be used as a basic web browser, but some features will not be available, and it will not be able to access data from other Intune-managed apps.
Android – The managed browser app cannot be used.
If users install the managed browser themselves on an iOS device with a version earlier than iOS 9, no policies that you create will manage the browser. To ensure that Intune manages the browser, users must uninstall the app before you can deploy it to them as a managed app. On iOS 9 and later, if users install the managed browser themselves, they will be prompted to allow it to become managed by policy.
You can create managed browser policies for the following device types:
Devices that run Android 4 and later
Devices that run iOS 8.0 and later
The Intune managed browser supports opening web content from Microsoft Intune application partners.
Create a managed browser policy
In the Microsoft Intune administration console, choose Policy > Add Policy.
Configure one of the following Software policy types:
Managed Browser (Android 4 and later)
Managed Browser (iOS 8.0 and later)
For more information about how to create and deploy policies, see the Manage settings and features on your devices with Microsoft Intune Policies topic.
Use the following to help you configure the managed browser policy settings:
- Name. Enter a unique name for the managed browser policy to help you identify it in the Intune console.
- Description. Provide a description that gives an overview of the managed browser policy and other relevant information that helps you to locate it.
- Enable an allow list or block list to restrict the URLs the Managed Browser can open. Select one of the following options:
- Allow the managed browser to open only the URLs listed below. Specify a list of URLs that the managed browser can open.
- Block the managed browser from opening the URLs listed below. Specify a list of URLs that the managed browser will be blocked from opening. Note: You cannot include both allowed and blocked URLs in the same managed browser policy. For more information about the URL formats you can specify, see URL format for allowed and blocked URLs in this topic.
When you are finished, choose Save Policy.
The new policy appears in the Configuration Policies node of the Policy workspace.
Create a deployment for the managed browser app
After you have created the managed browser policy, you can then create a software deployment for the managed browser app, and associate it with the managed browser policy that you created.
Managed browser policies are not deployed in the same way as other Intune polices. This type of policy must be associated with the managed browser software package.
Deploy the app, ensuring that you select the managed browser policy on the Mobile App Management page to associate the policy with the app.
For more information about how to deploy apps, see Deploy apps in Microsoft Intune.
Security and privacy for the managed browser
On iOS devices, websites that users visit that have an expired or untrusted certificate cannot be opened.
The managed browser does not use settings that users make for the built-in browser on their devices. This is because the managed browser does not have access to these settings.
If you configure the option Require simple PIN for access or Require corporate credentials for access in a mobile application management policy associated with the managed browser, and a user selects the help link on the authentication page, they can then browse any Internet sites regardless of whether they were added to a block list in the managed browser policy.
The managed browser can block access to sites only when they are accessed directly. It cannot block access when intermediate services (such as a translation service) are used to access the site.
To allow authentication, and to ensure that the Intune documentation can be accessed,*.microsoft.com is exempt from the allow or block list settings. It is always allowed.
Turn off usage data
Microsoft automatically collects anonymous data about the performance and use of the managed browser to improve Microsoft products and services. Users can turn off data collection by using the Usage Data setting on their devices. You have no control over the collection of this data.
URL format for allowed and blocked URLs
Use the following information to learn about the allowed formats and wildcards that you can use when specifying URLs in the allowed and blocked lists:
You can use the wildcard symbol (*) according to the rules in the following permitted patterns list.
Ensure that you prefix all URLs with http or https when entering them into the list.
You can specify port numbers in the address. If you do not specify a port number, the values used will be:
Port 80 for http
Port 443 for https
Using wildcards for the port number is not supported. For example, http://www.contoso.com:*; and http://www.contoso.com: /*; are not supported.
Use the following table to learn about the permitted patterns that you can use when you specify URLs:
|URL||Details||Matches||Does not match|
|http://www.contoso.com||Matches a single page||www.contoso.com||host.contoso.com
|http://contoso.com||Matches a single page||contoso.com/||host.contoso.com
|http://www.contoso.com/*;||Matches all URLs that begin with www.contoso.com||www.contoso.com
|http://*.contoso.com/*||Matches all subdomains under contoso.com||developer.contoso.com/resources
|http://www.contoso.com/images||Matches a single folder||www.contoso.com/images||www.contoso.com/images/dogs|
|http://www.contoso.com:80||Matches a single page, by using a port number||http://www.contoso.com:80|
|https://www.contoso.com||Matches a single, secure page||https://www.contoso.com||http://www.contoso.com|
|http://www.contoso.com/images/*;||Matches a single folder and all subfolders||www.contoso.com/images/dogs
The following are examples of some of the inputs that you cannot specify:
How conflicts between the allow and block list are resolved
If multiple managed browser policies are deployed to a device and the settings conflict, both the mode (allow or block) and the URL lists are evaluated for conflicts. In case of a conflict, the following behavior applies:
If the modes in each policy are the same, but the URL lists are different, the URLs will not be enforced on the device.
If the modes in each policy are different, but the URL lists are the same, the URLs will not be enforced on the device.
If a device is receiving managed browser policies for the first time and two policies conflict, the URLs will not be enforced on the device. Use the Policy Conflicts node of the Policy workspace to view the conflicts.
If a device has already received a managed browser policy and a second policy is deployed with conflicting settings, the original settings remain on the device. Use the Policy Conflicts node of the Policy workspace to view the conflicts.