diff --git a/windows/client-management/mdm/esim-enterprise-management.md b/windows/client-management/mdm/esim-enterprise-management.md
new file mode 100644
index 0000000000..1fad0a54a6
--- /dev/null
+++ b/windows/client-management/mdm/esim-enterprise-management.md
@@ -0,0 +1,26 @@
+---
+title: eSIM Enterprise Management
+description: Managing eSIM devices in an enterprise
+keywords: eSIM enterprise management
+ms.prod: w10
+ms.mktglfcycl:
+ms.sitesec: library
+author: dansimp
+ms.localizationpriority: medium
+ms.author: dansimp
+ms.topic: 
+---
+
+# How Mobile Device Management Providers support eSIM Management on Windows
+The eSIM Profile Management Solution puts the Mobile Device Management (MDM) Provider in the front and center. The whole idea is to leverage an already existing solution that customers are familiar with and that they use to manage devices. The expectations from an MDM are that it will leverage 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 installation happens on the background and not 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 would like to support eSIM Management on Windows, you should do the following:
+-	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 Window 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 to their own partners and/or customers. As such, the eSIM profile management capability is something that can be supported by integrating with the Window OMA-DM. This 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, please contact them and learn more about their onboarding. If you would like to support multiple mobile operators, [orchestrator providers]( https://www.idemia.com/esim-management-facilitation) are there to act as a proxy that will handle MDM onboarding as well as mobile operator onboarding. Their main [role]( https://www.idemia.com/smart-connect-hub) is to enable the process to be as painless but scalable to all parties. 
+-	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 does not 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:** The solution type is not noticeable to the end-user. The choice between the two is made between the MDM and the Mobile Operator.