executed cleanup activities
@ -1,27 +0,0 @@
|
||||
---
|
||||
title: eSIM Enterprise Management
|
||||
description: Learn how Mobile Device Management (MDM) Providers support the eSIM Profile Management Solution on Windows.
|
||||
ms.prod: windows-client
|
||||
author: vinaypamnani-msft
|
||||
ms.localizationpriority: medium
|
||||
ms.author: vinpa
|
||||
ms.topic: conceptual
|
||||
ms.technology: itpro-manage
|
||||
ms.date: 12/31/2017
|
||||
---
|
||||
|
||||
# How Mobile Device Management Providers support eSIM Management on Windows
|
||||
The eSIM Profile Management Solution places the Mobile Device Management (MDM) Provider in the front and center. The whole idea is to use an already-existing solution that customers are familiar with and use to manage devices. The expectations from an MDM are that it will use the same sync mechanism that it uses for device policies to push any policy to the eSIM profile, and be able to use Groups and Users the same way. This way, the eSIM profile download and the installation happen in the background without impacting the end user. Similarly, the IT admin would use the same method of managing the eSIM profiles (Assignment/de-assignment, etc.) the same way as they currently do device management.
|
||||
If you are a Mobile Device Management (MDM) Provider and want to support eSIM Management on Windows, perform the following steps:
|
||||
- Onboard to Azure Active Directory
|
||||
- Contact mobile operators directly or contact orchestrator providers. Windows provides the capability for eSIM profiles to be managed by MDM providers in the case of enterprise use cases. However, Windows does not limit how ecosystem partners might want to offer this to their own partners and/or customers. As such, the eSIM profile management capability is something that can be supported by integrating with the Windows OMA-DM. This makes it possible to remotely manage the eSIM profiles according to the company policies. Contact mobile operators directly or contact orchestrator providers. Windows provides the capability for eSIM profiles to be managed by MDM providers in the case of enterprise use cases. However, Windows does not limit how ecosystem partners might want to offer this capability to their own partners and/or customers. As such, the eSIM profile management capability is something that can be supported by integrating with the Windows OMA-DM. This characteristic makes it possible to remotely manage the eSIM profiles according to the company policies. As an MDM provider, if you are looking to integrate/onboard to a mobile operator on a 1:1 basis, contact them and learn more about their onboarding. If you would like to integrate and work with only one MDM provider, contact that provider directly. If you would like to offer eSIM management to customers using different MDM providers, contact an orchestrator provider. Orchestrator providers act as proxy handling MDM onboarding and as a mobile operator onboarding. Their role is to make the process as painless and scalable as possible for all parties. Potential orchestrator providers you could contact include:
|
||||
- [HPE Device Entitlement Gateway](https://www.hpe.com/emea_europe/en/solutions/digital-communications-services.html)
|
||||
- [IDEMIA The Smart Connect - Hub](https://www.idemia.com/smart-connect-hub)
|
||||
- Assess solution type that you would like to provide your customers
|
||||
- Batch/offline solution
|
||||
- IT Admin can manually import a flat file containing list of eSIM activation codes, and provision eSIM on LTE enabled devices.
|
||||
- Operator doesn't have visibility over status of the eSIM profiles and device eSIM has been downloaded and installed to
|
||||
- Real-time solution
|
||||
- MDM automatically syncs with the Operator backend system for subscription pool and eSIM management, via sim vendor solution component. IT Admin can view subscription pool and provision eSIM in real time.
|
||||
- Operator is notified of the status of each eSIM profile and has visibility on which devices are being used
|
||||
**Note:** End users don't notice the solution type. The choice between the two is made between the MDM and the Mobile Operator.
|
Before Width: | Height: | Size: 237 KiB |
Before Width: | Height: | Size: 220 KiB |
Before Width: | Height: | Size: 140 KiB |
Before Width: | Height: | Size: 381 KiB |
Before Width: | Height: | Size: 15 KiB |
Before Width: | Height: | Size: 195 KiB |
Before Width: | Height: | Size: 23 KiB |
Before Width: | Height: | Size: 514 KiB |
Before Width: | Height: | Size: 10 KiB |
Before Width: | Height: | Size: 284 KiB |
Before Width: | Height: | Size: 120 KiB |
Before Width: | Height: | Size: 91 KiB |
Before Width: | Height: | Size: 164 KiB |
Before Width: | Height: | Size: 931 KiB |
Before Width: | Height: | Size: 424 KiB |
Before Width: | Height: | Size: 73 KiB |
Before Width: | Height: | Size: 3.5 KiB |
Before Width: | Height: | Size: 7.1 KiB |
Before Width: | Height: | Size: 12 KiB |
Before Width: | Height: | Size: 98 KiB |
Before Width: | Height: | Size: 13 KiB |
Before Width: | Height: | Size: 40 KiB |
Before Width: | Height: | Size: 53 KiB |
Before Width: | Height: | Size: 29 KiB |
Before Width: | Height: | Size: 29 KiB |
Before Width: | Height: | Size: 130 KiB |
Before Width: | Height: | Size: 57 KiB |
Before Width: | Height: | Size: 6.7 KiB |
Before Width: | Height: | Size: 94 KiB |
Before Width: | Height: | Size: 100 KiB |
Before Width: | Height: | Size: 177 KiB |
Before Width: | Height: | Size: 455 KiB |
Before Width: | Height: | Size: 80 KiB |
Before Width: | Height: | Size: 82 KiB |
Before Width: | Height: | Size: 61 KiB |
Before Width: | Height: | Size: 267 KiB |
Before Width: | Height: | Size: 82 KiB |
Before Width: | Height: | Size: 44 KiB |
Before Width: | Height: | Size: 49 KiB |
Before Width: | Height: | Size: 245 KiB |
Before Width: | Height: | Size: 164 KiB |
Before Width: | Height: | Size: 39 KiB |
Before Width: | Height: | Size: 82 KiB |
Before Width: | Height: | Size: 136 KiB |
Before Width: | Height: | Size: 503 KiB |
Before Width: | Height: | Size: 395 KiB |
Before Width: | Height: | Size: 84 KiB |
Before Width: | Height: | Size: 9.3 KiB |
Before Width: | Height: | Size: 100 KiB |
Before Width: | Height: | Size: 236 KiB |
Before Width: | Height: | Size: 146 KiB |
Before Width: | Height: | Size: 275 KiB |
Before Width: | Height: | Size: 445 KiB |
Before Width: | Height: | Size: 22 KiB |
Before Width: | Height: | Size: 17 KiB |
Before Width: | Height: | Size: 7.9 KiB |
Before Width: | Height: | Size: 4.1 KiB |
Before Width: | Height: | Size: 24 KiB |
Before Width: | Height: | Size: 7.8 KiB |
@ -1,11 +0,0 @@
|
||||
---
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.date: 10/02/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.prod: edge
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
Since Microsoft Edge is integration with Cortana, Microsoft Edge allows users to use Cortana voice assistant by default. With this policy, you can configure Microsoft Edge to prevent users from using Cortana but can still search to find items on their device.
|
@ -1,11 +0,0 @@
|
||||
---
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.date: 10/02/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.prod: edge
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
Discontinued in Windows 10, version 1809. Use the **[Provision Favorites](../available-policies.md#provision-favorites)** policy instead.
|
@ -1,11 +0,0 @@
|
||||
---
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.date: 10/02/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.prod: edge
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
By default, Microsoft Edge turns on the _Sync your settings_ toggle in **Settings > Device sync settings** letting users choose what to sync on their devices. Enabling this policy turns off and disables the _Sync your settings_ toggle preventing the syncing of user’s settings between their devices. If you want syncing turned off by default in Microsoft Edge but not disabled, enable this policy and select the _Allow users to turn syncing on_ option.
|
@ -1,12 +0,0 @@
|
||||
---
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.date: 04/23/2020
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.prod: edge
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
[Microsoft browser extension policy](/legal/microsoft-edge/microsoft-browser-extension-policy):
|
||||
This article describes the supported mechanisms for extending or modifying the behavior or user experience of Microsoft Edge and Internet Explorer, or the content these browsers display. Techniques that aren't explicitly listed in this article are considered to be **unsupported**.
|
@ -1,11 +0,0 @@
|
||||
---
|
||||
author: dansimp
|
||||
ms.author: dansimp
|
||||
ms.date: 10/02/2018
|
||||
ms.reviewer:
|
||||
manager: dansimp
|
||||
ms.prod: edge
|
||||
ms.topic: include
|
||||
---
|
||||
|
||||
Microsoft Edge follows the OpenSearch 1.1 specification to discover and use web search providers. When a user browses to a search service, the OpenSearch description is picked up and saved for later use. Users can then choose to add the search service to use in the Microsoft Edge address bar.
|