| Method | -Request URI | -
|---|---|
GET |
-https://bspmts.mp.microsoft.com/V1/Inventory/{productId}/{skuId}/Seats?continuationToken={ContinuationToken}&maxResults={MaxResults} |
-
| Parameter | -Type | -Description | -
|---|---|---|
productId |
-string |
-Required. Product identifier for an application that is used by the Store for Business. |
-
skuId |
-string |
-Required. Product identifier that specifies a specific SKU of an application. |
-
continuationToken |
-string |
-Optional. |
-
maxResults |
-int32 |
-Optional. Default = 25, Maximum = 100 |
-
| Error code | -Description | -Retry | -Data field | -
|---|---|---|---|
400 |
-Invalid parameters |
-No |
-Parameter name -Reason: Missing parameter or invalid parameter -Details: String |
-
404 |
-Not found |
-- | - |
409 |
-Conflict |
-- | Reason: Not online |
-
| DHA-Service type | -Description | -Operation cost | -
|---|---|---|
| Device Health Attestation – Cloud (DHA-Cloud) |
-DHA-Cloud is a Microsoft owned and operated DHA-Service that is: -
| No cost | - -
| Device Health Attestation – On Premise (DHA-OnPrem) |
-DHA-OnPrem refers to DHA-Service that is running on premises: -
|
-The operation cost of running one or more instances of Server 2016 on-premises. | -
| Device Health Attestation - Enterprise-Managed Cloud (DHA-EMC) |
-DHA-EMC refers to an enterprise-managed DHA-Service that is running as a virtual host/service on a Windows Server 2016 compatible - enterprise-managed cloud service, such as Microsoft Azure. -
|
-The operation cost of running Server 2016 on a compatible cloud service, such as Microsoft Azure. | -
| Error code | -Error name | -Description | -
|---|---|---|
| 0 | -HEALTHATTESTATION_CERT_RETRIEVAL_UNINITIALIZED | -This is the initial state for devices that have never participated in a DHA-Session. | -
| 1 | -HEALTHATTESTATION_CERT_RETRIEVAL_REQUESTED | -This state signifies that MDM client’s Exec call on the node VerifyHealth has been triggered and now the OS is trying to retrieve DHA-EncBlob from DHA-Server. | -
| 2 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED | -This state signifies that the device failed to retrieve DHA-EncBlob from DHA-Server. | -
| 3 | -HEALTHATTESTATION_CERT_RETRIEVAL_COMPLETE | -This state signifies that the device has successfully retrieved DHA-EncBlob from the DHA-Server. | -
| 4 | -HEALTHATTESTATION_CERT_RETRIEVAL_PCR_FAIL | -Deprecated in Windows 10, version 1607. | -
| 5 | -HEALTHATTESTATION_CERT_RETRIEVAL_GETQUOTE_FAIL | -DHA-CSP failed to get a claim quote. | -
| 6 | -HEALTHATTESTATION_CERT_RETRIEVAL_DEVICE_NOT_READY | -DHA-CSP failed in opening a handle to Microsoft Platform Crypto Provider. | -
| 7 | -HEALTHATTESTATION_CERT_RETRIEVAL_WINDOWS_AIK_FAIL | -DHA-CSP failed in retrieving Windows AIK | -
| 8 | -HEALTHATTESTATION_CERT_RETRIEVAL_FROM_WEB_FAIL | -Deprecated in Windows 10, version 1607. | -
| 9 | -HEALTHATTESTATION_CERT_RETRIEVAL_INVALID_TPM_VERSION | -Invalid TPM version (TPM version is not 1.2 or 2.0) | -
| 10 | -HEALTHATTESTATION_CERT_RETRIEVAL_GETNONCE_FAIL | -Nonce was not found in the registry. | -
| 11 | -HEALTHATTESTATION_CERT_RETRIEVAL_GETCORRELATIONID_FAIL | -Correlation ID was not found in the registry. | -
| 12 | -HEALTHATTESTATION_CERT_RETRIEVAL_GETCERT_FAIL | -Deprecated in Windows 10, version 1607. | -
| 13 | -HEALTHATTESTATION_CERT_RETRIEVAL_GETCLAIM_FAIL | -Deprecated in Windows 10, version 1607. | -
| 14 | -HEALTHATTESTATION_CERT_RETRIEVAL_ENCODING_FAIL | -Failure in Encoding functions. (Extremely unlikely scenario) | -
| 15 | -HEALTHATTESTATION_CERT_RETRIEVAL_ENDPOINTOVERRIDE_FAIL | -Deprecated in Windows 10, version 1607. | -
| 16 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_LOAD_XML | -DHA-CSP failed to load the payload it received from DHA-Service | -
| 17 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_CORRUPT_XML | -DHA-CSP received a corrupted response from DHA-Service. | -
| 18 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_EMPTY_XML | -DHA-CSP received an empty response from DHA-Service. | -
| 19 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_DECRYPT_AES_EK | -DHA-CSP failed in decrypting the AES key from the EK challenge. | -
| 20 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_DECRYPT_CERT_AES_EK | -DHA-CSP failed in decrypting the health cert with the AES key. | -
| 21 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_EXPORT_AIKPUB | -DHA-CSP failed in exporting the AIK Public Key. | -
| 22 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_CREATE_CLAIMAUTHORITYONLY | -DHA-CSP failed in trying to create a claim with AIK attestation data. | -
| 23 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_APPEND_AIKPUB | -DHA-CSP failed in appending the AIK Pub to the request blob. | -
| 24 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_APPEND_AIKCERT | -DHA-CSP failed in appending the AIK Cert to the request blob. | -
| 25 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_INIT_HTTPHANDLE | -DHA-CSP failed to obtain a Session handle. | -
| 26 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_GETTARGET_HTTPHANDLE | -DHA-CSP failed to connect to the DHA-Service. | -
| 27 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_CREATE_HTTPHANDLE | -DHA-CSP failed to create an HTTP request handle. | -
| 28 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_SET_INTERNETOPTION | -DHA-CSP failed to set options. | -
| 29 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_ADD_REQUESTHEADERS | -DHA-CSP failed to add request headers. | -
| 30 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_SEND_REQUEST | -DHA-CSP failed to send the HTTP request. | -
| 31 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_RECEIVE_RESPONSE | -DHA-CSP failed to receive a response from the DHA-Service. | -
| 32 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_QUERY_HEADERS | -DHA-CSP failed to query headers when trying to get HTTP status code. | -
| 33 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_EMPTY_RESPONSE | -DHA-CSP received an empty response from DHA-Service even though HTTP status was OK. | -
| 34 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_MISSING_RESPONSE | -DHA-CSP received an empty response along with an HTTP error code from DHA-Service. | -
| 35 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_IMPERSONATE_USER | -DHA-CSP failed to impersonate user. | -
| 36 | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_ACQUIRE_PDCNETWORKACTIVATOR | -DHA-CSP failed to acquire the PDC activators that are needed for network communication when the device is in Connected standby mode. | -
| 0xFFFF | -HEALTHATTESTATION_CERT_RETRIEVAL_FAILED_UNKNOWN | -DHA-CSP failed due to an unknown reason, this error is highly unlikely to occur. | -
| 400 | -Bad_Request_From_Client | -DHA-CSP has received a bad (malformed) attestation request. | -
| 404 | -Endpoint_Not_Reachable | -DHA-Service is not reachable by DHA-CSP | -
| Value | -Description | -
|---|---|
ENTITLEMENT_SUCCESS |
-The device is allowed to connect to the server. |
-
ENTITLEMENT_FAILED |
-The device is not allowed to connect to the server |
-
ENTITLEMENT_UNAVAILABLE |
-The entitlement check failed because the device could not contact the server or acquire a connection to verify entitlement. |
-
| Update channel | -Primary purpose | -LOB Tattoo availability | -Default update channel for the products | -
|---|---|---|---|
| Current channel | -Provide pilot users and application compatibility testers the opportunity to test the next Deferred Channel. | -March 9 2017 | -Visio Pro for Office 365 -Project Desktop Client -Microsoft 365 Apps for business (the version of Office that comes with some Microsoft 365 plans, such as Business Premium.) |
-
| Deferred channel | -Provide users with new features of Office only a few times a year. | -October 10 2017 | -Microsoft 365 Apps for enterprise | -
| First release for Deferred channel | -Provide pilot users and application compatibility testers the opportunity to test the next Deferred Channel. | -June 13 2017 | -- |
Application data |
-The Store for Business service provides metadata for the applications that have been acquired via the Store for Business. This includes the application identifier that is used to deploy online license applications, artwork for an application that is used to create a company portal, and localized descriptions for applications. |
-
Licensing models |
-Offline vs. Online -Online-licensed applications require connectivity to the Microsoft Store. Users require an Azure Active Directory identity and rely on the store services on the device to be able to acquire an application from the store. It is similar to how applications are acquired from the Microsoft Store using a Microsoft account. Assigning or reclaiming seats for an application require a call to the Store for Business services. -Offline-licensed applications enable an organization to use the application for imaging and for devices that may not have connectivity to the store or may not have Azure Active Directory. Offline-licensed application do not require connectivity to the store, however it can be updated directly from the store if the device has connectivity and the app update policies allow updates to be distributed via the store. |
-
| Namespace | -Subcode | -Error | -Description | -HRESULT | -
|---|---|---|---|---|
s: |
-MessageFormat |
-MENROLL_E_DEVICE_MESSAGE_FORMAT_ERROR |
-Invalid message from the Mobile Device Management (MDM) server. |
-80180001 |
-
s: |
-Authentication |
-MENROLL_E_DEVICE_AUTHENTICATION_ERROR |
-The Mobile Device Management (MDM) server failed to authenticate the user. Try again or contact your system administrator. |
-80180002 |
-
s: |
-Authorization |
-MENROLL_E_DEVICE_AUTHORIZATION_ERROR |
-The user is not authorized to enroll to Mobile Device Management (MDM). Try again or contact your system administrator. |
-80180003 |
-
s: |
-CertificateRequest |
-MENROLL_E_DEVICE_CERTIFICATEREQUEST_ERROR |
-The user has no permission for the certificate template or the certificate authority is unreachable. Try again or contact your system administrator. |
-80180004 |
-
s: |
-EnrollmentServer |
-MENROLL_E_DEVICE_CONFIGMGRSERVER_ERROR |
-The Mobile Device Management (MDM) server encountered an error. Try again or contact your system administrator. | -80180005 |
-
a: |
-InternalServiceFault |
-MENROLL_E_DEVICE_INTERNALSERVICE_ERROR |
-There was an unhandled exception on the Mobile Device Management (MDM) server. Try again or contact your system administrator. |
-80180006 |
-
a: |
-InvalidSecurity |
-MENROLL_E_DEVICE_INVALIDSECURITY_ERROR |
-The Mobile Device Management (MDM) server was not able to validate your account. Try again or contact your system administrator. |
-80180007 |
-
| Subcode | -Error | -Description | -HRESULT | -
|---|---|---|---|
DeviceCapReached |
-MENROLL_E_DEVICECAPREACHED |
-The account has too many devices enrolled to Mobile Device Management (MDM). Delete or unenroll old devices to fix this error. |
-80180013 |
-
DeviceNotSupported |
-MENROLL_E_DEVICENOTSUPPORTED |
-The Mobile Device Management (MDM) server doesn't support this platform or version, consider upgrading your device. |
-80180014 |
-
NotSupported |
-MENROLL_E_NOT_SUPPORTED |
-Mobile Device Management (MDM) is generally not supported for this device. |
-80180015 |
-
NotEligibleToRenew |
-MENROLL_E_NOTELIGIBLETORENEW |
-The device is attempting to renew the Mobile Device Management (MDM) certificate, but the server rejected the request. Check renew schedule on the device. |
-80180016 |
-
InMaintenance |
-MENROLL_E_INMAINTENANCE |
-The Mobile Device Management (MDM) server states your account is in maintenance, try again later. |
-80180017 |
-
UserLicense |
-MENROLL_E_USER_LICENSE |
-There was an error with your Mobile Device Management (MDM) user license. Contact your system administrator. |
-80180018 |
-
InvalidEnrollmentData |
-MENROLL_E_ENROLLMENTDATAINVALID |
-The Mobile Device Management (MDM) server rejected the enrollment data. The server may not be configured correctly. |
-80180019 |
-
| ADDRTYPE Value | -Connection Type | -
|---|---|
E164 |
-RAS connections |
-
APN |
-GPRS connections |
-
ALPHA |
-Wi-Fi-based connections |
-
| Elements | -Available | -
|---|---|
Parm-query |
-Yes -Note that some GPRS parameters will not necessarily contain the exact same value as was set. |
-
Noparm |
-Yes |
-
Nocharacteristic |
-Yes |
-
Characteristic-query |
-Yes |
-
| Status | -Description | -Comment | -
|---|---|---|
| 0 | -Installation succeeded | -OK | -
| 997 | -Installation in progress | -- |
| 13 | -ERROR_INVALID_DATA
- Cannot verify signature of the downloaded Office Deployment Tool (ODT) |
-Failure | -
| 1460 | -ERROR_TIMEOUT
- Failed to download ODT |
-Failure | -
| 1602 | -ERROR_INSTALL_USEREXIT
- User cancelled the installation |
-Failure | -
| 1603 | -ERROR_INSTALL_FAILURE
- Failed any pre-req check. -
|
-Failure | -
| 17000 | -ERROR_PROCESSPOOL_INITIALIZATION
- Failed to start C2RClient |
-Failure | -
| 17001 | -ERROR_QUEUE_SCENARIO
- Failed to queue installation scenario in C2RClient |
-Failure | -
| 17002 | -ERROR_COMPLETING_SCENARIO
- Failed to complete the process. Possible reasons: -
|
-Failure | -
| 17003 | -ERROR_ANOTHER_RUNNING_SCENARIO
- Another scenario is running |
-Failure | -
| 17004 | -ERROR_COMPLETING_SCENARIO_NEED_CLEAN_UP
- Possible reasons: -
|
-Failure | -
| 17005 | -ERROR_SCENARIO_CANCELLED_AS_PLANNED | -Failure | -
| 17006 | -ERROR_SCENARIO_CANCELLED
- Blocked update by running apps |
-Failure | -
| 17007 | -ERROR_REMOVE_INSTALLATION_NEEDED
- The client is requesting client clean up in a "Remove Installation" scenario |
-Failure | -
| 17100 | -ERROR_HANDLING_COMMAND_LINE
- C2RClient command line error |
-Failure | -
| 0x80004005 | -E_FAIL
- ODT cannot be used to install Volume license |
-Failure | -
| 0x8000ffff | -E_UNEXPECTED
- Tried to uninstall when there is no C2R Office on the machine. |
-Failure | -
| General area | -OMA DM standard that is supported | -
|---|---|
Data transport and session |
-
|
-
Bootstrap XML |
-
|
-
DM protocol commands |
-The following list shows the commands that are used by the device. For further information about the OMA DM command elements, see "SyncML Representation Protocol Device Management Usage (OMA-SyncML-DMRepPro-V1_1_2-20030613-A)" available from the OMA website. -
If an XML element that is not a valid OMA DM command is under one of the following elements, the status code 400 is returned for that element: -
If no CmdID is provided in the DM command, the client returns blank in the status element and the status code 400. -If Atomic elements are nested, the following status codes are returned: -
For more information about the Atomic command, see OMA DM protocol common elements. -Performing an Add command followed by Replace on the same node within an Atomic element is not supported. -LocURI cannot start with "/". -Meta XML tag in SyncHdr is ignored by the device. |
-
OMA DM standard objects |
-
|
-
Security |
-
|
-
Nodes |
-In the OMA DM tree, the following rules apply for the node name: -
|
-
Provisioning Files |
-Provisioning XML must be well formed and follow the definition in SyncML Representation Protocol specification. -If an XML element that is not a valid OMA DM command is under SyncBody, the status code 400 is returned for that element. -
-Note
-To represent a Unicode string as a URI, first encode the string as UTF-8. Then encode each of the UTF-8 bytes using URI encoding. -
-
- |
-
WBXML support |
-Windows supports sending and receiving SyncML in both XML format and encoded WBXML format. This is configurable by using the DEFAULTENCODING node under the w7 APPLICATION characteristic during enrollment. For more information about WBXML encoding, see section 8 of the SyncML Representation Protocol specification. |
-
Handling of large objects |
-In Windows 10, version 1511, client support for uploading large objects to the server was added. |
-
| Element | -Description | -
|---|---|
Chal |
-Specifies an authentication challenge. The server or client can send a challenge to the other if no credentials or inadequate credentials were given in the original request message. |
-
Cmd |
-Specifies the name of an OMA DM command referenced in a Status element. |
-
CmdID |
-Specifies the unique identifier for an OMA DM command. |
-
CmdRef |
-Specifies the ID of the command for which status or results information is being returned. This element takes the value of the CmdID element of the corresponding request message. |
-
Cred |
-Specifies the authentication credential for the originator of the message. |
-
Final |
-Indicates that the current message is the last message in the package. |
-
LocName |
-Specifies the display name in the Target and Source elements, used for sending a user ID for MD5 authentication. |
-
LocURI |
-Specifies the address of the target or source location. If the address contains a non-alphanumeric character, it must be properly escaped according to the URL encoding standard. |
-
MsgID |
-Specifies a unique identifier for an OMA DM session message. |
-
MsgRef |
-Specifies the ID of the corresponding request message. This element takes the value of the request message MsgID element. |
-
RespURI |
-Specifies the URI that the recipient must use when sending a response to this message. |
-
SessionID |
-Specifies the identifier of the OMA DM session associated with the containing message. -
-Note If the server does not notify the device that it supports a new version (through SyncApplicationVersion node in the DMClient CSP), the desktop client returns the SessionID in integer in decimal format and the mobile device client returns 2 bytes as a string. If the server supports DM session sync version 2.0, which is used in Windows 10, the desktop and mobile device client returns 2 bytes.
-
-
-
- |
-
Source |
-Specifies the message source address. |
-
SourceRef |
-Specifies the source of the corresponding request message. This element takes the value of the request message Source element and is returned in the Status or Results element. |
-
Target |
-Specifies the address of the node, in the DM Tree, that is the target of the OMA DM command. |
-
TargetRef |
-Specifies the target address in the corresponding request message. This element takes the value of the request message Target element and is returned in the Status or Results element. |
-
VerDTD |
-Specifies the major and minor version identifier of the OMA DM representation protocol specification used to represent the message. |
-
VerProto |
-Specifies the major and minor version identifier of the OMA DM protocol specification used with the message. |
-
| Step | -Action | -Description | -
|---|---|---|
1 |
-DM client is invoked to call back to the management server -Enterprise scenario – The device task schedule invokes the DM client. |
-The MO server sends a server trigger message to invoke the DM client. -The trigger message includes the server ID and tells the client device to initiate a session with the server. The client device authenticates the trigger message and verifies that the server is authorized to communicate with it. -Enterprise scenario - At the scheduled time, the DM client is invoked periodically to call back to the enterprise management server over HTTPS. |
-
2 |
-The device sends a message, over an IP connection, to initiate the session. |
-This message includes device information and credentials. The client and server do mutual authentication over an SSL channel or at the DM application level. |
-
3 |
-The DM server responds, over an IP connection (HTTPS). |
-The server sends initial device management commands, if any. |
-
4 |
-The device responds to server management commands. |
-This message includes the results of performing the specified device management operations. |
-
5 |
-The DM server terminates the session or sends another command. |
-The DM session ends, or Step 4 is repeated. |
-
| Edition | -Windows 10 | -Windows 11 | -
|---|---|---|
| Home | -No | -No | -
| Pro | -Yes | -Yes | -
| Enterprise | -Yes | -Yes | -
| Education | -Yes | -Yes | -
| Edition | -Windows 10 | -Windows 11 | -
|---|---|---|
| Home | -No | No | -
| Pro | -Yes, starting in Windows 10, version 1607 | Yes | -
| Enterprise | -Yes, starting in Windows 10, version 1607 | Yes | -
| Education | -Yes, starting in Windows 10, version 1607 | Yes | -
| Edition | -Windows 10 | -Windows 11 | -
|---|---|---|
| Home | -No | -No | -
| Pro | -Yes | -Yes | -
| Enterprise | -Yes | -Yes | -
| Education | -Yes | -Yes | -
| Mobile | -Yes | -Yes | -
| Mobile Enterprise | -Yes | -Yes | -
| Edition | -Windows 10 | -Windows 11 | -
|---|---|---|
| Home | -No | -No | -
| Pro | -Yes | -Yes | -
| Business | -Yes | -Yes | -
| Enterprise | -Yes | -Yes | -
| Education | -Yes | -Yes | -
| Mobile | -Yes | -Yes | -
| Mobile Enterprise | -Yes | -Yes | -
| Edition | -Windows 10 | -Windows 11 | -
|---|---|---|
| Home | -No | -No | -
| Pro | -Yes | -Yes | -
| Business | -Yes | -Yes | -
| Enterprise | -Yes | -Yes | -
| Education | -Yes | -Yes | -
| Mobile | -Yes | -Yes | -
| Mobile Enterprise | -Yes | -Yes | -
| Edition | -Windows 10 | -Windows 11 | -
|---|---|---|
| Home | -No | No | -
| Pro | -Yes | -Yes | -
| Enterprise | -Yes | -Yes | -
| Education | -Yes | -Yes | -
| Edition | -Windows 10 | -Windows 11 | -
|---|---|---|
| Home | -No | -No | -
| Pro | -Yes | -Yes | -
| Enterprise | -Yes | -Yes | -
| Education | -Yes | -Yes | -
| Edition | -Windows 10 | -Windows 11 | -
|---|---|---|
| Home | -No | -No | -
| Edition | -Windows 10 | -Windows 11 | -
|---|---|---|
| Home | -No | -No | -
| Pro | -No | -No | -
| Business | -||
| Enterprise | -Yes | -Yes | -
| Education | -
| Edition | -Windows 10 | -Windows 11 | -
|---|---|---|
| Home | -No | -No | -
| Pro | -No | -No | -
| Business | -No | -No | -
| Enterprise | -Yes | -Yes | -
| Education | -Yes | -Yes | -
| Edition | -Windows 10 | -Windows 11 | -
|---|---|---|
| Home | -No | -No | -
| Pro | -No | -No | -
| Business | -No | -No | -
| Enterprise | -Yes | -Yes | -
| Education | -Yes | -Yes | -
| Edition | -Windows 10 | -Windows 11 | -
|---|---|---|
| Home | -No | -No | -
| Pro | -No | -No | -
| Business | -No | -No | -
| Enterprise | -Yes | -Yes | -
| Education | -Yes | -Yes | -
| Edition | -Windows 10 | -Windows 11 | -
|---|---|---|
| Home | -No | -No | -
| Pro | -No | -No | -
| Business | -No | -No | -
| Enterprise | -Yes | -Yes | -
| Education | -Yes | -Yes | -
| Edition | -Windows 10 | -Windows 11 | -
|---|---|---|
| Home | -No | -No | -
| Pro | -No | -No | -
| Business | -No | -No | -
| Enterprise | -Yes | -Yes | -
| Education | -Yes | -Yes | -
| Edition | -Windows 10 | -Windows 11 | -
|---|---|---|
| Home | -No | -No | -
| Pro | -No | -No | -
| Business | -No | -No | -
| Enterprise | -Yes | -Yes | -
| Education | -Yes | -Yes | -
| Edition | -Windows 10 | -Windows 11 | -
|---|---|---|
| Home | -No | -No | -
| Pro | -No | -No | -
| Business | -No | -No | -
| Enterprise | -Yes | -Yes | -
| Education | -Yes | -Yes | -
| Edition | -Windows 10 | -Windows 11 | -
|---|---|---|
| Home | -No | -No | -
| Pro | -No | -No | -
| Business | -No | -No | -
| Enterprise | -Yes | -Yes | -
| Education | -Yes | -Yes | -
| Edition | -Windows 10 | -Windows 11 | -
|---|---|---|
| Home | -No | -No | -
| Pro | -No | -No | -
| Business | -No | -No | -
| Enterprise | -Yes | -Yes | -
| Education | -Yes | -Yes | -