Merge branch 'master' into fix--MD037/no-space-in-emphasis

CONTRIBUTING.md

@@ -18,7 +18,7 @@ We've tried to make editing an existing, public file as simple as possible.
 
 **To edit a topic**
 
-1.	Go to the page on docs.microsoft.com that you want to update, and then click **Edit**.
+1. Go to the page on docs.microsoft.com that you want to update, and then click **Edit**.
 
     ![GitHub Web, showing the Edit link](images/contribute-link.png)
 
@@ -30,12 +30,12 @@ We've tried to make editing an existing, public file as simple as possible.
 
     ![GitHub Web, showing the Pencil icon in the red box](images/pencil-icon.png)
 
-4.	Using Markdown language, make your changes to the topic. For info about how to edit content using Markdown, see:
+4. Using Markdown language, make your changes to the topic. For info about how to edit content using Markdown, see:
     - **If you're linked to the Microsoft organization in GitHub:** [Windows authoring guide](https://aka.ms/WindowsAuthoring)
     
     - **If you're external to Microsoft:** [Mastering Markdown](https://guides.github.com/features/mastering-markdown/) 
 
-5.	Make your suggested change, and then click **Preview Changes** to make sure it looks correct.
+5. Make your suggested change, and then click **Preview Changes** to make sure it looks correct.
 
     ![GitHub Web, showing the Preview Changes tab](images/preview-changes.png)
 
@@ -45,19 +45,19 @@ We've tried to make editing an existing, public file as simple as possible.
 
     The **Comparing changes** screen appears to see what the changes are between your fork and the original content.
 
-7.	On the **Comparing changes** screen, you’ll see if there are any problems with the file you’re checking in.
+7. On the **Comparing changes** screen, you’ll see if there are any problems with the file you’re checking in.
 
     If there are no problems, you’ll see the message, **Able to merge**.
     
     ![GitHub Web, showing the Comparing changes screen](images/compare-changes.png)
 
-8.	Click **Create pull request**.
+8. Click **Create pull request**.
 
-9.	Enter a title and description to give the approver the appropriate context about what’s in the request.
+9. Enter a title and description to give the approver the appropriate context about what’s in the request.
 
-10.	Scroll to the bottom of the page, making sure that only your changed files are in this pull request. Otherwise, you could overwrite changes from other people.
+10. Scroll to the bottom of the page, making sure that only your changed files are in this pull request. Otherwise, you could overwrite changes from other people.
 
-11.	Click **Create pull request** again to actually submit the pull request.
+11. Click **Create pull request** again to actually submit the pull request.
 
     The pull request is sent to the writer of the topic and your edits are reviewed. If your request is accepted, updates are published to one of the following places:
 

browsers/edge/includes/configure-kiosk-mode-supported-values-include.md

@@ -11,7 +11,7 @@ ms.topic: include
 
 | | |
 |----------|------|
-|**Single-app**<p><a href="/images/Picture1.png" alt="Full-sized view single-app digital/interactive signage" target="_blank">![thumbnail](../images/Picture1-sm.png)</a><p>**Digital/interactive signage**<p>Displays a specific site in full-screen mode, running Microsoft Edge InPrivate protecting user data.<ul><li>**Digital signage** does not require user interaction.<p>***Example.*** Use digital signage for things like a rotating advertisement or menu.<p></li><li>**Interactive signage**, on the other hand, requires user interaction within the page but doesn’t allow for any other uses, such as browsing the internet.<p>***Example.*** Use interactive signage for things like a building business directory or restaurant order/pay station.</li></ul><p>**Policy setting** = Not configured (0 default)<p>                                      |                                                                                                                    <p>&nbsp;<p><a href="/images/Picture2.png" alt="Full-sized view single-app public browsing" target="_blank">![thumbnail](../images/Picture2-sm.png)</a> <p><strong>Public browsing</strong><p>Runs a limited multi-tab version of Microsoft Edge, protecting user data. Microsoft Edge is the only app users can use on the device, preventing them from customizing Microsoft Edge.  Users can only browse publically or end their browsing session.<p>The single-app public browsing mode is the only kiosk mode that has an <strong>End session</strong> button. Microsoft Edge also resets the session after a specified time of user inactivity. Both restart Microsoft Edge and clear the user’s session.<p><em><strong>Example.</strong></em> A public library or hotel concierge desk are two examples of public browsing that provides access to Microsoft Edge and other apps. <p><strong>Policy setting</strong> = Enabled (1)                                                                                                                     |
+|**Single-app**<p><a href="../images/Picture1.png" alt="Full-sized view single-app digital/interactive signage" target="_blank">![thumbnail](../images/Picture1-sm.png)</a><p>**Digital/interactive signage**<p>Displays a specific site in full-screen mode, running Microsoft Edge InPrivate protecting user data.<ul><li>**Digital signage** does not require user interaction.<p>***Example.*** Use digital signage for things like a rotating advertisement or menu.<p></li><li>**Interactive signage**, on the other hand, requires user interaction within the page but doesn’t allow for any other uses, such as browsing the internet.<p>***Example.*** Use interactive signage for things like a building business directory or restaurant order/pay station.</li></ul><p>**Policy setting** = Not configured (0 default)<p>                                      |                                                                                                                    <p>&nbsp;<p><a href="../images/Picture2.png" alt="Full-sized view single-app public browsing" target="_blank">![thumbnail](../images/Picture2-sm.png)</a> <p><strong>Public browsing</strong><p>Runs a limited multi-tab version of Microsoft Edge, protecting user data. Microsoft Edge is the only app users can use on the device, preventing them from customizing Microsoft Edge.  Users can only browse publically or end their browsing session.<p>The single-app public browsing mode is the only kiosk mode that has an <strong>End session</strong> button. Microsoft Edge also resets the session after a specified time of user inactivity. Both restart Microsoft Edge and clear the user’s session.<p><em><strong>Example.</strong></em> A public library or hotel concierge desk are two examples of public browsing that provides access to Microsoft Edge and other apps. <p><strong>Policy setting</strong> = Enabled (1)                                                                                                                     |
-| **Multi-app**<p><a href="/images/Picture5.png" alt="Full-sized view multi-app normal browsing" target="_blank">![thumbnail](../images/Picture5-sm.png)</a><p>**Normal browsing**<p>Runs a full-version of Microsoft Edge with all browsing features and preserves the user data and state between sessions.<p>Some features may not work depending on what other apps you have configured in assigned access. For example, installing extensions or books from the Microsoft store are not allowed if the store is not available. Also, if Internet Explorer 11 is set up in assigned access, you can enable [EnterpriseModeSiteList](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-browser#browser-enterprisemodesitelist) to automatically switch users to Internet Explorer 11 for sites that need backward compatibility support.<p>**Policy setting** = Not configured (0 default) | <p>&nbsp;<p><a href="/images/Picture6.png" alt="Full-sized view multi-app public browsing" target="_blank">![thumbnail](../images/Picture6-sm.png)</a><p><strong>Public browsing</strong><p>Runs a multi-tab version of Microsoft Edge InPrivate with a tailored experience for kiosks that runs in full-screen mode. Users can open and close Microsoft Edge and launch other apps if allowed by assigned access. Instead of an End session button to clear their browsing session, the user closes Microsoft Edge normally.<p>In this configuration, Microsoft Edge can interact with other applications. For example, if Internet Explorer 11 is set up in multi-app assigned access, you can enable [EnterpriseModeSiteList](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-browser#browser-enterprisemodesitelist) to automatically switch users to Internet Explorer 11 for sites that need backward compatibility support. <p><em><strong>Example.</strong></em> A public library or hotel concierge desk are two examples of public browsing that provides access to Microsoft Edge and other apps.<p><strong>Policy setting</strong> = Enabled (1) |
+| **Multi-app**<p><a href="../images/Picture5.png" alt="Full-sized view multi-app normal browsing" target="_blank">![thumbnail](../images/Picture5-sm.png)</a><p>**Normal browsing**<p>Runs a full-version of Microsoft Edge with all browsing features and preserves the user data and state between sessions.<p>Some features may not work depending on what other apps you have configured in assigned access. For example, installing extensions or books from the Microsoft store are not allowed if the store is not available. Also, if Internet Explorer 11 is set up in assigned access, you can enable [EnterpriseModeSiteList](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-browser#browser-enterprisemodesitelist) to automatically switch users to Internet Explorer 11 for sites that need backward compatibility support.<p>**Policy setting** = Not configured (0 default) | <p>&nbsp;<p><a href="../images/Picture6.png" alt="Full-sized view multi-app public browsing" target="_blank">![thumbnail](../images/Picture6-sm.png)</a><p><strong>Public browsing</strong><p>Runs a multi-tab version of Microsoft Edge InPrivate with a tailored experience for kiosks that runs in full-screen mode. Users can open and close Microsoft Edge and launch other apps if allowed by assigned access. Instead of an End session button to clear their browsing session, the user closes Microsoft Edge normally.<p>In this configuration, Microsoft Edge can interact with other applications. For example, if Internet Explorer 11 is set up in multi-app assigned access, you can enable [EnterpriseModeSiteList](https://docs.microsoft.com/windows/client-management/mdm/policy-csp-browser#browser-enterprisemodesitelist) to automatically switch users to Internet Explorer 11 for sites that need backward compatibility support. <p><em><strong>Example.</strong></em> A public library or hotel concierge desk are two examples of public browsing that provides access to Microsoft Edge and other apps.<p><strong>Policy setting</strong> = Enabled (1) |
 
 ---

browsers/enterprise-mode/collect-data-using-enterprise-site-discovery.md

@@ -154,11 +154,11 @@ If you choose to use WMI as your data output, you need to make sure that your WM
 
 **To set up your firewall**
 
-1.	In **Control Panel**, click **System and Security**, and then click **Windows Firewall**.
+1. In **Control Panel**, click **System and Security**, and then click **Windows Firewall**.
 
-2.	In the left pane, click **Allow an app or feature through Windows Firewall** and scroll down to check the box for **Windows Management Instrumentation (WMI)**.
+2. In the left pane, click **Allow an app or feature through Windows Firewall** and scroll down to check the box for **Windows Management Instrumentation (WMI)**.
 
-3.	Restart your computer to start collecting your WMI data.
+3. Restart your computer to start collecting your WMI data.
 
 ## Use PowerShell to finish setting up Enterprise Site Discovery
 You can determine which zones or domains are used for data collection, using PowerShell. If you don’t want to use PowerShell, you can do this using Group Policy. For more info, see [Use Group Policy to finish setting up Enterprise Site Discovery](#use-group-policy-to-finish-setting-up-enterprise-site-discovery).

browsers/internet-explorer/ie11-deploy-guide/collect-data-using-enterprise-site-discovery.md

@@ -154,11 +154,11 @@ If you choose to use WMI as your data output, you need to make sure that your WM
 
 **To set up your firewall**
 
-1.	In **Control Panel**, click **System and Security**, and then click **Windows Firewall**.
+1. In **Control Panel**, click **System and Security**, and then click **Windows Firewall**.
 
-2.	In the left pane, click **Allow an app or feature through Windows Firewall** and scroll down to check the box for **Windows Management Instrumentation (WMI)**.
+2. In the left pane, click **Allow an app or feature through Windows Firewall** and scroll down to check the box for **Windows Management Instrumentation (WMI)**.
 
-3.	Restart your computer to start collecting your WMI data.
+3. Restart your computer to start collecting your WMI data.
 
 ## Use PowerShell to finish setting up Enterprise Site Discovery
 You can determine which zones or domains are used for data collection, using PowerShell. If you don’t want to use PowerShell, you can do this using Group Policy. For more info, see [Use Group Policy to finish setting up Enterprise Site Discovery](#use-group-policy-to-finish-setting-up-enterprise-site-discovery).

browsers/internet-explorer/ie11-deploy-guide/intranet-problems-and-ie11.md

@@ -24,7 +24,7 @@ IE11 works differently with search, based on whether your organization is domain
 
 -   **Non-domain-joined computers.** A single word entry is treated as an intranet site. However, if the term doesn't resolve to a site, IE11 then treats the entry as a search term and opens your default search provider.
 
-To explicitly go to an intranet site, regardless of the environment, users can type either a trailing slash like ` contoso/` or the `https://` prefix. Either of these will cause IE11 to treat the entry as an intranet search. You can also change the default behavior so that IE11 treats your single word entry in the address bar as an intranet site, regardless of your environment.
+To explicitly go to an intranet site, regardless of the environment, users can type either a trailing slash like `contoso/` or the `https://` prefix. Either of these will cause IE11 to treat the entry as an intranet search. You can also change the default behavior so that IE11 treats your single word entry in the address bar as an intranet site, regardless of your environment.
 
  **To enable single-word intranet search**
 

browsers/internet-explorer/ie11-ieak/troubleshooting-custom-browser-pkg-ieak11.md

@@ -75,8 +75,8 @@ If you cannot uninstall IE using **Uninstall or change a program** in the Contro
 ## The Internet Explorer Customization Wizard 11 does not work with user names that user double-byte character sets
 The customization wizard does not work with user names that use double-byte character sets, such as Chinese or Japanese. To fix this, set the **TEMP** and **TMP** environmental variables to a path that does not use these characters (for example, C:\temp).
 
-1.	Open **System Properties**, click the **Advanced** tab, and then click **Environmental Variables**.
+1. Open **System Properties**, click the **Advanced** tab, and then click **Environmental Variables**.
-2.	Click Edit, and then modify the **TEMP** and **TMP** environmental variables to a non-user profile directory.
+2. Click Edit, and then modify the **TEMP** and **TMP** environmental variables to a non-user profile directory.
 
  
 ## Unicode characters are not supported in IEAK 11 path names

devices/hololens/hololens-cortana.md

@@ -31,13 +31,13 @@ Here are some things you can try saying (remember to say "Hey Cortana" first):
 - Restart.
 - Go to sleep.
 - Mute.
-- Launch <app name>.
+- Launch `<app name>`.
-- Move <app name> here (gaze at the spot you want the app to move to).
+- Move `<app name>` here (gaze at the spot you want the app to move to).
 - Go to Start.
 - Take a picture.
 - Start recording. (Starts recording a video.)
 - Stop recording. (Stops recording a video.)
-- Call <contact>. (Requires Skype.)
+- Call `<contact>`. (Requires Skype.)
 - What time is it?
 - Show me the latest NBA scores. 
 - How much battery do I have left?

devices/hololens/hololens-encryption.md

@@ -45,7 +45,7 @@ Provisioning packages are files created by the Windows Configuration Designer to
 
     ![Require device encryption setting configured to yes](images/device-encryption.png)
 
-2.	Browse to and select the XML license file that was provided when you purchased the Commercial Suite.
+2. Browse to and select the XML license file that was provided when you purchased the Commercial Suite.
 
     >[!NOTE]
     >You can configure [additional settings in the provisioning package](hololens-provisioning.md).

devices/hololens/hololens-setup.md

@@ -1,46 +1,75 @@
 ---
-title: Set up HoloLens (HoloLens)
+title: Set up a new HoloLens
-description: The first time you set up HoloLens, you'll need a Wi-Fi network and either a Microsoft or Azure Active Directory account.
+description: This guide walks through first time set up.  You'll need a Wi-Fi network and either a Microsoft (MSA) or Azure Active Directory (AAD) account.
 ms.prod: hololens
 ms.sitesec: library
-author: dansimp
+author: scooley
-ms.author: dansimp
+ms.author: scooley
-ms.topic: article
+ms.topic: quickstart
 ms.localizationpriority: medium
-ms.date: 07/27/2017
+ms.date: 07/14/2019
-ms.reviewer: 
-manager: dansimp
 ---
 
-# Set up HoloLens
+# Set up HoloLens for the first time
 
-Before you get started setting up your HoloLens, make sure you have a Wi-Fi network and a Microsoft account or an Azure Active Directory (Azure AD) account. 
+Follow along to set up a HoloLens for the first time.  At the end of this quickstart, you'll be able to use HoloLens and navigate HoloLens settings on-device.
 
-## Network connectivity requirements
+This is a high level unboxing guide to become familiar with HoloLens.  
+See [Set up HoloLens in the enterprise](hololens-requirements.md) to configure HoloLens for scale enterprise deployment and ongoing device management.
 
-The first time you use your HoloLens, you'll be guided through connecting to a Wi-Fi network. You need to connect HoloLens to a Wi-Fi network with Internet connectivity so that the user account can be authenticated.
+## Prerequisites
 
-- It can be an open Wi-Fi or password-protected Wi-Fi network.
+- Internet access.
-- The Wi-Fi network cannot require certificates to connect.
+  - Wi-Fi is the easiest way to do first set up on both HoloLens and HoloLens 2.  It can be an open Wi-Fi or password-protected Wi-Fi network; the Wi-Fi network does not need to provide access to enterprise resources or intranet sites.
-- The Wi-Fi network does not need to provide access to enterprise resources or intranet sites. 
+  - HoloLens 2 can connect to the internet via ethernet and a USB-C adapter.
+- a user account - Microsoft (MSA) or Azure Active Directory (AAD)
 
-## HoloLens setup
+## Prepare for first-boot
 
-The HoloLens setup process combines a quick tutorial on using HoloLens with the steps needed to connect to the network and add an account.
+Become familiar with the HoloLens hardware and prepare to turn your HoloLens on for the first time.
 
-1. Be sure your HoloLens is [charged](https://support.microsoft.com/help/12627), then [adjust it](https://support.microsoft.com/help/12632) for a comfortable fit.
+1. Be sure your HoloLens is [charged](https://support.microsoft.com/help/12627)
-2. [Turn on HoloLens](https://support.microsoft.com/help/12642). You will be guided through a calibration procedure and how to perform [the gestures](https://support.microsoft.com/help/12644/hololens-use-gestures) that you will use to operate HoloLens.
+1. [Adjust fit](https://support.microsoft.com/help/12632) for a comfortable fit.
-3. Next, you'll be guided through connecting to a Wi-Fi network. 
+1. [Turn on HoloLens](https://support.microsoft.com/help/12642). You will be guided through a calibration procedure and how to perform [the gestures](https://support.microsoft.com/help/12644/hololens-use-gestures) that you will use to operate HoloLens.
-4. After HoloLens connects to the Wi-Fi network, you select between **My work or school owns it** and **I own it**. 
+
+## Set up your HoloLens
+
+Set up your HoloLens and your user account.
+
+1. Connect to the internet (select Wi-Fi).
+1. Sign in to your user account.  You'll choose between **My work or school owns it** and **I own it**.
     - When you choose **My work or school owns it**, you sign in with an Azure AD account. If your organization uses Azure AD Premium and has configured automatic MDM enrollment, HoloLens will be enrolled in MDM. If your organization does not use Azure AD Premium, automatic MDM enrollment isn't available, so you will need to [enroll HoloLens in device management manually](hololens-enroll-mdm.md#enroll-through-settings-app).
-        1. Enter your organizational account. 
+        1. Enter your organizational account.
         2. Accept privacy statement.
         3. Sign in using your Azure AD credentials. This may redirect to your organization's sign-in page.
         4. Continue with device setup.
     - When you choose **I own it**, you sign in with a Microsoft account. After setup is complete, you can [enroll HoloLens in device management manually](hololens-enroll-mdm.md#enroll-through-settings-app).
-        1. Enter your Microsoft account. 
+        1. Enter your Microsoft account.
-        2. Enter your password. If your Microsoft account requires [two-step verification (2FA)](https://blogs.technet.microsoft.com/microsoft_blog/2013/04/17/microsoft-account-gets-more-secure/), complete the verification process. 
+        2. Enter your password. If your Microsoft account requires [two-step verification (2FA)](https://blogs.technet.microsoft.com/microsoft_blog/2013/04/17/microsoft-account-gets-more-secure/), complete the verification process.
-5. The device sets your time zone based on information obtained from the Wi-Fi network. 
+1. The device sets your time zone based on information obtained from the Wi-Fi network.
-6. Next, you learn how to perform the bloom gesture and how to select and place the Start screen. After you place the Start screen, setup is complete and you can begin using HoloLens.
+1. Follow the first-start guides to learn how to interact with holograms, control the HoloLens with your voice, and access the start menu.
 
+Congratulations!  Setup is complete and you can begin using HoloLens.
 
+## Explore HoloLens
+
+### Check out on-device settings and desktop
+
+HoloLens doesn't have an on-device command line.  With that in mind, the settings section in HoloLens plays an important role in diagnosing problems on-device.  Understanding the information available to HoloLens users will pay dividends when troubleshooting or configuring the device.
+
+Open settings by opening the start menu and clicking on the **Settings** in the top bar.  You can also ask Cortana to open settings.
+
+Follow [this guide](https://docs.microsoft.com/windows/mixed-reality/navigating-the-windows-mixed-reality-home) to navigate around the HoloLens home.
+
+### Connect bluetooth devices
+
+Connecting a bluetooth keyboard makes typing on HoloLens as efficient as a Windows PC.
+
+[Connect a bluetooth keyboard or clicker](https://support.microsoft.com/en-us/help/12636).
+
+## Next steps
+
+Start planning for HoloLens at scale with HoloLens' enterprise management features.
+
+> [!div class="nextstepaction"]
+> [HoloLens in the enterprise](hololens-requirements.md)

devices/hololens/hololens-upgrade-enterprise.md

@@ -47,7 +47,7 @@ Provisioning packages are files created by the Windows Configuration Designer to
 
     ![Upgrade edition with license setting selected](images/icd1.png)
 
-2.	Browse to and select the XML license file that was provided when you purchased the Commercial Suite.
+2. Browse to and select the XML license file that was provided when you purchased the Commercial Suite.
 
     >[!NOTE]
     >You can configure [additional settings in the provisioning package](hololens-provisioning.md).

devices/hololens/index.md

@@ -1,46 +1,51 @@
 ---
 title: Microsoft HoloLens (HoloLens)
-description: HoloLens provides extra features designed for business in the Commercial Suite.
+description: Landing page for HoloLens commercial and enterprise management.
 ms.prod: hololens
 ms.sitesec: library
-author: jdeckerms
+author: scooley
-ms.author: jdecker
+ms.author: scooley
 ms.topic: article
 ms.localizationpriority: medium
-ms.date: 07/27/2018
+ms.date: 07/14/2019
 ---
 
 # Microsoft HoloLens
 
-
 <table><tbody>
-<tr><td style="border: 0px;width: 75%;valign= top"><p>Microsoft HoloLens is the first fully self-contained holographic computer running Windows 10.</p><p> Microsoft HoloLens is available in the <strong>Development Edition</strong>, which runs Windows Holographic (an edition of Windows 10 designed for HoloLens), and in the <strong>Commercial Suite</strong>, which runs Windows Holographic for Business when you apply the Enterprise license file to the device.</p></td><td align="left" style="border: 0px"><img src="images/hololens.png" alt="Hololens"/></td></tr>
+<tr><td style="border: 0px;width: 75%;valign= top">
+<p>Microsoft HoloLens is the first fully self-contained holographic computer running Windows 10.</p>
+
+<p>Now, with the introduction of HoloLens 2, every device provides commercial ready management enhanced by the reliability, security, and scalability of cloud and AI services from Microsoft.</p>
+
+</td><td align="left" style="border: 0px">![Hololens](images/hololens2-side-render.png)</td></tr>
 </tbody></table>
 
-## In this section
+## Guides in this section
+
+| Guide | Description |
+| --- | --- |
+| [Get started with HoloLens](hololens-setup.md) | Set up HoloLens for the first time.  |
+| [Set up HoloLens in the enterprise](hololens-requirements.md) | Configure HoloLens for scale enterprise deployment and ongoing device management.  |
+| [Install and manage applications on HoloLens](hololens-install-apps.md) |Install and manage important applications on HoloLens at scale.  |
+| [Recover and troubleshoot HoloLens issues](https://support.microsoft.com/products/hololens) |  Learn how to gather logs from HoloLens, recover a misbehaving device, or reset HoloLens when necessary.  |
+| [Get support](https://support.microsoft.com/products/hololens) |Connect with Microsoft support resources for HoloLens in enterprise.  |
+
+## Quick reference by topic
 
 | Topic | Description |
 | --- | --- |
-| [What's new in Microsoft HoloLens](hololens-whats-new.md) | Discover the new features in the latest update. |
+| [What's new in Microsoft HoloLens](hololens-whats-new.md) | Discover new features in the latest updates. |
-| [HoloLens in the enterprise: requirements](hololens-requirements.md) | Lists requirements for general use, Wi-Fi, and device management |
-| [Set up HoloLens](hololens-setup.md) | How to set up HoloLens for the first time  |
-[Install localized version of HoloLens](hololens-install-localized.md) | Install the Chinese or Japanese version of HoloLens
-| [Unlock Windows Holographic for Business features](hololens-upgrade-enterprise.md)  | How to upgrade your Development Edition HoloLens to Windows Holographic for Business |
-| [Enroll HoloLens in MDM](hololens-enroll-mdm.md) | Manage multiple HoloLens devices simultaneously using solutions like Microsoft Intune |
-| [Manage updates to HoloLens](hololens-updates.md) | Use mobile device management (MDM) policies to configure settings for updates. |
-| [Set up HoloLens in kiosk mode](hololens-kiosk.md) | Enable kiosk mode for HoloLens, which limits the user's ability to launch new apps or change the running app  |
-[Share HoloLens with multiple people](hololens-multiple-users.md) | Multiple users can shared a HoloLens device by using their Azure Active Directory accounts. |
 | [Configure HoloLens using a provisioning package](hololens-provisioning.md) | Provisioning packages make it easy for IT administrators to configure HoloLens devices without imaging |
-| [Install apps on HoloLens](hololens-install-apps.md) | Use Microsoft Store for Business, mobile device management (MDM), or the Windows Device Portal to install apps on HoloLens |
+| [HoloLens MDM support](hololens-enroll-mdm.md) | Manage multiple HoloLens devices simultaneously using Mobile Device Management (MDM) solutions like Microsoft Intune. |
-| [Enable Bitlocker device encryption for HoloLens](hololens-encryption.md) | Learn how to use Bitlocker device encryption to protect files and information stored on the HoloLens |
+| [HoloLens update management](hololens-updates.md) | Use mobile device management (MDM) policies to configure settings for updates. |
-| [Change history for Microsoft HoloLens documentation](change-history-hololens.md) | See new and updated topics in the HoloLens documentation library. |
+| [HoloLens user management](hololens-multiple-users.md) | Multiple users can shared a HoloLens device by using their Azure Active Directory accounts. |
+| [HoloLens application access management](hololens-kiosk.md) | Manage application access for different user groups.  |
+| [Enable Bitlocker device encryption for HoloLens](hololens-encryption.md) | Learn how to use Bitlocker device encryption to protect files and information stored on the HoloLens. |
+| [Install localized version of HoloLens](hololens-install-localized.md) | Configure HoloLens for different locale.  |
 
 ## Related resources
 
-- [Help for using HoloLens](https://support.microsoft.com/products/hololens)
+* [Documentation for Holographic app development](https://developer.microsoft.com/windows/mixed-reality/development)
-
+* [HoloLens Commercial Suite](https://www.microsoft.com/microsoft-hololens/hololens-commercial)
-- [Documentation for Holographic app development](https://developer.microsoft.com/windows/mixed-reality/development)
+* [HoloLens release notes](https://developer.microsoft.com/en-us/windows/mixed-reality/release_notes)
-
-- [HoloLens Commercial Suite](https://www.microsoft.com/microsoft-hololens/hololens-commercial)
-
-- [HoloLens release notes](https://developer.microsoft.com/en-us/windows/mixed-reality/release_notes)

devices/surface-hub/TOC.md

@@ -5,7 +5,7 @@
 ## Overview
 ### [What's new in Surface Hub 2S for IT admins](surface-hub-2s-whats-new.md)
 ### [Surface Hub 2S tech specs](surface-hub-2s-techspecs.md) 
-### [Operating system essentials (Surface Hub) ](differences-between-surface-hub-and-windows-10-enterprise.md)
+### [Operating system essentials (Surface Hub)](differences-between-surface-hub-and-windows-10-enterprise.md)
 ### [Adjust Surface Hub 2S brightness, volume, and input](surface-hub-2s-onscreen-display.md)
 
 ## Plan

devices/surface-hub/appendix-a-powershell-scripts-for-surface-hub.md

@@ -534,7 +534,7 @@ if ($status.Count -gt 0)
         elseif ($v[0] -eq "F")
         {
             $color = "red"
-            $v += " Go to http://aka.ms/shubtshoot"
+            $v += " Go to https://aka.ms/shubtshoot"
         }
 
         Write-Host -NoNewline $k -ForegroundColor $color
@@ -978,7 +978,7 @@ if ($status.Count -gt 0)
         elseif ($v[0] -eq "F")
         {
             $color = "red"
-            $v += " Go to http://aka.ms/shubtshoot for help"
+            $v += " Go to https://aka.ms/shubtshoot for help"
         }
 
         Write-Host -NoNewline $k -ForegroundColor $color

devices/surface-hub/device-reset-surface-hub.md

@@ -44,15 +44,15 @@ If you see a blank screen for long periods of time during the **Reset device** p
 ## Reset a Surface Hub from Settings
 
 **To reset a Surface Hub**
-1.	On your Surface Hub, open **Settings**.
+1. On your Surface Hub, open **Settings**.
 
     ![Image showing Settings app for Surface Hub.](images/sh-settings.png)
 
-2.	Click **Update & Security**.
+2. Click **Update & Security**.
 
     ![Image showing Update & Security group in Settings app for Surface Hub.](images/sh-settings-update-security.png)
 
-3.	Click **Recovery**, and then, under **Reset device**, click **Get started**.
+3. Click **Recovery**, and then, under **Reset device**, click **Get started**.
 
     ![Image showing Reset device option in Settings app for Surface Hub.](images/sh-settings-reset-device.png)
 

devices/surface-hub/differences-between-surface-hub-and-windows-10-enterprise.md

@@ -127,7 +127,7 @@ The administrative features in Windows 10 Enterprise, such as the Microsoft Mana
 
 ### Remote management and monitoring
 
-Surface Hub supports remote management through mobile device management (MDM) solutions such as [Microsoft Intune](https://docs.microsoft.com/en-us/intune/) and monitoring through [Azure Monitor](https://azure.microsoft.com/services/monitor/). 
+Surface Hub supports remote management through mobile device management (MDM) solutions such as [Microsoft Intune](https://docs.microsoft.com/intune/) and monitoring through [Azure Monitor](https://azure.microsoft.com/services/monitor/). 
 
 *Organization policies that this may affect:* <br> Surface Hub doesn't support installing Win32 agents required by most traditional PC management and monitoring tools, such as System Center Operations Manager.
 

devices/surface-hub/docfx.json

@@ -14,7 +14,9 @@
     "resource": [
       {
         "files": [
-          "**/images/**"
+          "**/images/**",
+          "**/*.pptx",
+          "**/*.pdf"
         ],
         "exclude": [
           "**/obj/**"

devices/surface-hub/install-apps-on-surface-hub.md

@@ -21,7 +21,7 @@ You can install additional apps on your Surface Hub to fit your team or organiza
 A few things to know about apps on Surface Hub:
 - Surface Hub only runs [Universal Windows Platform (UWP) apps](https://msdn.microsoft.com/windows/uwp/get-started/whats-a-uwp). Apps created using the [Desktop App Converter](https://docs.microsoft.com/windows/uwp/porting/desktop-to-uwp-run-desktop-app-converter) will not run on Surface Hub.
 - Apps must be targeted for the [Universal device family](https://msdn.microsoft.com/library/windows/apps/dn894631) or Windows Team device family.
-- Surface Hub only supports [offline-licensed apps](https://docs.microsoft.com/microsoft-store/distribute-offline-apps) from Microsoft Store for Business.
+- Surface Hub only supports [offline-licensed apps](https://docs.microsoft.com/microsoft-store/distribute-offline-apps) from [Microsoft Store for Business](https://businessstore.microsoft.com/store).
 - By default, apps must be Store-signed to be installed. During testing and development, you can also choose to run developer-signed UWP apps by placing the device in developer mode.
 - When submitting an app to the Microsoft Store, developers need to set Device family availability and Organizational licensing options to make sure an app will be available to run on Surface Hub.
 - You need admin credentials to install apps on your Surface Hub. Since the device is designed to be used in communal spaces like meeting rooms, people can't access the Microsoft Store to download and install apps.
@@ -39,10 +39,10 @@ By enabling developer mode, you can also install developer-signed UWP apps.
 > After developer mode has been enabled, you will need to reset the Surface Hub to disable it. Resetting the device removes all local user files and configurations and then reinstalls Windows.
 
 **To turn on developer mode** 
-1.	From your Surface Hub, start **Settings**.
+1. From your Surface Hub, start **Settings**.
-2.	Type the device admin credentials when prompted.
+2. Type the device admin credentials when prompted.
-3.	Navigate to **Update & security** > **For developers**.
+3. Navigate to **Update & security** > **For developers**.
-4.	Select **Developer mode** and accept the warning prompt.
+4. Select **Developer mode** and accept the warning prompt.
 
 ### Visual Studio
 During development, the easiest way to test your app on a Surface Hub is using Visual Studio. Visual Studio's remote debugging feature helps you discover issues in your app before deploying it broadly. For more information, see [Test Surface Hub apps using Visual Studio](https://msdn.microsoft.com/windows/uwp/debug-test-perf/test-surface-hub-apps-using-visual-studio).
@@ -101,10 +101,10 @@ To evaluate apps released on the Microsoft Store, use the Microsoft Store app on
 > - To install apps, you will need to manually sign in to the Microsoft Store app on each Surface Hub you own.
 
 **To browse the Microsoft Store on Surface Hub** 
-1.	From your Surface Hub, start **Settings**.
+1. From your Surface Hub, start **Settings**.
-2.	Type the device admin credentials when prompted.
+2. Type the device admin credentials when prompted.
-3.	Navigate to **This device** > **Apps & features**.
+3. Navigate to **This device** > **Apps & features**.
-4.	Select **Open Store**.
+4. Select **Open Store**.
 
 ### Download app packages from Microsoft Store for Business
 To download the app package you need to install apps on your Surface Hub, visit the [Microsoft Store for Business](https://www.microsoft.com/business-store). The Store for Business is where you can find, acquire, and manage apps for the Windows 10 devices in your organization, including Surface Hub.

devices/surface-hub/monitor-surface-hub.md

@@ -95,10 +95,10 @@ This table describes the sample queries in the Surface Hub solution:
 | Hardware   | Error | **Contact Microsoft support**. <br> Indicates impact to core functionality (such as Skype, projection, touch, and internet connectivity). <br> **Note** Some events, including heartbeat, include the device’s serial number that you can use when contacting support.| Triggers when there is an error with any of the following hardware components. <br> **Components that affect Skype**: <br> - Speaker driver <br> - Microphone driver <br> - Camera driver <br> **Components that affect wired and wireless projection**: <br> - Wired touchback driver <br> - Wired ingest driver <br> - Wireless adapter driver <br> - Wi-Fi Direct error <br> **Other components**: <br> - Touch digitizer driver <br> - Network adapter error (not reported to OMS)|
 
 **To set up an alert**
-1.	From the Surface Hub solution, select one of the sample queries.
+1. From the Surface Hub solution, select one of the sample queries.
-2.	Modify the query as desired. See Log Analytics search reference to learn more.
+2. Modify the query as desired. See Log Analytics search reference to learn more.
-3.	Click **Alert** at the top of the page to open the **Add Alert Rule** screen. See [Alerts in Log Analytics](https://azure.microsoft.com/documentation/articles/log-analytics-alerts/) for details on the options to configure the alert.
+3. Click **Alert** at the top of the page to open the **Add Alert Rule** screen. See [Alerts in Log Analytics](https://azure.microsoft.com/documentation/articles/log-analytics-alerts/) for details on the options to configure the alert.
-4.	Click **Save** to complete the alert rule. It will start running immediately.
+4. Click **Save** to complete the alert rule. It will start running immediately.
 
 ## Enroll your Surface Hub
 

devices/surface-hub/skype-hybrid-voice.md

@@ -80,14 +80,14 @@ If you deployed Skype for Business Cloud PBX with one of the hybrid voice option
    Set-Mailbox surfacehub2@adatum.com -RoomMailboxPassword $credNewAccount.Password -EnableRoomMailboxAccount $true
    ```
     
-10.	Various Exchange properties must be set on the device account to improve the meeting experience. You can see which properties can be set in [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md). The following cmdlets provide an example of setting Exchange properties.
+10. Various Exchange properties must be set on the device account to improve the meeting experience. You can see which properties can be set in [Exchange properties](exchange-properties-for-surface-hub-device-accounts.md). The following cmdlets provide an example of setting Exchange properties.
 
     ```
     Set-CalendarProcessing surfacehub2@adatum.com -AutomateProcessing AutoAccept -AddOrganizerToSubject $false –AllowConflicts $false –DeleteComments $false -DeleteSubject $false -RemovePrivateProperty $false
     Set-CalendarProcessing surfacehub2@adatum.com -AddAdditionalResponse $true -AdditionalResponse "This is a Surface Hub room!"
     ```
 
-11.	Enable the mailbox as a meeting device in Skype for Business Online. Run the following cmdlet which enables the account as a meeting device. 
+11. Enable the mailbox as a meeting device in Skype for Business Online. Run the following cmdlet which enables the account as a meeting device. 
 
     ```
     Get-CsTenant | select registrarpool

devices/surface-hub/surface-hub-2s-deploy-apps-intune.md

@@ -20,7 +20,7 @@ You can install additional apps to fit your team or organization's needs.
 
 - Surface Hub only runs [Universal Windows Platform (UWP) apps](https://msdn.microsoft.com/windows/uwp/get-started/whats-a-uwp). Apps created using the [Desktop App Converter](https://docs.microsoft.com/windows/uwp/porting/desktop-to-uwp-run-desktop-app-converter) will not run on Surface Hub.
 - Apps must be targeted for the [Universal device family](https://msdn.microsoft.com/library/windows/apps/dn894631) or Windows Team device family.
-- Surface Hub only supports [offline-licensed apps](https://docs.microsoft.com/microsoft-store/distribute-offline-apps) from Microsoft Store for Business.
+- Surface Hub only supports [offline-licensed apps](https://docs.microsoft.com/microsoft-store/distribute-offline-apps) from [Microsoft Store for Business](https://businessstore.microsoft.com/store).
 - By default, apps must be Store-signed to be installed. During testing and development, you can also choose to run developer-signed UWP apps by placing the device in developer mode.
 - When developing and submitting apps to the Microsoft Store, set Device family availability and Organizational licensing options to ensure that apps are available to run on Surface Hub.
 - You need admin credentials to install apps on Surface Hub. Designed for use in meeting rooms and other shared spaces, Surface Hub prevents regular users from accessing the Microsoft Store to download and install apps.

devices/surface-hub/surface-hub-2s-phone-authenticate.md

@@ -39,4 +39,4 @@ Password-less phone sign-in simplifies signing-in to your meetings and files on
 3. If prompted, enter the PIN or biometric ID on your phone to complete sign-in.
 
 ## Learn more
-For more information, see [Password-less phone sign-in with the Microsoft Authenticator app](https://docs.microsoft.com/en-us/azure/active-directory/authentication/howto-authentication-phone-sign-in).
+For more information, see [Password-less phone sign-in with the Microsoft Authenticator app](https://docs.microsoft.com/azure/active-directory/authentication/howto-authentication-phone-sign-in).

devices/surface-hub/surface-hub-2s-prepare-environment.md

@@ -44,6 +44,6 @@ If you affiliate Surface Hub 2S with on-premises Active Directory Domain Service
 
 ## Azure Active Directory
 
-When choosing to affiliate your Surface Hub 2S with Azure AD, any user in the Global Admins Security Group can sign in to the Settings app on Surface Hub 2S. Alternatively, you can configure the Device Administrator role to sign in to the Settings app. For more information, see [Administrator role permissions in Azure Active Directory](https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/directory-assign-admin-roles#device-administrators). Currently, no other group can be delegated to sign in to the Settings app on Surface Hub 2S.
+When choosing to affiliate your Surface Hub 2S with Azure AD, any user in the Global Admins Security Group can sign in to the Settings app on Surface Hub 2S. Alternatively, you can configure the Device Administrator role to sign in to the Settings app. For more information, see [Administrator role permissions in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/users-groups-roles/directory-assign-admin-roles#device-administrators). Currently, no other group can be delegated to sign in to the Settings app on Surface Hub 2S.
 
 If you enabled Intune Automatic Enrollment for your organization, Surface Hub 2S will automatically enroll itself with Intune. The device’s Bitlocker key is automatically saved in Azure AD. When affiliating Surface Hub 2S with Azure AD, single sign-on and Easy Authentication will not work.

devices/surface-hub/surface-hub-2s-setup.md

@@ -43,7 +43,7 @@ When you first start Surface Hub 2S, the device automatically enters first time
  
 ## Configuring device admin accounts
 
-You can only set up device admins during first time Setup. For more information, refer to [Surface Hub 2S device affiliation](https://docs.microsoft.com/en-us/surface-hub/surface-hub-2s-prepare-environment#device-affiliation).
+You can only set up device admins during first time Setup. For more information, refer to [Surface Hub 2S device affiliation](https://docs.microsoft.com/surface-hub/surface-hub-2s-prepare-environment#device-affiliation).
 
  In the **Setup admins for this device** window, select one of the following options: Active Directory Domain Services, Azure Active Directory, or Local admin.
 
@@ -91,7 +91,7 @@ If you insert a USB thumb drive with a provisioning package into one of the USB
 
    ![* Choose provisioning package to use*](images/sh2-run13.png) <br>
 
-3. If you created a multiple devices CSV file, you will be able to choose a device configuration. For more information, refer to [Create provisioning packages for Surface Hub 2S](https://docs.microsoft.com/en-us/surface-hub/surface-hub-2s-deploy#provisioning-multiple-devices-csv-file).
+3. If you created a multiple devices CSV file, you will be able to choose a device configuration. For more information, refer to [Create provisioning packages for Surface Hub 2S](https://docs.microsoft.com/surface-hub/surface-hub-2s-deploy#provisioning-multiple-devices-csv-file).
 
 
     ![* Select a device account and friendly name from your configuration file*](images/sh2-run14.png) <br>

devices/surface-hub/whiteboard-collaboration.md

@@ -44,14 +44,14 @@ To get Whiteboard to Whiteboard collaboration up and running, you’ll need to m
 
 To start a collaboration session:
 
-1.	In the Whiteboard app, tap the **Sign in** button.
+1. In the Whiteboard app, tap the **Sign in** button.
-2.	Sign in with your organization ID.
+2. Sign in with your organization ID.
-3.	Tap the **Invite** button next to your name at the top of the app.
+3. Tap the **Invite** button next to your name at the top of the app.
-4.	Tap **Start session**. Whiteboard will generate a link that you can share.
+4. Tap **Start session**. Whiteboard will generate a link that you can share.
 
     ![screenshot of the link dialog box on whiteboard](images/wb-collab-link.png)
     
-5.	Copy and paste this link into a Skype chat with another Surface Hub
+5. Copy and paste this link into a Skype chat with another Surface Hub
 
 When the other Surface Hub receives the link, the recipient can tap on the link, sign in to Whiteboard, and then begin collaborating. You can copy and paste other content, use smart ink features like Ink to Shape, and co-author together.
 

devices/surface/deploy-surface-app-with-windows-store-for-business.md

@@ -54,7 +54,7 @@ Before users can install or deploy an app from a company’s Microsoft Store for
    ![Show offline licenses apps checkbox](images/deploysurfapp-figure1-enablingapps.png "Show offline licenses apps checkbox")<br/>
    *Figure 1. Enable apps for offline use*
 
-4.	Add Surface app to your Microsoft Store for Business account by following this procedure:
+4. Add Surface app to your Microsoft Store for Business account by following this procedure:
     * Click the **Shop** menu.
     * In the search box, type **Surface app**, and then click the search icon.
     * After the Surface app is presented in the search results, click the app’s icon.
@@ -99,21 +99,21 @@ Figure 5 shows the required frameworks for the Surface app.
 >The version numbers of the Surface app and required frameworks will change as the apps are updated. Check for the latest version of Surface app and each framework in Microsoft Store for Business. Always use the Surface app and recommended framework versions as provided by Microsoft Store for Business. Using outdated frameworks or the incorrect versions may result in errors or application crashes.
 
 To download the required frameworks for the Surface app, follow these steps:
-1.	Click the **Download** button under **Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe**. This downloads the Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe.Appx file to your specified folder.
+1. Click the **Download** button under **Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe**. This downloads the Microsoft.VCLibs.140.00_14.0.23816.0_x64__8wekyb3d8bbwe.Appx file to your specified folder.
-2.	Click the **Download** button under **Microsoft.NET.Native.Runtime.1.1_1.1.23406.0_x64__8wekyb3d8bbwe**. This downloads the Microsoft.NET.Native.Runtime.1.1_1.1.23406.0_x64__8wekyb3d8bbwe.Appx file to your specified folder.
+2. Click the **Download** button under **Microsoft.NET.Native.Runtime.1.1_1.1.23406.0_x64__8wekyb3d8bbwe**. This downloads the Microsoft.NET.Native.Runtime.1.1_1.1.23406.0_x64__8wekyb3d8bbwe.Appx file to your specified folder.
 
 >[!NOTE]
 >Only the 64-bit (x64) version of each framework is required for Surface devices. Surface devices are native 64-bit UEFI devices and are not compatible with 32-bit (x86) versions of Windows that would require 32-bit frameworks. 
 
 ## Install Surface app on your computer with PowerShell
 The following procedure provisions the Surface app onto your computer and makes it available for any user accounts created on the computer afterwards.
-1.	Using the procedure described in the [How to download Surface app from a Microsoft Store for Business account](#download-surface-app-from-a-microsoft-store-for-business-account) section of this article, download the Surface app AppxBundle and license file. 
+1. Using the procedure described in the [How to download Surface app from a Microsoft Store for Business account](#download-surface-app-from-a-microsoft-store-for-business-account) section of this article, download the Surface app AppxBundle and license file. 
-2.	Begin an elevated PowerShell session.
+2. Begin an elevated PowerShell session.
 
     >[!NOTE]
     >If you don’t run PowerShell as an Administrator, the session won’t have the required permissions to install the app.
     
-3.	In the elevated PowerShell session, copy and paste the following command:
+3. In the elevated PowerShell session, copy and paste the following command:
     ```
     Add-AppxProvisionedPackage –Online –PackagePath <DownloadPath>\ Microsoft.SurfaceHub_10.0.342.0_neutral_~_8wekyb3d8bbwe.AppxBundle –LicensePath <DownloadPath>\ Microsoft.SurfaceHub_8wekyb3d8bbwe_a53ef8ab-9dbd-dec1-46c5-7b664d4dd003.xml
     ```
@@ -125,7 +125,7 @@ The following procedure provisions the Surface app onto your computer and makes
     Add-AppxProvisionedPackage –Online –PackagePath c:\Temp\ Microsoft.SurfaceHub_10.0.342.0_neutral_~_8wekyb3d8bbwe.AppxBundle –LicensePath c:\Temp\ Microsoft.SurfaceHub_8wekyb3d8bbwe_a53ef8ab-9dbd-dec1-46c5-7b664d4dd003.xml
     ```
 
-4.	The Surface app will now be available on your current Windows computer. 
+4. The Surface app will now be available on your current Windows computer. 
 
 Before the Surface app is functional on the computer where it has been provisioned, you must also provision the frameworks described earlier in this article. To provision these frameworks, use the following procedure in the elevated PowerShell session you used to provision the Surface app.
 
@@ -151,18 +151,18 @@ The following procedure uses MDT to automate installation of the Surface app at
    * Working Directory: %DEPLOYROOT%\Applications\SurfaceApp
 
 For the Surface app to function on the target computer, it will also require the frameworks described earlier in this article. Use the following procedure to import the frameworks required for the Surface app into MDT and to configure them as dependencies.
-1.	Using the procedure described earlier in this article, download the framework files. Store each framework in a separate folder.
+1. Using the procedure described earlier in this article, download the framework files. Store each framework in a separate folder.
-2.	Using the New Application Wizard in the MDT Deployment Workbench, import the downloaded files as a new **Application with source files**.
+2. Using the New Application Wizard in the MDT Deployment Workbench, import the downloaded files as a new **Application with source files**.
-3.	On the **Command Details** page, type the file name of each application you downloaded in the **Command** field and the default Working Directory.
+3. On the **Command Details** page, type the file name of each application you downloaded in the **Command** field and the default Working Directory.
 
 To configure the frameworks as dependencies of the Surface app, use this process:
-1.	Open the properties of the Surface app in the MDT Deployment Workbench.
+1. Open the properties of the Surface app in the MDT Deployment Workbench.
-2.	Click the **Dependencies** tab, and then click **Add**.
+2. Click the **Dependencies** tab, and then click **Add**.
-3.	Select the check box for each framework using the name you provided in the New Application Wizard.
+3. Select the check box for each framework using the name you provided in the New Application Wizard.
 
 After import, the Surface app will be available for selection in the **Applications** step of the Windows Deployment Wizard. You can also install the application automatically by specifying the application in the deployment task sequence by following this process:
-1.	Open your deployment task sequence in the MDT Deployment Workbench.
+1. Open your deployment task sequence in the MDT Deployment Workbench.
-2.	Add a new **Install Application** task in the **State Restore** section of deployment.
+2. Add a new **Install Application** task in the **State Restore** section of deployment.
-3.	Select **Install a single application** and specify the **Surface App** as the **Application to be installed**.
+3. Select **Install a single application** and specify the **Surface App** as the **Application to be installed**.
 
 For more information about including apps into your Windows deployments, see [Deploy Windows 10 with the Microsoft Deployment Toolkit](https://technet.microsoft.com/itpro/windows/deploy/deploy-windows-10-with-the-microsoft-deployment-toolkit).

devices/surface/deploy-windows-10-to-surface-devices-with-mdt.md

@@ -579,10 +579,10 @@ After the task sequence is created it can be modified for increased automation,
 
 8. On the **Properties** tab of the new **Install Application** step, enter **Install Microsoft Office 2016 Click-to-Run** in the **Name** field.
 9. Click **Install a Single Application**, and then click **Browse** to view available applications that have been imported into the deployment share.
-10.	Select Office 2016 Click-to-Run from the list of applications, and then click **OK**.
+10. Select Office 2016 Click-to-Run from the list of applications, and then click **OK**.
-11.	Repeat Steps 6 through 10 for the Surface app.
+11. Repeat Steps 6 through 10 for the Surface app.
-12.	Expand the **Preinstall** folder, and then click the **Enable BitLocker (Offline)** step.
+12. Expand the **Preinstall** folder, and then click the **Enable BitLocker (Offline)** step.
-13.	Open the **Add** menu again and choose **Set Task Sequence Variable** from under the **General** menu.
+13. Open the **Add** menu again and choose **Set Task Sequence Variable** from under the **General** menu.
 14. On the **Properties** tab of the new **Set Task Sequence Variable** step (as shown in Figure 22), configure the following options:
     * **Name** – Set DriverGroup001
     * **Task Sequence Variable** – DriverGroup001
@@ -592,8 +592,8 @@ After the task sequence is created it can be modified for increased automation,
 
     *Figure 22. Configure a new Set Task Sequence Variable step in the deployment task sequence*
 
-15.	Select the **Inject Drivers** step, the next step in the task sequence.
+15. Select the **Inject Drivers** step, the next step in the task sequence.
-16.	On the **Properties** tab of the **Inject Drivers** step (as shown in Figure 23), configure the following options:
+16. On the **Properties** tab of the **Inject Drivers** step (as shown in Figure 23), configure the following options:
     * In the **Choose a selection profile** drop-down menu, select **Nothing**.
     * Click the **Install all drivers from the selection profile** button.
 
@@ -601,7 +601,7 @@ After the task sequence is created it can be modified for increased automation,
 
     *Figure 23. Configure the deployment task sequence not to choose the drivers to inject into Windows*
 
-17.	Click **OK** to apply changes to the task sequence and close the task sequence properties window.
+17. Click **OK** to apply changes to the task sequence and close the task sequence properties window.
 
 ### Configure deployment share rules
 

devices/surface/enroll-and-configure-surface-devices-with-semm.md

@@ -63,15 +63,15 @@ To create a Surface UEFI configuration package, follow these steps:
 
     *Figure 4. Disable or enable individual Surface components*
 
-11.	Click **Next**.
+11. Click **Next**.
-12.	To enable or disable advanced options in Surface UEFI or the display of Surface UEFI pages, on the **Choose the advanced settings for your devices** page, click the slider beside the desired setting to configure that option to **On** or **Off** (shown in Figure 5). In the **UEFI Front Page** section, you can use the sliders for **Security**, **Devices**, and **Boot** to control what pages are available to users who boot into Surface UEFI. (For more information about Surface UEFI settings, see [Manage Surface UEFI settings](https://technet.microsoft.com/itpro/surface/manage-surface-uefi-settings).) Click **Build** when you have finished selecting options to generate and save the package.
+12. To enable or disable advanced options in Surface UEFI or the display of Surface UEFI pages, on the **Choose the advanced settings for your devices** page, click the slider beside the desired setting to configure that option to **On** or **Off** (shown in Figure 5). In the **UEFI Front Page** section, you can use the sliders for **Security**, **Devices**, and **Boot** to control what pages are available to users who boot into Surface UEFI. (For more information about Surface UEFI settings, see [Manage Surface UEFI settings](https://technet.microsoft.com/itpro/surface/manage-surface-uefi-settings).) Click **Build** when you have finished selecting options to generate and save the package.
 
     ![Control advanced Surface UEFI settings and Surface UEFI pages](images/surface-ent-mgmt-fig4-advancedsettings.png "Control advanced Surface UEFI settings and Surface UEFI pages")
 
     *Figure 5. Control advanced Surface UEFI settings and Surface UEFI pages with SEMM*
 
-13.	In the **Save As** dialog box, specify a name for the Surface UEFI configuration package, browse to the location where you would like to save the file, and then click **Save**.
+13. In the **Save As** dialog box, specify a name for the Surface UEFI configuration package, browse to the location where you would like to save the file, and then click **Save**.
-14.	When the package is created and saved, the **Successful** page is displayed.
+14. When the package is created and saved, the **Successful** page is displayed.
 
 >[!NOTE]
 >Record the certificate thumbprint characters that are displayed on this page, as shown in Figure 6. You will need these characters to confirm enrollment of new Surface devices in SEMM. Click **End** to complete package creation and close Microsoft Surface UEFI Configurator.

devices/surface/surface-diagnostic-toolkit-business.md

@@ -59,9 +59,9 @@ SDT for Business is supported on Surface 3 and later devices, including:
 
 To create an SDT package that you can distribute to users in your organization:
 
-1.	Sign in to your Surface device using the Administrator account.
+1. Sign in to your Surface device using the Administrator account.
-2.	Download SDT Windows Installer Package (.msi) from the [Surface Tools for IT download page](https://www.microsoft.com/download/details.aspx?id=46703) and copy it to a preferred location on your Surface device, such as Desktop.
+2. Download SDT Windows Installer Package (.msi) from the [Surface Tools for IT download page](https://www.microsoft.com/download/details.aspx?id=46703) and copy it to a preferred location on your Surface device, such as Desktop.
-3.	The SDT setup wizard appears, as shown in figure 1. Click **Next**. 
+3. The SDT setup wizard appears, as shown in figure 1. Click **Next**. 
 
     >[!NOTE]
     >If the setup wizard does not appear, ensure that you are signed into the Administrator account on your computer. 
@@ -72,15 +72,15 @@ To create an SDT package that you can distribute to users in your organization:
 
 4. When the SDT setup wizard appears, click **Next**, accept the End User License Agreement (EULA)
 
-5.	On the Install Options screen, change the default install location if desired. 
+5. On the Install Options screen, change the default install location if desired. 
-6.	Under Setup Type, select **Advanced**. 
+6. Under Setup Type, select **Advanced**. 
 
     >[!NOTE]
     >The standard option allows users to run the diagnostic tool directly on their Surface device provided they are signed into their device using an Administrator account. 
     
      ![Install Options: Advanced](images/sdt-install.png)
 
-7.	Click **Next** and then click **Install**. 
+7. Click **Next** and then click **Install**. 
 
 ## Installing using the command line
 If desired, you can install SDT at a command prompt and set a custom flag to install the tool in admin mode. SDT contains the following install option flags:
@@ -90,7 +90,7 @@ If desired, you can install SDT at a command prompt and set a custom flag to ins
 
 ### To install SDT from the command line:
 
-1.	Open a command prompt and enter:
+1. Open a command prompt and enter:
 
     ```
     msiexec.exe /i <the path of installer> ADMINMODE=1. 
@@ -116,8 +116,8 @@ In addition to the .exe file, SDT installs a JSON file and an admin.dll file (mo
 
 Creating a custom package allows you to target the tool to specific known issues.
 
-1.	Click **Start > Run**, enter **Surface** and then click **Surface Diagnostic Toolkit for Business**. 
+1. Click **Start > Run**, enter **Surface** and then click **Surface Diagnostic Toolkit for Business**. 
-2.	When the tool opens, click **Create Custom Package**, as shown in figure 3.
+2. When the tool opens, click **Create Custom Package**, as shown in figure 3.
 
     ![Create custom package option](images/sdt-3.png)
 

devices/surface/surface-diagnostic-toolkit-desktop-mode.md

@@ -16,9 +16,9 @@ manager: dansimp
 
 This topic explains how to use the Surface Diagnostic Toolkit (SDT) to help users in your organization run the tool to identify and diagnose issues with the Surface device. Successfully running SDT can quickly determine if a reported issue is caused by failed hardware or user error.
 
-1.	Direct the user to install [the SDT package](surface-diagnostic-toolkit-business.md#create-custom-sdt) from a software distribution point or network share. After it is installed, you’re ready to guide the user through a series of tests. 
+1. Direct the user to install [the SDT package](surface-diagnostic-toolkit-business.md#create-custom-sdt) from a software distribution point or network share. After it is installed, you’re ready to guide the user through a series of tests. 
 
-2.	Begin at the home page, which allows users to enter a description of the issue, and click **Continue**, as shown in figure 1.
+2. Begin at the home page, which allows users to enter a description of the issue, and click **Continue**, as shown in figure 1.
 
     ![Start SDT in desktop mode](images/sdt-desk-1.png)
 
@@ -63,9 +63,9 @@ For each test, if functionality does not work as expected and the user clicks **
 
 *Figure 4. Running hardware diagnostics*
 
-1.	If the brightness successfully adjusts from 0-100 percent as expected, direct the user to click **Yes** and then click **Continue**. 
+1. If the brightness successfully adjusts from 0-100 percent as expected, direct the user to click **Yes** and then click **Continue**. 
-2.	If the brightness fails to adjust from 0-100 percent as expected, direct the user to click **No** and then click **Continue**. 
+2. If the brightness fails to adjust from 0-100 percent as expected, direct the user to click **No** and then click **Continue**. 
-3.	Guide users through remaining tests as appropriate. When finished, SDT automatically provides a high-level summary of the report, including the possible causes of any hardware issues along with guidance for resolution.
+3. Guide users through remaining tests as appropriate. When finished, SDT automatically provides a high-level summary of the report, including the possible causes of any hardware issues along with guidance for resolution.
 
 
 ### Repairing applications

devices/surface/surface-enterprise-management-mode.md

@@ -226,8 +226,16 @@ create a reset package using PowerShell to reset SEMM.
 
 ## Version History
 
+
+
+### Version 2.43.136.0
+* Support to enable/disable simulatenous multithreating 
+* Separate options for WiFi and Bluetooth for some devices 
+* Battery Limit removed for Surface Studio 
+
 ### Version 2.26.136.0
 * Add support to Surface Studio 2
+* Battery Limit feature
 
 ### Version 2.21.136.0
 * Add support to Surface Pro 6

devices/surface/unenroll-surface-devices-from-semm.md

@@ -118,9 +118,9 @@ To initiate a Recovery Request, follow these steps:
 
     *Figure 10. Click Recovery Request to begin the process to approve a Recovery Request*
 
-11.	Click **Certificate Protection** to authenticate the Recovery Request with the SEMM certificate.
+11. Click **Certificate Protection** to authenticate the Recovery Request with the SEMM certificate.
-12.	Browse to and select your SEMM certificate file, and then click **OK**.
+12. Browse to and select your SEMM certificate file, and then click **OK**.
-13.	When you are prompted to enter the certificate password as shown in Figure 11, type and confirm the password for the certificate file, and then click **OK**.
+13. When you are prompted to enter the certificate password as shown in Figure 11, type and confirm the password for the certificate file, and then click **OK**.
 
     ![Type password for SEMM certificate](images/surface-semm-unenroll-fig11.png "Type password for SEMM certificate")
 
@@ -137,7 +137,7 @@ To initiate a Recovery Request, follow these steps:
     * If you displayed the Recovery Request (Reset Request) as a QR Code and then used a messaging or email application to send the code to the computer with Microsoft Surface UEFI Configurator, copy and paste the code into the provided field.
     * If you saved the Recovery Request (Reset Request) as a file to a USB drive, click the **Import** button, browse to and select the Recovery Request (Reset Request) file, and then click **OK**.
 
-16.	The reset verification code is displayed in Microsoft Surface UEFI Configurator, as shown in Figure 13.
+16. The reset verification code is displayed in Microsoft Surface UEFI Configurator, as shown in Figure 13.
 
     ![Display of the reset verification code](images/surface-semm-unenroll-fig13.png "Display of the reset verification code")
 
@@ -145,13 +145,13 @@ To initiate a Recovery Request, follow these steps:
 
     * Click the **Share** button to send the reset verification code by email.
 
-17.	Enter the reset verification code in the provided field on the Surface device (shown in Figure 8), and then click or press **Verify** to reset the device and unenroll the device from SEMM.
+17. Enter the reset verification code in the provided field on the Surface device (shown in Figure 8), and then click or press **Verify** to reset the device and unenroll the device from SEMM.
-18.	Click or press **Restart now** on the **SEMM reset successful** page to complete the unenrollment from SEMM, as shown in Figure 14.
+18. Click or press **Restart now** on the **SEMM reset successful** page to complete the unenrollment from SEMM, as shown in Figure 14.
 
     ![Example display of successful unenrollment from SEMM](images/surface-semm-unenroll-fig14.png "Example display of successful unenrollment from SEMM")
 
     *Figure 14. Successful unenrollment from SEMM*
 
-19.	Click **End** in Microsoft Surface UEFI Configurator to complete the Recovery Request (Reset Request) process and close Microsoft Surface UEFI Configurator.
+19. Click **End** in Microsoft Surface UEFI Configurator to complete the Recovery Request (Reset Request) process and close Microsoft Surface UEFI Configurator.
 
 

devices/surface/using-the-sda-deployment-share.md

@@ -141,23 +141,23 @@ In the previous example for including drivers for a POS system, you would also n
 
 9. Click the **Task Sequence** tab to view the steps that are included in the new task sequence.
 
-10.	Select the **Windows Update (Pre-Application Installation)** step, and then click **Add**.
+10. Select the **Windows Update (Pre-Application Installation)** step, and then click **Add**.
 
-11.	Hover the mouse over **General** under the **Add** menu, and then click **Install Application**. This will add a new step after the selected step for the installation of a specific application as shown in Figure 3.
+11. Hover the mouse over **General** under the **Add** menu, and then click **Install Application**. This will add a new step after the selected step for the installation of a specific application as shown in Figure 3.
 
     ![A new Install Application step for Sample POS App](images/using-sda-newinstall-fig3.png "A new Install Application step for Sample POS App")
   
     *Figure 3. A new Install Application step for Sample POS App*
 
-12.	On the **Properties** tab of the new **Install Application** step, enter **Install - Sample POS App** in the **Name** field, where *Sample POS App* is the name of your app.
+12. On the **Properties** tab of the new **Install Application** step, enter **Install - Sample POS App** in the **Name** field, where *Sample POS App* is the name of your app.
 
-13.	Click **Install a Single Application**, and then click **Browse** to view available applications that have been imported into the deployment share.
+13. Click **Install a Single Application**, and then click **Browse** to view available applications that have been imported into the deployment share.
 
-14.	Select your app from the list of applications, and then click **OK**.
+14. Select your app from the list of applications, and then click **OK**.
 
-15.	Click **OK** to close the task sequence properties.
+15. Click **OK** to close the task sequence properties.
 
-16.	Close the Deployment Workbench.
+16. Close the Deployment Workbench.
 
 ## Work with existing deployment shares
 

education/trial-in-a-box/educator-tib-get-started.md

@@ -182,9 +182,9 @@ Use video to create a project summary.
 
 9. Select the first card in the Storyboard (the video of the project materials) and select **Text**, type a title in, a text style, a layout, and select **Done**.
 
-10.	Select the third card in the Storyboard (the video of the children assembling the maze) and select **Trim**.  Drag the trim handle on the left to shorten the duration of the clip and select **Done**.
+10. Select the third card in the Storyboard (the video of the children assembling the maze) and select **Trim**.  Drag the trim handle on the left to shorten the duration of the clip and select **Done**.
 
-11.	Select the last card on the Storyboard and select **3D effects**.
+11. Select the last card on the Storyboard and select **3D effects**.
     1. Position the playback indicator to be roughly 1 second into the video clip, or when the boy moves down to examine the laser.
     2. Find the **lightning bolt** effect and click or drag to add it to the scene.  Rotate, scale, and position the effect so it looks like the lightning is coming out of the laser beam and hitting the black back of the mirror.
     3. Position the blue anchor over the end of the laser pointer in the video and toggle on **Attach to a point** for the lightning bolt effect to anchor the effect in the scene.

education/windows/deploy-windows-10-in-a-school-district.md

@@ -1247,7 +1247,7 @@ You can use Windows Deployment Services in conjunction with System Center Config
 
     To support PXE boot requests, you install the PXE service point site system role. Then, you must configure one or more distribution points to respond to PXE boot request.
     For more information about how to perform this step, see [Install site system roles for System Center Configuration Manager](https://technet.microsoft.com/library/mt704036.aspx), [Use PXE to deploy Windows over the network with System Center Configuration Manager](https://technet.microsoft.com/library/mt627940.aspx), and [Configuring distribution points to accept PXE requests](https://technet.microsoft.com/library/mt627944.aspx#BKMK_PXEDistributionPoint).
-3.	Configure the appropriate boot images (Windows PE images) to deploy from the PXE-enabled distribution point.
+3. Configure the appropriate boot images (Windows PE images) to deploy from the PXE-enabled distribution point.
 
     Before a device can start a boot image from a PXE-enabled distribution point, you must change the properties of the boot image to enable PXE booting. Typically, you create this boot image when you created your MDT task sequence in the Configuration Manager console.
 

education/windows/edu-deployment-recommendations.md

@@ -123,10 +123,10 @@ If you want to delete either (or both) the Skype and the Xbox accounts, here’s
 To delete a Skype account, you can follow the instructions here: [How do I close my Skype account?](https://go.microsoft.com/fwlink/?LinkId=816515)
 
 If you need help deleting the account, you can contact Skype customer service by going to the [Skype support request page](https://go.microsoft.com/fwlink/?LinkId=816519). You may need to sign in and specify a Skype account. Once you’ve signed in, you can:
-1.	Select a help topic (**Account and Password**)
+1. Select a help topic (**Account and Password**)
-2.	Select a related problem (**Deleting an account**)
+2. Select a related problem (**Deleting an account**)
-3.	Click **Next**.
+3. Click **Next**.
-4.	Select a contact method to get answers to your questions.
+4. Select a contact method to get answers to your questions.
 
 
 #### Xbox

education/windows/teacher-get-minecraft.md

@@ -49,9 +49,9 @@ You can purchase individual Minecraft: Education Edition subscriptions for you a
 
 To purchase individual Minecraft: Education Edition subscriptions (i.e. direct purchase):
 
-1.	Sign in to [Microsoft Store for Education](https://educationstore.microsoft.com/) with your Office 365 account.
+1. Sign in to [Microsoft Store for Education](https://educationstore.microsoft.com/) with your Office 365 account.
-2.	Click on [Minecraft: Education Edition](https://educationstore.microsoft.com/en-us/store/details/minecraft-education-edition/9nblggh4r2r6) (or use Search the Store to find it)
+2. Click on [Minecraft: Education Edition](https://educationstore.microsoft.com/en-us/store/details/minecraft-education-edition/9nblggh4r2r6) (or use Search the Store to find it)
-3.	Click **Buy**
+3. Click **Buy**
 
 >[!Note]
 >Administrators can restrict the ability for teachers to purchase applications in the Microsoft Store for Education. If you do not have the ability to Buy, contact your school administration or IT administrator.

mdop/appv-v4/delete-package.md

@@ -19,7 +19,7 @@ ms.date: 06/16/2016
 
 Removes a package record and the applications associated with it.
 
-` SFTMIME DELETE PACKAGE:package-name                 [/LOG log-pathname | /CONSOLE | /GUI]`
+`SFTMIME DELETE PACKAGE:package-name                 [/LOG log-pathname | /CONSOLE | /GUI]`
 
 <table>
 <colgroup>

mdop/appv-v4/sfttray-command-reference.md

@@ -31,23 +31,23 @@ There is only one Application Virtualization Client Tray instance for each user
 
 
 
-`     Sfttray.exe /?`
+`Sfttray.exe /?`
 
 ### Command Usage
 
-`     Sfttray.exe [/HIDE | /SHOW]`
+`Sfttray.exe [/HIDE | /SHOW]`
 
-`     Sfttray.exe [/HIDE | /SHOW] [/QUIET] [/EXE alternate-exe] /LAUNCH app [args]`
+`Sfttray.exe [/HIDE | /SHOW] [/QUIET] [/EXE alternate-exe] /LAUNCH app [args]`
 
-`     Sfttray.exe [/HIDE | /SHOW] [/QUIET] /LOAD app [/SFTFILE sft]`
+`Sfttray.exe [/HIDE | /SHOW] [/QUIET] /LOAD app [/SFTFILE sft]`
 
-`     Sfttray.exe [/HIDE | /SHOW] [/QUIET] /LOADALL`
+`Sfttray.exe [/HIDE | /SHOW] [/QUIET] /LOADALL`
 
-`     Sfttray.exe [/HIDE | /SHOW] [/QUIET] /REFRESHALL`
+`Sfttray.exe [/HIDE | /SHOW] [/QUIET] /REFRESHALL`
 
-`     Sfttray.exe [/HIDE | /SHOW] [/QUIET] /LAUNCHRESULT <UNIQUE ID>  /LAUNCH app [args]`
+`Sfttray.exe [/HIDE | /SHOW] [/QUIET] /LAUNCHRESULT <UNIQUE ID>  /LAUNCH app [args]`
 
-`     Sfttray.exe /EXIT`
+`Sfttray.exe /EXIT`
 
 ### Command-Line Switches
 

mdop/appv-v5/how-to-install-the-publishing-server-on-a-remote-computer.md

@@ -51,21 +51,16 @@ Use the following procedure to install the publishing server on a separate compu
 
 9. To verify if the publishing server is running correctly, you should import a package to the management server, entitle the package to an AD group, and publish the package. Using an internet browser, open the following URL: <strong>http://publishingserver:pubport</strong>. If the server is running correctly information similar to the following will be displayed:
 
-   `<Publishing Protocol="1.0">`
+   ```xml
-
+   <Publishing Protocol="1.0">
-   `  <Packages>`
+     <Packages>
-
+       <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" VersionId="5d03c08f-51dc-4026-8cf9-15ebe3d65a72" PackageUrl="\\server\share\file.appv" />
-   `  <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" VersionId="5d03c08f-51dc-4026-8cf9-15ebe3d65a72" PackageUrl="\\server\share\file.appv" />`
+     </Packages>
-
+     <NoGroup>
-   `  </Packages>`
+       <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" />
-
+     </NoGroup>
-   `  <NoGroup>`
+   </Publishing>
-
+   ```
-   `  <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" />`
-
-   `  </NoGroup>`
-
-   `</Publishing>`
 
    **Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
 

mdop/appv-v5/how-to-install-the-publishing-server-on-a-remote-computer51.md

@@ -51,21 +51,16 @@ Use the following procedure to install the publishing server on a separate compu
 
 9. To verify if the publishing server is running correctly, you should import a package to the management server, entitle the package to an AD group, and publish the package. Using an internet browser, open the following URL: <strong>http://publishingserver:pubport</strong>. If the server is running correctly information similar to the following will be displayed:
 
-   `<Publishing Protocol="1.0">`
+   ```xml
-
+   <Publishing Protocol="1.0">
-   `  <Packages>`
+     <Packages>
-
+       <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" VersionId="5d03c08f-51dc-4026-8cf9-15ebe3d65a72" PackageUrl="\\server\share\file.appv" />
-   `  <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" VersionId="5d03c08f-51dc-4026-8cf9-15ebe3d65a72" PackageUrl="\\server\share\file.appv" />`
+     </Packages>
-
+     <NoGroup>
-   `  </Packages>`
+       <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" />
-
+     </NoGroup>
-   `  <NoGroup>`
+   </Publishing>
-
+   ```
-   `  <Package PackageId="28115343-06e2-44dc-a327-3a0b9b868bda" />`
-
-   `  </NoGroup>`
-
-   `</Publishing>`
 
    **Got a suggestion for App-V**? Add or vote on suggestions [here](http://appv.uservoice.com/forums/280448-microsoft-application-virtualization). **Got an App-V issue?** Use the [App-V TechNet Forum](https://social.technet.microsoft.com/Forums/home?forum=mdopappv).
 

mdop/mbam-v1/how-to-move-mbam-10-features-to-another-computer.md

@@ -88,49 +88,55 @@ You can use the following procedure to move the MBAM Recovery and Hardware Datab
 
     Modify the MBAM Recovery and Hardware Database to use the full recovery mode.
 
-    `USE master;`
+    ```sql
+    USE master;
 
-    `GO`
+    GO
 
-    `ALTER DATABASE "MBAM Recovery and Hardware"`
+    ALTER DATABASE "MBAM Recovery and Hardware"
 
-    `   SET RECOVERY FULL;`
+       SET RECOVERY FULL;
 
-    `GO`
+    GO
+    ```
 
     Create MBAM Recovery and Hardware Database Data and MBAM Recovery logical backup devices.
 
-    `USE master`
+    ```sql
+    USE master
 
-    `GO`
+    GO
 
-    `EXEC sp_addumpdevice 'disk', 'MBAM Recovery and Hardware Database Data Device',`
+    EXEC sp_addumpdevice 'disk', 'MBAM Recovery and Hardware Database Data Device',
 
-    `'Z:\MBAM Recovery and Hardware Database Data.bak';`
+    'Z:\MBAM Recovery and Hardware Database Data.bak';
 
-    `GO`
+    GO
+    ```
 
     Back up the full MBAM Recovery and Hardware database.
 
-    `BACKUP DATABASE [MBAM Recovery and Hardware] TO [MBAM Recovery and Hardware Database Data Device];`
+    ```sql
+    BACKUP DATABASE [MBAM Recovery and Hardware] TO [MBAM Recovery and Hardware Database Data Device];
 
-    `GO`
+    GO
 
-    `BACKUP CERTIFICATE [MBAM Recovery Encryption Certificate]`
+    BACKUP CERTIFICATE [MBAM Recovery Encryption Certificate]
 
-    `TO FILE = 'Z:\SQLServerInstanceCertificateFile'`
+    TO FILE = 'Z:\SQLServerInstanceCertificateFile'
 
-    `WITH PRIVATE KEY`
+    WITH PRIVATE KEY
 
-    `(`
+    (
 
-    `    FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',`
+        FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',
 
-    `    ENCRYPTION BY PASSWORD = '$PASSWORD$'`
+        ENCRYPTION BY PASSWORD = '$PASSWORD$'
 
-    `);`
+    );
 
-    `GO`
+    GO
+    ```
 
     **Note**  
     Replace the values from the preceding example with those that match your environment:
@@ -181,43 +187,51 @@ You can use the following procedure to move the MBAM Recovery and Hardware Datab
 
 4.  To automate this procedure, create a SQL file (.sql) that contains the following SQL script:
 
-    `-- Restore MBAM Recovery and Hardware Database. `
+    ```sql
+    -- Restore MBAM Recovery and Hardware Database. 
 
-    `USE master`
+    USE master
 
-    `GO`
+    GO
+    ```
 
     Drop the certificate created by MBAM Setup.
 
-    `DROP CERTIFICATE [MBAM Recovery Encryption Certificate]`
+    ```sql
+    DROP CERTIFICATE [MBAM Recovery Encryption Certificate]
 
-    `GO`
+    GO
+    ```
 
     Add certificate
 
-    `CREATE CERTIFICATE [MBAM Recovery Encryption Certificate]`
+    ```sql
+    CREATE CERTIFICATE [MBAM Recovery Encryption Certificate]
 
-    `FROM FILE = 'Z: \SQLServerInstanceCertificateFile'`
+    FROM FILE = 'Z: \SQLServerInstanceCertificateFile'
 
-    `WITH PRIVATE KEY`
+    WITH PRIVATE KEY
 
-    `(`
+    (
 
-    `    FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',`
+        FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',
 
-    `    DECRYPTION BY PASSWORD = '$PASSWORD$'`
+        DECRYPTION BY PASSWORD = '$PASSWORD$'
 
-    `);`
+    );
 
-    `GO`
+    GO
+    ```
 
     Restore the MBAM Recovery and Hardware database data and the log files.
 
-    `RESTORE DATABASE [MBAM Recovery and Hardware]`
+    ```sql
+    RESTORE DATABASE [MBAM Recovery and Hardware]
 
-    `   FROM DISK = 'Z:\MBAM Recovery and Hardware Database Data.bak'`
+       FROM DISK = 'Z:\MBAM Recovery and Hardware Database Data.bak'
 
-    `   WITH REPLACE`
+       WITH REPLACE
+    ```
 
     **Note**  
     Replace the values from the preceding example with those that match your environment:
@@ -354,35 +368,37 @@ If you choose to move the MBAM Compliance Status Database feature from one compu
 
 2.  To automate this procedure, create a SQL file (.sql) that contains the following-SQL script:
 
-    `-- Modify the MBAM Compliance Status Database to use the full recovery model.`
+    ```sql
+    -- Modify the MBAM Compliance Status Database to use the full recovery model.
 
-    `USE master;`
+    USE master;
 
-    `GO`
+    GO
 
-    `ALTER DATABASE "MBAM Compliance Status"`
+    ALTER DATABASE "MBAM Compliance Status"
 
-    `   SET RECOVERY FULL;`
+       SET RECOVERY FULL;
 
-    `GO`
+    GO
 
-    `-- Create MBAM Compliance Status Data logical backup devices.`
+    -- Create MBAM Compliance Status Data logical backup devices.
 
-    `USE master`
+    USE master
 
-    `GO`
+    GO
 
-    `EXEC sp_addumpdevice 'disk', 'MBAM Compliance Status Database Data Device',`
+    EXEC sp_addumpdevice 'disk', 'MBAM Compliance Status Database Data Device',
 
-    `'Z: \MBAM Compliance Status Database Data.bak';`
+    'Z: \MBAM Compliance Status Database Data.bak';
 
-    `GO`
+    GO
 
     -- Back up the full MBAM Recovery and Hardware database.
 
-    `BACKUP DATABASE [MBAM Compliance Status] TO [MBAM Compliance Status Database Data Device];`
+    BACKUP DATABASE [MBAM Compliance Status] TO [MBAM Compliance Status Database Data Device];
 
-    `GO`
+    GO
+    ```
 
 3.  Run the SQL file with a command that is similar to the following one, by using the SQL Server PowerShell:
 
@@ -422,19 +438,21 @@ If you choose to move the MBAM Compliance Status Database feature from one compu
 
 3.  To automate this procedure, create a SQL file (.sql) that contains the following-SQL script:
 
-    `-- Create MBAM Compliance Status Database Data logical backup devices. `
+    ```sql
+    -- Create MBAM Compliance Status Database Data logical backup devices. 
 
-    `Use master`
+    Use master
 
-    `GO`
+    GO
 
     -- Restore the MBAM Compliance Status database data files.
 
-    `RESTORE DATABASE [MBAM Compliance Status Database]`
+    RESTORE DATABASE [MBAM Compliance Status Database]
 
-    `   FROM DISK = 'C:\test\MBAM Compliance Status Database Data.bak'`
+       FROM DISK = 'C:\test\MBAM Compliance Status Database Data.bak'
 
-    `   WITH REPLACE`
+       WITH REPLACE
+    ```
 
 4.  Run the SQL File with a command that is similar to the following one, by using the SQL Server PowerShell:
 

mdop/mbam-v2/how-to-move-mbam-20-features-to-another-computer-mbam-2.md

@@ -88,49 +88,51 @@ To move the Recovery Database from one computer to another (for example, from Se
 
     Modify the MBAM Recovery Database to use the full recovery mode.
 
-    `USE master;`
+    ```sql
+    USE master;
 
-    `GO`
+    GO
 
-    `ALTER DATABASE "MBAM Recovery and Hardware"`
+    ALTER DATABASE "MBAM Recovery and Hardware"
 
-    `   SET RECOVERY FULL;`
+       SET RECOVERY FULL;
 
-    `GO`
+    GO
 
     -- Create MBAM Recovery Database Data and MBAM Recovery logical backup devices.
 
-    `USE master`
+    USE master
 
-    `GO`
+    GO
 
-    `EXEC sp_addumpdevice 'disk', 'MBAM Recovery and Hardware Database Data Device',`
+    EXEC sp_addumpdevice 'disk', 'MBAM Recovery and Hardware Database Data Device',
 
-    `'Z:\MBAM Recovery Database Data.bak';`
+    'Z:\MBAM Recovery Database Data.bak';
 
-    `GO`
+    GO
 
     -- Back up the full MBAM Recovery Database.
 
-    `BACKUP DATABASE [MBAM Recovery and Hardware] TO [MBAM Recovery and Hardware Database Data Device];`
+    BACKUP DATABASE [MBAM Recovery and Hardware] TO [MBAM Recovery and Hardware Database Data Device];
 
-    `GO`
+    GO
 
-    `BACKUP CERTIFICATE [MBAM Recovery Encryption Certificate]`
+    BACKUP CERTIFICATE [MBAM Recovery Encryption Certificate]
 
-    `TO FILE = 'Z:\SQLServerInstanceCertificateFile'`
+    TO FILE = 'Z:\SQLServerInstanceCertificateFile'
 
-    `WITH PRIVATE KEY`
+    WITH PRIVATE KEY
 
-    `(`
+    (
 
-    `    FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',`
+        FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',
 
-    `    ENCRYPTION BY PASSWORD = '$PASSWORD$'`
+        ENCRYPTION BY PASSWORD = '$PASSWORD$'
 
-    `);`
+    );
 
-    `GO`
+    GO
+    ```
 
     **Note**  
     Replace the following values in the example above with those that match your environment:
@@ -183,43 +185,45 @@ To move the Recovery Database from one computer to another (for example, from Se
 
 4.  To automate this procedure, create a SQL file (.sql) that contains the following-SQL script:
 
-    `-- Restore MBAM Recovery Database. `
+    ```sql
+    -- Restore MBAM Recovery Database. 
 
-    `USE master`
+    USE master
 
-    `GO`
+    GO
 
     -- Drop certificate created by MBAM Setup.
 
-    `DROP CERTIFICATE [MBAM Recovery Encryption Certificate]`
+    DROP CERTIFICATE [MBAM Recovery Encryption Certificate]
 
-    `GO`
+    GO
 
     --Add certificate
 
-    `CREATE CERTIFICATE [MBAM Recovery Encryption Certificate]`
+    CREATE CERTIFICATE [MBAM Recovery Encryption Certificate]
 
-    `FROM FILE = 'Z: \SQLServerInstanceCertificateFile'`
+    FROM FILE = 'Z: \SQLServerInstanceCertificateFile'
 
-    `WITH PRIVATE KEY`
+    WITH PRIVATE KEY
 
-    `(`
+    (
 
-    `    FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',`
+        FILE = ' Z:\SQLServerInstanceCertificateFilePrivateKey',
 
-    `    DECRYPTION BY PASSWORD = '$PASSWORD$'`
+        DECRYPTION BY PASSWORD = '$PASSWORD$'
 
-    `);`
+    );
 
-    `GO`
+    GO
 
     -- Restore the MBAM Recovery Database data and log files.
 
-    `RESTORE DATABASE [MBAM Recovery and Hardware]`
+    RESTORE DATABASE [MBAM Recovery and Hardware]
 
-    `   FROM DISK = 'Z:\MBAM Recovery Database Data.bak'`
+       FROM DISK = 'Z:\MBAM Recovery Database Data.bak'
 
-    `   WITH REPLACE`
+       WITH REPLACE
+    ```
 
     **Note**  
     Replace the following values in the example above with those that match your environment:
@@ -362,35 +366,37 @@ If you want to move the MBAM Compliance and Audit Database from one computer to
 
 2.  To automate this procedure, create a SQL file (.sql) that contains the following-SQL script:
 
-    `-- Modify the MBAM Compliance Status Database to use the full recovery model.`
+    ```sql
+    -- Modify the MBAM Compliance Status Database to use the full recovery model.
 
-    `USE master;`
+    USE master;
 
-    `GO`
+    GO
 
-    `ALTER DATABASE "MBAM Compliance Status"`
+    ALTER DATABASE "MBAM Compliance Status"
 
-    `   SET RECOVERY FULL;`
+       SET RECOVERY FULL;
 
-    `GO`
+    GO
 
-    `-- Create MBAM Compliance Status Data logical backup devices.`
+    -- Create MBAM Compliance Status Data logical backup devices.
 
-    `USE master`
+    USE master
 
-    `GO`
+    GO
 
-    `EXEC sp_addumpdevice 'disk', 'MBAM Compliance Status Database Data Device',`
+    EXEC sp_addumpdevice 'disk', 'MBAM Compliance Status Database Data Device',
 
-    `'Z: \MBAM Compliance Status Database Data.bak';`
+    'Z: \MBAM Compliance Status Database Data.bak';
 
-    `GO`
+    GO
 
     -- Back up the full MBAM Recovery database.
 
-    `BACKUP DATABASE [MBAM Compliance Status] TO [MBAM Compliance Status Database Data Device];`
+    BACKUP DATABASE [MBAM Compliance Status] TO [MBAM Compliance Status Database Data Device];
 
-    `GO`
+    GO
+    ```
 
 3.  Run the SQL file by using a Windows PowerShell command line that is similar to the following:
 
@@ -430,19 +436,21 @@ If you want to move the MBAM Compliance and Audit Database from one computer to
 
 3.  To automate this procedure, create a SQL file (.sql) that contains the following-SQL script:
 
-    `-- Create MBAM Compliance Status Database Data logical backup devices. `
+    ```sql
+    -- Create MBAM Compliance Status Database Data logical backup devices. 
 
-    `Use master`
+    Use master
 
-    `GO`
+    GO
 
     -- Restore the MBAM Compliance Status database data files.
 
-    `RESTORE DATABASE [MBAM Compliance Status]`
+    RESTORE DATABASE [MBAM Compliance Status]
 
-    `   FROM DISK = 'C:\test\MBAM Compliance Status Database Data.bak'`
+       FROM DISK = 'C:\test\MBAM Compliance Status Database Data.bak'
 
-    `   WITH REPLACE`
+       WITH REPLACE
+    ```
 
 4.  Run the SQL File by using a Windows PowerShell command line that is similar to the following:
 

mdop/uev-v2/application-template-schema-reference-for-ue-v-2x-both-uevv2.md

@@ -240,7 +240,7 @@ Version identifies the version of the settings location template for administrat
 
 **Hint:** You can save notes about version changes using XML comment tags `<!-- -->`, for example:
 
-``` syntax
+```xml
   <!--
      Version History
 
@@ -279,25 +279,25 @@ Author identifies the creator of the settings location template. Two optional ch
 
 Processes contains at least one `<Process>` element, which in turn contains the following child elements: **Filename**, **Architecture**, **ProductName**, **FileDescription**, **ProductVersion**, and **FileVersion**. The Filename child element is mandatory and the others are optional. A fully populated element contains tags similar to this example:
 
-``` syntax
+```xml
-    <Process>
+<Process>
-      <Filename>MyApplication.exe</Filename>
+  <Filename>MyApplication.exe</Filename>
-      <Architecture>Win64</Architecture>
+  <Architecture>Win64</Architecture>
-      <ProductName> MyApplication </ProductName>
+  <ProductName> MyApplication </ProductName>
-      <FileDescription>MyApplication.exe</FileDescription>
+  <FileDescription>MyApplication.exe</FileDescription>
-      <ProductVersion>
+  <ProductVersion>
-        <Major Minimum="2" Maximum="2" />
+    <Major Minimum="2" Maximum="2" />
-        <Minor Minimum="0" Maximum="0" />
+    <Minor Minimum="0" Maximum="0" />
-        <Build Minimum="0" Maximum="0" />
+    <Build Minimum="0" Maximum="0" />
-        <Patch Minimum="5" Maximum="5" />
+    <Patch Minimum="5" Maximum="5" />
-      </ProductVersion>
+  </ProductVersion>
-      <FileVersion>
+  <FileVersion>
-        <Major Minimum="2" Maximum="2" />
+    <Major Minimum="2" Maximum="2" />
-        <Minor Minimum="0" Maximum="0" />
+    <Minor Minimum="0" Maximum="0" />
-        <Build Minimum="0" Maximum="0" />
+    <Build Minimum="0" Maximum="0" />
-        <Patch Minimum="5" Maximum="5" />
+    <Patch Minimum="5" Maximum="5" />
-      </FileVersion>
+  </FileVersion>
-    </Process>
+</Process>
 ```
 
 ### Filename
@@ -354,14 +354,14 @@ UE-V does not support ARM processors in this version.
 
 ProductName is an optional element used to identify a product for administrative purposes or reporting. ProductName differs from Filename in that there are no regular expression restrictions on its value. This allows for more easily understood descriptions of a process where the executable name may not be obvious. For example:
 
-``` syntax
+```xml
-    <Process>
+<Process>
-      <Filename>MyApplication.exe</Filename>
+  <Filename>MyApplication.exe</Filename>
-      <ProductName>My Application 6.x by Contoso.com</ProductName>
+  <ProductName>My Application 6.x by Contoso.com</ProductName>
-      <ProductVersion>
+  <ProductVersion>
-        <Major Minimum="6" Maximum="6" />
+    <Major Minimum="6" Maximum="6" />
-      </ProductVersion>
+  </ProductVersion>
-    </Process>
+</Process>
 ```
 
 ### FileDescription
@@ -374,23 +374,22 @@ FileDescription is an optional tag that allows for an administrative description
 
 For example, in a suited application, it might be useful to provide reminders about the function of two executables (MyApplication.exe and MyApplicationHelper.exe), as shown here:
 
-``` syntax
+```xml
 <Processes>
-
+  <Process>
-   <Process>
+    <Filename>MyApplication.exe</Filename>
-      <Filename>MyApplication.exe</Filename>
+    <FileDescription>My Application Main Engine</ FileDescription>
-      <FileDescription>My Application Main Engine</ FileDescription>
+    <ProductVersion>
-      <ProductVersion>
+      <Major Minimum="6" Maximum="6" />
-        <Major Minimum="6" Maximum="6" />
+    </ProductVersion>
-      </ProductVersion>
+  </Process>
-    </Process>
+  <Process>
-    <Process>
+    <Filename>MyApplicationHelper.exe</Filename>
-      <Filename>MyApplicationHelper.exe</Filename>
+    <FileDescription>My Application Background Process Executable</FileDescription>
-      <FileDescription>My Application Background Process Executable</FileDescription>
+    <ProductVersion>
-      <ProductVersion>
+      <Major Minimum="6" Maximum="6" />
-        <Major Minimum="6" Maximum="6" />
+    </ProductVersion>
-      </ProductVersion>
+  </Process>
-    </Process>
 </Processes>
 ```
 
@@ -408,44 +407,44 @@ The product and file version elements may be left unspecified. Doing so makes th
 
 Product version: 1.0 specified in the UE-V Generator produces the following XML:
 
-``` syntax
+```xml
-      <ProductVersion>
+<ProductVersion>
-        <Major Minimum="1" Maximum="1" />
+  <Major Minimum="1" Maximum="1" />
-        <Minor Minimum="0" Maximum="0" />
+  <Minor Minimum="0" Maximum="0" />
-      </ProductVersion>
+</ProductVersion>
 ```
 
 **Example 2:**
 
 File version: 5.0.2.1000 specified in the UE-V Generator produces the following XML:
 
-``` syntax
+```xml
-      <FileVersion>
+<FileVersion>
-        <Major Minimum="5" Maximum="5" />
+  <Major Minimum="5" Maximum="5" />
-        <Minor Minimum="0" Maximum="0" />
+  <Minor Minimum="0" Maximum="0" />
-        <Build Minimum="2" Maximum="2" />
+  <Build Minimum="2" Maximum="2" />
-        <Patch Minimum="1000" Maximum="1000" />
+  <Patch Minimum="1000" Maximum="1000" />
-      </FileVersion>
+</FileVersion>
 ```
 
 **Incorrect Example 1 – incomplete range:**
 
 Only the Minimum attribute is present. Maximum must be included in a range as well.
 
-``` syntax
+```xml
-      <ProductVersion>
+<ProductVersion>
-        <Major Minimum="2" />
+  <Major Minimum="2" />
-      </ProductVersion>
+</ProductVersion>
 ```
 
 **Incorrect Example 2 – Minor specified without Major element:**
 
 Only the Minor element is present. Major must be included as well.
 
-``` syntax
+```xml
-      <ProductVersion>
+<ProductVersion>
-        <Minor Minimum="0" Maximum="0" />
+  <Minor Minimum="0" Maximum="0" />
-      </ProductVersion>
+</ProductVersion>
 ```
 
 ### FileVersion
@@ -462,19 +461,19 @@ Including a FileVersion element for an application allows for more granular fine
 
 The child elements and syntax rules for FileVersion are identical to those of ProductVersion.
 
-``` syntax
+```xml
-      <Process>
+<Process>
-        <Filename>MSACCESS.EXE</Filename>
+  <Filename>MSACCESS.EXE</Filename>
-        <Architecture>Win32</Architecture>
+  <Architecture>Win32</Architecture>
-        <ProductVersion>
+  <ProductVersion>
-          <Major Minimum="14" Maximum="14" />
+    <Major Minimum="14" Maximum="14" />
-          <Minor Minimum="0" Maximum="0" />
+    <Minor Minimum="0" Maximum="0" />
-        </ProductVersion>
+  </ProductVersion>
-        <FileVersion>
+  <FileVersion>
-          <Major Minimum="14" Maximum="14" />
+    <Major Minimum="14" Maximum="14" />
-          <Minor Minimum="0" Maximum="0" />
+    <Minor Minimum="0" Maximum="0" />
-        </FileVersion>
+  </FileVersion>
-      </Process>
+</Process>
 ```
 
 ### <a href="" id="application21"></a>Application Element
@@ -1177,16 +1176,16 @@ Version identifies the version of the settings location template for administrat
 
 **Hint:** You can save notes about version changes using XML comment tags `<!-- -->`, for example:
 
-``` syntax
+```xml
-  <!--
+<!--
-     Version History
+    Version History
 
-     Version 1 Jul 05, 2012 Initial template created by Generator - Denise@Contoso.com
+    Version 1 Jul 05, 2012 Initial template created by Generator - Denise@Contoso.com
-     Version 2 Jul 31, 2012 Added support for app.exe v2.1.3 - Mark@Contoso.com
+    Version 2 Jul 31, 2012 Added support for app.exe v2.1.3 - Mark@Contoso.com
-     Version 3 Jan 01, 2013 Added font settings support - Mark@Contoso.com
+    Version 3 Jan 01, 2013 Added font settings support - Mark@Contoso.com
-     Version 4 Jan 31, 2013 Added support for plugin settings - Tony@Contoso.com
+    Version 4 Jan 31, 2013 Added support for plugin settings - Tony@Contoso.com
-   -->
+  -->
-  <Version>4</Version>
+<Version>4</Version>
 ```
 
 **Important**  
@@ -1216,25 +1215,25 @@ Author identifies the creator of the settings location template. Two optional ch
 
 Processes contains at least one `<Process>` element, which in turn contains the following child elements: **Filename**, **Architecture**, **ProductName**, **FileDescription**, **ProductVersion**, and **FileVersion**. The Filename child element is mandatory and the others are optional. A fully populated element contains tags similar to this example:
 
-``` syntax
+```xml
-    <Process>
+<Process>
-      <Filename>MyApplication.exe</Filename>
+  <Filename>MyApplication.exe</Filename>
-      <Architecture>Win64</Architecture>
+  <Architecture>Win64</Architecture>
-      <ProductName> MyApplication </ProductName>
+  <ProductName> MyApplication </ProductName>
-      <FileDescription>MyApplication.exe</FileDescription>
+  <FileDescription>MyApplication.exe</FileDescription>
-      <ProductVersion>
+  <ProductVersion>
-        <Major Minimum="2" Maximum="2" />
+    <Major Minimum="2" Maximum="2" />
-        <Minor Minimum="0" Maximum="0" />
+    <Minor Minimum="0" Maximum="0" />
-        <Build Minimum="0" Maximum="0" />
+    <Build Minimum="0" Maximum="0" />
-        <Patch Minimum="5" Maximum="5" />
+    <Patch Minimum="5" Maximum="5" />
-      </ProductVersion>
+  </ProductVersion>
-      <FileVersion>
+  <FileVersion>
-        <Major Minimum="2" Maximum="2" />
+    <Major Minimum="2" Maximum="2" />
-        <Minor Minimum="0" Maximum="0" />
+    <Minor Minimum="0" Maximum="0" />
-        <Build Minimum="0" Maximum="0" />
+    <Build Minimum="0" Maximum="0" />
-        <Patch Minimum="5" Maximum="5" />
+    <Patch Minimum="5" Maximum="5" />
-      </FileVersion>
+  </FileVersion>
-    </Process>
+</Process>
 ```
 
 ### Filename
@@ -1291,14 +1290,14 @@ UE-V does not support ARM processors in this version.
 
 ProductName is an optional element used to identify a product for administrative purposes or reporting. ProductName differs from Filename in that there are no regular expression restrictions on its value. This allows for more easily understood descriptions of a process where the executable name may not be obvious. For example:
 
-``` syntax
+```xml
-    <Process>
+<Process>
-      <Filename>MyApplication.exe</Filename>
+  <Filename>MyApplication.exe</Filename>
-      <ProductName>My Application 6.x by Contoso.com</ProductName>
+  <ProductName>My Application 6.x by Contoso.com</ProductName>
-      <ProductVersion>
+  <ProductVersion>
-        <Major Minimum="6" Maximum="6" />
+    <Major Minimum="6" Maximum="6" />
-      </ProductVersion>
+  </ProductVersion>
-    </Process>
+</Process>
 ```
 
 ### FileDescription
@@ -1311,23 +1310,22 @@ FileDescription is an optional tag that allows for an administrative description
 
 For example, in a suited application, it might be useful to provide reminders about the function of two executables (MyApplication.exe and MyApplicationHelper.exe), as shown here:
 
-``` syntax
+```xml
 <Processes>
-
+  <Process>
-   <Process>
+    <Filename>MyApplication.exe</Filename>
-      <Filename>MyApplication.exe</Filename>
+    <FileDescription>My Application Main Engine</ FileDescription>
-      <FileDescription>My Application Main Engine</ FileDescription>
+    <ProductVersion>
-      <ProductVersion>
+      <Major Minimum="6" Maximum="6" />
-        <Major Minimum="6" Maximum="6" />
+    </ProductVersion>
-      </ProductVersion>
+  </Process>
-    </Process>
+  <Process>
-    <Process>
+    <Filename>MyApplicationHelper.exe</Filename>
-      <Filename>MyApplicationHelper.exe</Filename>
+    <FileDescription>My Application Background Process Executable</FileDescription>
-      <FileDescription>My Application Background Process Executable</FileDescription>
+    <ProductVersion>
-      <ProductVersion>
+      <Major Minimum="6" Maximum="6" />
-        <Major Minimum="6" Maximum="6" />
+    </ProductVersion>
-      </ProductVersion>
+  </Process>
-    </Process>
 </Processes>
 ```
 
@@ -1345,44 +1343,44 @@ The product and file version elements may be left unspecified. Doing so makes th
 
 Product version: 1.0 specified in the UE-V Generator produces the following XML:
 
-``` syntax
+```xml
-      <ProductVersion>
+<ProductVersion>
-        <Major Minimum="1" Maximum="1" />
+  <Major Minimum="1" Maximum="1" />
-        <Minor Minimum="0" Maximum="0" />
+  <Minor Minimum="0" Maximum="0" />
-      </ProductVersion>
+</ProductVersion>
 ```
 
 **Example 2:**
 
 File version: 5.0.2.1000 specified in the UE-V Generator produces the following XML:
 
-``` syntax
+```xml
-      <FileVersion>
+<FileVersion>
-        <Major Minimum="5" Maximum="5" />
+  <Major Minimum="5" Maximum="5" />
-        <Minor Minimum="0" Maximum="0" />
+  <Minor Minimum="0" Maximum="0" />
-        <Build Minimum="2" Maximum="2" />
+  <Build Minimum="2" Maximum="2" />
-        <Patch Minimum="1000" Maximum="1000" />
+  <Patch Minimum="1000" Maximum="1000" />
-      </FileVersion>
+</FileVersion>
 ```
 
 **Incorrect Example 1 – incomplete range:**
 
 Only the Minimum attribute is present. Maximum must be included in a range as well.
 
-``` syntax
+```xml
-      <ProductVersion>
+<ProductVersion>
-        <Major Minimum="2" />
+  <Major Minimum="2" />
-      </ProductVersion>
+</ProductVersion>
 ```
 
 **Incorrect Example 2 – Minor specified without Major element:**
 
 Only the Minor element is present. Major must be included as well.
 
-``` syntax
+```xml
-      <ProductVersion>
+<ProductVersion>
-        <Minor Minimum="0" Maximum="0" />
+  <Minor Minimum="0" Maximum="0" />
-      </ProductVersion>
+</ProductVersion>
 ```
 
 ### FileVersion
@@ -1399,19 +1397,19 @@ Including a FileVersion element for an application allows for more granular fine
 
 The child elements and syntax rules for FileVersion are identical to those of ProductVersion.
 
-``` syntax
+```xml
-      <Process>
+<Process>
-        <Filename>MSACCESS.EXE</Filename>
+  <Filename>MSACCESS.EXE</Filename>
-        <Architecture>Win32</Architecture>
+  <Architecture>Win32</Architecture>
-        <ProductVersion>
+  <ProductVersion>
-          <Major Minimum="14" Maximum="14" />
+    <Major Minimum="14" Maximum="14" />
-          <Minor Minimum="0" Maximum="0" />
+    <Minor Minimum="0" Maximum="0" />
-        </ProductVersion>
+  </ProductVersion>
-        <FileVersion>
+  <FileVersion>
-          <Major Minimum="14" Maximum="14" />
+    <Major Minimum="14" Maximum="14" />
-          <Minor Minimum="0" Maximum="0" />
+    <Minor Minimum="0" Maximum="0" />
-        </FileVersion>
+  </FileVersion>
-      </Process>
+</Process>
 ```
 
 ### <a href="" id="application"></a>Application Element

store-for-business/acquire-apps-microsoft-store-for-business.md

@@ -61,13 +61,13 @@ People in your org can request license for apps that they need, or that others n
 
 ## Acquire apps
 **To acquire an app**  
-1.	Sign in to http://businessstore.microsoft.com
+1. Sign in to http://businessstore.microsoft.com
-2.	Select **Shop for my group**, or use Search to find an app. 
+2. Select **Shop for my group**, or use Search to find an app. 
-3.	Select the app you want to purchase. 
+3. Select the app you want to purchase. 
-4.	On the product description page, choose your license type - either online or offline. 
+4. On the product description page, choose your license type - either online or offline. 
 5.  Free apps will be added to **Products & services**. For apps with a price, you can set the quantity you want to buy. Type the quantity and select **Next**.
-6.	If you don’t have a payment method saved in **Billing & payments**, we will prompt you for one.
+6. If you don’t have a payment method saved in **Billing & payments**, we will prompt you for one.
-7.	Add your credit card or debit card info, and select **Next**. Your card info is saved as a payment option on **Billing & payments - Payment methods**.
+7. Add your credit card or debit card info, and select **Next**. Your card info is saved as a payment option on **Billing & payments - Payment methods**.
 
 You’ll also need to have your business address saved on **My organization - Profile**. The address is used to generate tax rates. For more information on taxes for apps, see [organization tax information](https://docs.microsoft.com/microsoft-store/update-microsoft-store-for-business-account-settings#organization-tax-information). 
 

store-for-business/app-inventory-management-microsoft-store-for-business.md

@@ -75,10 +75,10 @@ For online-licensed apps, you can assign apps directly to people in your organiz
 
 **To assign an app to an employee**
 
-1.	Sign in to the [Microsoft Store for Business](https://businessstore.microsoft.com) or [Microsoft Store for Education](https://businessstore.microsoft.com).
+1. Sign in to the [Microsoft Store for Business](https://businessstore.microsoft.com) or [Microsoft Store for Education](https://businessstore.microsoft.com).
-2.	Click **Manage**, and then choose **Inventory**.
+2. Click **Manage**, and then choose **Inventory**.
-3.	Find an app, click the ellipses, and then choose **Assign to people**.
+3. Find an app, click the ellipses, and then choose **Assign to people**.
-4.	Type the email address for the employee that you're assigning the app to, and click **Confirm**.
+4. Type the email address for the employee that you're assigning the app to, and click **Confirm**.
 
 Employees will receive an email with a link that will install the app on their device. Click the link to start the Microsoft Store app, and then click **Install**. Also, in the Microsoft Store app, they can find the app under **My Library**.
 
@@ -103,9 +103,9 @@ Employees can claim apps that admins added to the private store by doing the fol
 ### Get and remove private store apps
 **To claim an app from the private store**
 
-1.	Sign in to your computer with your Azure Active Directory (AD) credentials, and start the Microsoft Store app.
+1. Sign in to your computer with your Azure Active Directory (AD) credentials, and start the Microsoft Store app.
-2.	Click the private store tab.
+2. Click the private store tab.
-3.	Click the app you want to install, and then click **Install**.
+3. Click the app you want to install, and then click **Install**.
 
 Another way to distribute apps is by assigning them to people in your organization.
 

store-for-business/distribute-apps-from-your-private-store.md

@@ -43,13 +43,11 @@ Microsoft Store adds the app to **Products and services**. Click **Manage**, **A
 
     <!--- ![Image showing Manage menu in Microsoft Store for Business.](images/wsfb-manageinventory.png) -->
 
-3.  Use **Refine results** to search for online-licensed apps under **License type**.
+3.  Click on the application to open the application settings, then select **Private store availability**.
-4.  From the list of online-licensed apps, click the ellipses for the app you want, and then choose **Add to private store**.
+4.  Select **Everyone** to make application available for all people in your organization.
 
     <!--- ![Image showing options from Action for each app in Inventory.](images/wsfb-inventoryaddprivatestore.png) -->
 
-The value under **Private store** for the app will change to pending. It will take approximately thirty-six hours before the app is available in the private store.
-
 >[!Note]
  > If you are working with a new Line-of-Business (LOB) app, you have to wait for the app to be available in **Products & services** before adding it to your private store. For more information, see [Working with line-of-business apps](working-with-line-of-business-apps.md). 
 

store-for-business/manage-orders-microsoft-store-for-business.md

@@ -55,10 +55,10 @@ Refunds work a little differently for free apps, and apps that have a price. In
 
 Reclaim licenses, and then request a refund. If you haven't assigned licenses, start on step 5.
 1.  Sign in to the [Microsoft Store for Business](https://businessstore.microsoft.com) or [Microsoft Store for Education](https://educationstore.microsoft.com).
-2.	Click **Manage**, and then choose **Apps & software**.
+2. Click **Manage**, and then choose **Apps & software**.
-3.	Find the app you want to refund, click the ellipses under **Actions**, and then choose **View license details**.
+3. Find the app you want to refund, click the ellipses under **Actions**, and then choose **View license details**.
 4.  Select the people who you want to reclaim license from, click the ellipses under **Actions**, and then choose **Reclaim licenses**.
-5.	Click **Order history**, click the order you want to refund, and click **Refund order**.
+5. Click **Order history**, click the order you want to refund, and click **Refund order**.
 
 For free apps, the app will be removed from your inventory in **Apps & software**.
 

store-for-business/update-microsoft-store-for-business-account-settings.md

@@ -94,7 +94,7 @@ If you qualify for tax-exempt status in your market, start a service request to
 
 **To start a service request**
 1.  Sign in to the [Microsoft Store for Business](https://businessstore.microsoft.com).
-2.	Select **Manage**, click **Support**, and then under **Store settings & configuration** select **Create technical support ticket**.
+2. Select **Manage**, click **Support**, and then under **Store settings & configuration** select **Create technical support ticket**.
 
 You’ll need this documentation:
 

windows/application-management/app-v/appv-install-the-appv-databases-and-convert-the-associated-security-identifiers-with-powershell.md

@@ -42,7 +42,7 @@ Before attempting this procedure, you should read and understand the information
 
 2.  To open a Windows PowerShell console, click **Start** and type **PowerShell**. Right-click **Windows PowerShell** and select **Run as Administrator**.
 
-    ``` syntax
+    ```powershell
     <#
     .SYNOPSIS
     This Windows PowerShell script will take an array of account names and try to convert each of them to the corresponding SID in standard and hexadecimal formats.
@@ -59,9 +59,6 @@ Before attempting this procedure, you should read and understand the information
     .\ConvertToSID.ps1 $accountsArray | Write-Output -FilePath .\SIDs.txt -Width 200
     #>
 
-    []()  
-
-    []()  
     function ConvertSIDToHexFormat
     {
        param([System.Security.Principal.SecurityIdentifier]$sidToConvert)

windows/application-management/svchost-service-refactoring.md

@@ -40,8 +40,8 @@ Benefits of this design change include:
 >**Try This**
 >
 > To see the refactoring behavior, create a Windows 10 version 1703 VM and configure the memory settings as follows:
-> 1.	To see grouped processes, set the RAM to 3484 MB or less. Restart the VM and then open Task Manager.
+> 1. To see grouped processes, set the RAM to 3484 MB or less. Restart the VM and then open Task Manager.
-> 2.	To see separated processes, set the RAM to 3486 MB or greater. Restart the VM and then open Task Manager.
+> 2. To see separated processes, set the RAM to 3486 MB or greater. Restart the VM and then open Task Manager.
 
 
 Refactoring also makes it easier to view running processes in Task Manager. You can look at Task Manager and know exactly which service is using what resources, without having to expand many separate host groups.

windows/client-management/mdm/activesync-csp.md

@@ -60,13 +60,13 @@ When managing over OMA DM, make sure to always use a unique GUID. Provisioning w
 
 Braces { } are required around the GUID. In OMA Client Provisioning, you can type the braces. For example:
 
-``` syntax
+```xml
 <characteristic type="{C556E16F-56C4-4EDB-9C64-D9469EE1FBE0}"/>
 ```
 
 For OMA DM, you must use the ASCII values of %7B and %7D for the opening and closing braces, respectively. For example, if the GUID is "C556E16F-56C4-4EDB-9C64-D9469EE1FBE0", type:
 
-``` syntax
+```xml
 <Target>
    <LocURI>
       ./Vendor/MSFT/ActiveSync/Accounts/%7BC556E16F-56C4-4EDB-9C64-D9469EE1FBE0%7D

windows/client-management/mdm/assignedaccess-csp.md

@@ -14,6 +14,7 @@ ms.date: 09/18/2018
 
 # AssignedAccess CSP
 
+**Some information relates to prereleased product which may be substantially modified before it's commercially released. Microsoft makes no warranties, express or implied, with respect to the information provided here.**
 
 The AssignedAccess configuration service provider (CSP) is used to set the device to run in kiosk mode. Once the CSP has been executed, then the next user login that is associated with the kiosk mode puts the device into the kiosk mode running the application specified in the CSP configuration.
 
@@ -134,7 +135,7 @@ Additionally, the Status payload includes the following fields:
 Supported operation is Get.
 
 <a href="" id="assignedaccess-shelllauncher"></a>**./Device/Vendor/MSFT/AssignedAccess/ShellLauncher**
-Added in Windows 10,version 1803. This node accepts a ShellLauncherConfiguration xml as input. Click [link](#shelllauncherconfiguration-xsd) to see the schema. Shell Launcher V2 is introduced in Windows 10, version 1903 to support both UWP and Win32 apps as the custom shell. For more information, see [Shell Launcher](https://docs.microsoft.com/en-us/windows/configuration/kiosk-shelllauncher).
+Added in Windows 10,version 1803. This node accepts a ShellLauncherConfiguration xml as input. Click [link](#shelllauncherconfiguration-xsd) to see the schema. Shell Launcher V2 is introduced in Windows 10, version 1903 to support both UWP and Win32 apps as the custom shell. For more information, see [Shell Launcher](https://docs.microsoft.com/windows/configuration/kiosk-shelllauncher).
 
 > [!Note]
 > You cannot set both ShellLauncher and KioskModeApp at the same time on the device.
@@ -246,6 +247,8 @@ KioskModeApp Replace
 
 ## AssignedAccessConfiguration XSD
 
+Below schema is for AssignedAccess Configuration up to Windows 10 1803 release.
+
 ```xml
 <?xml version="1.0" encoding="utf-8"?>
 <xs:schema
@@ -253,9 +256,14 @@ KioskModeApp Replace
     xmlns:xs="http://www.w3.org/2001/XMLSchema"
     xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config"
     xmlns:default="http://schemas.microsoft.com/AssignedAccess/2017/config"
+    xmlns:rs5="http://schemas.microsoft.com/AssignedAccess/201810/config"
+    xmlns:v3="http://schemas.microsoft.com/AssignedAccess/2020/config"
     targetNamespace="http://schemas.microsoft.com/AssignedAccess/2017/config"
     >
 
+    <xs:import namespace="http://schemas.microsoft.com/AssignedAccess/201810/config"/>
+    <xs:import namespace="http://schemas.microsoft.com/AssignedAccess/2020/config"/>
+
     <xs:complexType name="profile_list_t">
         <xs:sequence minOccurs="1" >
             <xs:element name="Profile" type="profile_t" minOccurs="1" maxOccurs="unbounded"/>
@@ -270,6 +278,7 @@ KioskModeApp Replace
         <xs:choice>
             <xs:sequence minOccurs="1" maxOccurs="1">
                 <xs:element name="AllAppsList" type="allappslist_t" minOccurs="1" maxOccurs="1"/>
+                <xs:element ref="rs5:FileExplorerNamespaceRestrictions" minOccurs="0" maxOccurs="1"/>
                 <xs:element name="StartLayout" type="xs:string" minOccurs="1" maxOccurs="1"/>
                 <xs:element name="Taskbar" type="taskbar_t" minOccurs="1" maxOccurs="1"/>
             </xs:sequence>
@@ -286,6 +295,10 @@ KioskModeApp Replace
                     <xs:selector xpath="default:App"/>
                     <xs:field xpath="@AppUserModelId|@DesktopAppPath"/>
                 </xs:unique>
+                <xs:unique name="OnlyOneAppCanHaveAutoLaunch">
+                    <xs:selector xpath="default:App"/>
+                    <xs:field xpath="@rs5:AutoLaunch"/>
+                </xs:unique>
             </xs:element>
         </xs:sequence>
     </xs:complexType>
@@ -304,7 +317,13 @@ KioskModeApp Replace
     <xs:complexType name="app_t">
         <xs:attribute name="AppUserModelId" type="xs:string"/>
         <xs:attribute name="DesktopAppPath" type="xs:string"/>
+        <xs:attributeGroup ref="autoLaunch_attributeGroup"/>
     </xs:complexType>
+    
+    <xs:attributeGroup name="autoLaunch_attributeGroup">
+        <xs:attribute ref="rs5:AutoLaunch"/>
+        <xs:attribute ref="rs5:AutoLaunchArguments" use="optional"/>
+    </xs:attributeGroup>
 
     <xs:complexType name="taskbar_t">
         <xs:attribute name="ShowTaskbar" type="xs:boolean" use="required"/>
@@ -322,7 +341,8 @@ KioskModeApp Replace
 
     <xs:complexType name="config_list_t">
         <xs:sequence minOccurs="1" >
-            <xs:element name="Config" type="config_t" minOccurs="1" maxOccurs="unbounded"/>
+            <xs:element ref="v3:GlobalProfile" minOccurs="0" maxOccurs="1"/>
+            <xs:element name="Config" type="config_t" minOccurs="0" maxOccurs="unbounded"/>
         </xs:sequence>
     </xs:complexType>
 
@@ -340,6 +360,7 @@ KioskModeApp Replace
 
     <xs:complexType name="autologon_account_t">
         <xs:attribute name="HiddenId" type="guid_t" fixed="{74331115-F68A-4DF9-8D2C-52BA2CE2ADB1}"/>
+        <xs:attribute ref="rs5:DisplayName" use="optional" />
     </xs:complexType>
 
     <xs:complexType name="group_t">
@@ -365,6 +386,22 @@ KioskModeApp Replace
         </xs:restriction>
     </xs:simpleType>
 
+    <xs:complexType name="fileExplorerNamespaceRestrictions_t">
+        <xs:sequence minOccurs="1">
+            <xs:element name="AllowedNamespace" type="allowedFileExplorerNamespace_t"/>
+        </xs:sequence>
+    </xs:complexType>
+
+    <xs:complexType name="allowedFileExplorerNamespace_t">
+        <xs:attribute name="Name" type="allowedFileExplorerNamespaceValues_t"/>
+    </xs:complexType>
+
+    <xs:simpleType name="allowedFileExplorerNamespaceValues_t">
+        <xs:restriction base="xs:string">
+            <xs:enumeration value="Downloads"/>
+        </xs:restriction>
+    </xs:simpleType>
+
     <!--below is the definition of the config xml content-->
     <xs:element name="AssignedAccessConfiguration">
         <xs:complexType>
@@ -385,7 +422,94 @@ KioskModeApp Replace
         </xs:complexType>
     </xs:element>
 </xs:schema>
+```
 
+Here is the schema for new features introduced in Windows 10 1809 release
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<xs:schema
+    elementFormDefault="qualified"
+    xmlns:xs="http://www.w3.org/2001/XMLSchema"
+    xmlns="http://schemas.microsoft.com/AssignedAccess/201810/config"
+    xmlns:default="http://schemas.microsoft.com/AssignedAccess/201810/config"
+    xmlns:v3="http://schemas.microsoft.com/AssignedAccess/2020/config"
+    targetNamespace="http://schemas.microsoft.com/AssignedAccess/201810/config"
+    >
+
+    <xs:import namespace="http://schemas.microsoft.com/AssignedAccess/2020/config"/>
+
+    <xs:complexType name="fileExplorerNamespaceRestrictions_t">
+        <xs:choice>
+            <xs:sequence minOccurs="0">
+                <xs:element name="AllowedNamespace" type="allowedFileExplorerNamespace_t" minOccurs="0"/>
+                <xs:element ref="v3:AllowRemovableDrives" minOccurs="0" maxOccurs="1"/>
+            </xs:sequence>
+            <xs:element ref="v3:NoRestriction" minOccurs="0" maxOccurs="1" />
+        </xs:choice>
+    </xs:complexType>
+
+    <xs:complexType name="allowedFileExplorerNamespace_t">
+        <xs:attribute name="Name" type="allowedFileExplorerNamespaceValues_t" use="required"/>
+    </xs:complexType>
+
+    <xs:simpleType name="allowedFileExplorerNamespaceValues_t">
+        <xs:restriction base="xs:string">
+            <xs:enumeration value="Downloads"/>
+        </xs:restriction>
+    </xs:simpleType>
+
+    <xs:element name="FileExplorerNamespaceRestrictions" type="fileExplorerNamespaceRestrictions_t" />
+
+    <xs:attribute name="AutoLaunch" type="xs:boolean"/>
+
+    <xs:attribute name="AutoLaunchArguments" type="xs:string"/>
+
+    <xs:attribute name="DisplayName" type="xs:string"/>
+
+</xs:schema>
+```
+
+Schema for Windows 10 prerelease
+```xml
+<?xml version="1.0" encoding="utf-8"?>
+<xs:schema
+    elementFormDefault="qualified"
+    xmlns:xs="http://www.w3.org/2001/XMLSchema"
+    xmlns="http://schemas.microsoft.com/AssignedAccess/2020/config"
+    xmlns:default="http://schemas.microsoft.com/AssignedAccess/2020/config"
+    xmlns:vc="http://www.w3.org/2007/XMLSchema-versioning"
+    vc:minVersion="1.1"
+    targetNamespace="http://schemas.microsoft.com/AssignedAccess/2020/config"
+    >
+
+    <xs:simpleType name="guid_t">
+        <xs:restriction base="xs:string">
+            <xs:pattern value="\{[0-9a-fA-F]{8}\-([0-9a-fA-F]{4}\-){3}[0-9a-fA-F]{12}\}"/>
+        </xs:restriction>
+    </xs:simpleType>
+
+    <xs:complexType name="globalProfile_t">
+        <xs:attribute name="Id" type="guid_t" />
+    </xs:complexType>
+  
+    <xs:element name="AllowRemovableDrives"/>
+    <xs:element name="NoRestriction" />
+    <xs:element name="GlobalProfile" type="globalProfile_t" />
+
+</xs:schema>
+```
+
+To authorize a compatible configuration XML that includes 1809 or prerelease elements and attributes, always include the namespace of these add-on schemas, and decorate the attributes and elements accordingly with the namespace alias. e.g. to configure auto-launch feature which is added in 1809 release, use below sample, notice an alias r1809 is given to the 201810 namespace for 1809 release, and the alias is tagged on AutoLaunch and AutoLaunchArguments inline.
+```xml
+<AssignedAccessConfiguration
+    xmlns="http://schemas.microsoft.com/AssignedAccess/2017/config"
+    xmlns:r1809="http://schemas.microsoft.com/AssignedAccess/201810/config"
+>
+    <Profiles>
+        <Profile Id="{9A2A490F-10F6-4764-974A-43B19E722C23}">
+            <AllAppsList>
+                <AllowedApps>
+                  <App DesktopAppPath="%SystemRoot%\system32\notepad.exe" r1809:AutoLaunch="true" r1809:AutoLaunchArguments="1.txt"/>
 ```
 
 ## Example AssignedAccessConfiguration XML
@@ -796,7 +920,7 @@ StatusConfiguration Get
 
 StatusConfiguration Replace On
 
-```syntax
+```xml
 <SyncML xmlns='SYNCML:SYNCML1.2'>
   <SyncBody>
     <Replace>
@@ -1219,7 +1343,7 @@ ShellLauncherConfiguration Get
 
 ## AssignedAccessAlert XSD
 
-```syntax
+```xml
 <?xml version="1.0" encoding="utf-8"?>
 <xs:schema
     elementFormDefault="qualified"

windows/client-management/mdm/certificatestore-csp.md

@@ -360,7 +360,7 @@ Supported operations are Add, Get, and Replace.
 
 Add a root certificate to the MDM server.
 
-``` syntax
+```xml
 <Add>
    <CmdID>1</CmdID>
    <Item>
@@ -379,7 +379,7 @@ Add a root certificate to the MDM server.
 
 Get all installed client certificates.
 
-``` syntax
+```xml
 <Get>
    <CmdID>1</CmdID>
    <Item>
@@ -394,7 +394,7 @@ Get all installed client certificates.
 
 Delete a root certificate.
 
-``` syntax
+```xml
 <Delete>
    <CmdID>1</CmdID>
    <Item>
@@ -409,7 +409,7 @@ Delete a root certificate.
 
 Configure the device to enroll a client certificate through SCEP.
 
-``` syntax
+```xml
 <Atomic>
 <CmdID>100</CmdID>
 <Add>
@@ -588,7 +588,7 @@ Configure the device to enroll a client certificate through SCEP.
 
 Configure the device to automatically renew an MDM client certificate with the specified renew period and retry interval.
 
-``` syntax
+```xml
 <Atomic>
    <CmdID>1</CmdID>
      <Replace>

windows/client-management/mdm/cm-cellularentries-csp.md

@@ -198,7 +198,7 @@ The following diagram shows the CM\_CellularEntries configuration service provid
 
 To delete a connection, you must first delete any associated proxies and then delete the connection. The following example shows how to delete the proxy and then the connection.
 
-``` syntax
+```xml
 <wap-provisioningdoc>
    <characteristic type="CM_ProxyEntries">
       <nocharacteristic type="GPRS_Proxy"/>
@@ -214,7 +214,7 @@ To delete a connection, you must first delete any associated proxies and then de
 
 Configuring a GPRS connection:
 
-``` syntax
+```xml
 <wap-provisioningdoc>
    <characteristic type="CM_CellularEntries">
       <characteristic type="GPRSConn">
@@ -231,7 +231,7 @@ Configuring a GPRS connection:
 
 Configuring an LTE connection:
 
-``` syntax
+```xml
 <wap-provisioningdoc>
    <characteristic type="CM_CellularEntries">
       <characteristic type="LteConn">
@@ -250,7 +250,7 @@ Configuring an LTE connection:
 
 Configuring a CDMA connection:
 
-``` syntax
+```xml
 <wap-provisioningdoc>
    <characteristic type="CM_CellularEntries">
       <characteristic type="CDMAConn">

windows/client-management/mdm/cmpolicy-csp.md

@@ -240,7 +240,7 @@ Specifies the type of connection being referenced. The following list describes
 
 Adding an application-based mapping policy. In this example, the ConnectionId for type CMST\_CONNECTION\_NAME is set to the name of the connection (“GPRSConn1”) that is configured with the CM\_CellularEntries configuration service provider.
 
-``` syntax
+```xml
 <wap-provisioningdoc>
 
    <characteristic type="CM_CellularEntries">
@@ -285,7 +285,7 @@ Adding an application-based mapping policy. In this example, the ConnectionId fo
 
 Adding a host-based mapping policy. In this example, the ConnectionId for type CMST\_CONNECTION\_NAME is set to the name of the connection (“GPRSConn1”) that is configured with the CM\_CellularEntries configuration service provider.
 
-``` syntax
+```xml
 <wap-provisioningdoc>
 
    <characteristic type="CM_CellularEntries">
@@ -334,7 +334,7 @@ Adding a host-based mapping policy. In this example, the ConnectionId for type C
 
 Adding an application-based mapping policy:
 
-``` syntax
+```xml
 <SyncML>
     <SyncBody>
         <Atomic>
@@ -401,7 +401,7 @@ Adding an application-based mapping policy:
 
 Adding a host-based mapping policy:
 
-``` syntax
+```xml
 <SyncML>
     <SyncBody>
         <Atomic>

windows/client-management/mdm/cmpolicyenterprise-csp.md

@@ -240,7 +240,7 @@ Specifies the type of connection being referenced. The following list describes
 
 Adding an application-based mapping policy. In this example, the ConnectionId for type CMST\_CONNECTION\_NAME is set to the name of the connection (“GPRSConn1”) that is configured with the CM\_CellularEntries configuration service provider.
 
-``` syntax
+```xml
 <wap-provisioningdoc>
 
    <characteristic type="CM_CellularEntries">
@@ -285,7 +285,7 @@ Adding an application-based mapping policy. In this example, the ConnectionId fo
 
 Adding a host-based mapping policy. In this example, the ConnectionId for type CMST\_CONNECTION\_NAME is set to the name of the connection (“GPRSConn1”) that is configured with the CM\_CellularEntries configuration service provider.
 
-``` syntax
+```xml
 <wap-provisioningdoc>
 
    <characteristic type="CM_CellularEntries">
@@ -334,7 +334,7 @@ Adding a host-based mapping policy. In this example, the ConnectionId for type C
 
 Adding an application-based mapping policy:
 
-``` syntax
+```xml
 <SyncML>
     <SyncBody>
         <Atomic>
@@ -401,7 +401,7 @@ Adding an application-based mapping policy:
 
 Adding a host-based mapping policy:
 
-``` syntax
+```xml
 <SyncML>
     <SyncBody>
         <Atomic>

windows/client-management/mdm/customdeviceui-csp.md

@@ -38,7 +38,7 @@ Package Full Name of the App that needs be launched in the background. This can
 
 **Set StartupAppID**
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>      
         <Replace>
@@ -60,7 +60,7 @@ Package Full Name of the App that needs be launched in the background. This can
 
 **Get all background tasks**
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>      
         <Get>
@@ -78,7 +78,7 @@ Package Full Name of the App that needs be launched in the background. This can
 
 **Add background task**
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>      
         <Add>

windows/client-management/mdm/device-update-management.md

@@ -648,7 +648,7 @@ If a machine has Microsoft Update enabled, any Microsoft Updates in these catego
 
 Example
 
-``` syntax
+```xml
         <Replace>
             <CmdID>$CmdID$</CmdID>
             <Item>
@@ -919,7 +919,7 @@ The following screenshots of the administrator console shows the list of update
 
 Set auto update to notify and defer.
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.1">
     <SyncBody>
         <Replace xmlns="">

windows/client-management/mdm/deviceinstanceservice-csp.md

@@ -70,7 +70,7 @@ The parent node to group SIM2 specific information in case of dual SIM mode.
 
 The following sample shows how to query roaming status and phone number on the device.
 
-``` syntax
+```xml
 <Get>
       <CmdID>2</CmdID>
       <Item>
@@ -88,7 +88,7 @@ The following sample shows how to query roaming status and phone number on the d
 
 Response from the phone.
 
-``` syntax
+```xml
 <Results>
    <CmdID>3</CmdID>
    <MsgRef>1</MsgRef>

windows/client-management/mdm/devicelock-csp.md

@@ -126,7 +126,7 @@ Required. This node has the same set of policy nodes as the **ProviderID** node.
 
 Set device lock policies:
 
-``` syntax
+```xml
 <Atomic>
    <CmdID>13</CmdID>
    <Add>

windows/client-management/mdm/diagnosticlog-csp.md

@@ -420,7 +420,7 @@ Default value is 0 meaning no keyword.
 
 Get provider **Keywords**
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
     <Get>
@@ -440,7 +440,7 @@ Get provider **Keywords**
 
 Set provider **Keywords**
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
     <Replace>

windows/client-management/mdm/disconnecting-from-mdm-unenrollment.md

@@ -105,7 +105,7 @@ After the previous package is sent, the unenrollment process begins.
 
 When the server initiates disconnection, all undergoing sessions for the enrollment ID are aborted immediately to avoid deadlocks. The server will not get a response for the unenrollment, instead a generic alert notification is sent with messageid=1.
 
-``` syntax
+```xml
 <Alert>
       <CmdID>4</CmdID>
       <Data>1226</Data>

windows/client-management/mdm/dmclient-csp.md

@@ -70,7 +70,7 @@ Supported operation is Get.
 
 The following is a Get command example.
 
-``` syntax
+```xml
 <Get>
    <CmdID>12</CmdID>
    <Item>
@@ -173,7 +173,7 @@ To work around the timeout, you can use this setting to keep the session alive b
 
 Here is an example of DM message sent by the device when it is in pending state:
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncHdr>
 <VerDTD>1.2</VerDTD>
@@ -229,7 +229,7 @@ Added in Windows 10, version 1607. The list of management server URLs in the fo
 
  
 
-``` syntax
+```xml
    <Replace>
        <CmdID>101</CmdID>
        <Item>
@@ -770,7 +770,7 @@ Note that &lt;LocURI&gt;./Vendor/MSFT/DMClient/Unenroll&lt;/LocURI&gt; is suppor
 
 The following SyncML shows how to remotely unenroll the device. Note that this command should be inserted in the general DM packages sent from the server to the device.
 
-``` syntax
+```xml
     <Exec>
        <CmdID>2</CmdID>
        <Item>

windows/client-management/mdm/dynamicmanagement-csp.md

@@ -29,7 +29,7 @@ The following diagram shows the DynamicManagement configuration service provider
 <p style="margin-left: 20px">Default value is False. Supported operations are Get and Replace.</p>
 <p style="margin-left: 20px">Example to turn on NotificationsEnabled:</p>
 
-``` syntax
+```xml
 <Replace>
       <CmdID>100</CmdID>
       <Item>
@@ -84,7 +84,7 @@ The following diagram shows the DynamicManagement configuration service provider
 
 Disable Cortana based on Geo location and time, From 9am-5pm, when in the 100 meters radius of the specified latitude/longitude
 
-``` syntax
+```xml
     <Replace>
       <CmdID>200</CmdID>
       <Item>
@@ -138,7 +138,7 @@ Disable Cortana based on Geo location and time, From 9am-5pm, when in the 100 me
 
 Disable camera using network trigger with time trigger, from 9-5, when ip4 gateway is 192.168.0.1
 
-``` syntax
+```xml
 <Replace>
       <CmdID>300</CmdID>
       <Item>
@@ -193,7 +193,7 @@ Disable camera using network trigger with time trigger, from 9-5, when ip4 gatew
 
 Delete a context
 
-``` syntax
+```xml
 <Delete>
       <CmdID>400</CmdID>
       <Item>
@@ -206,7 +206,7 @@ Delete a context
 
 Get ContextStatus and SignalDefinition from a specific context
 
-``` syntax
+```xml
 <Get>
       <CmdID>400</CmdID>
       <Item>

windows/client-management/mdm/eap-configuration.md

@@ -142,11 +142,11 @@ The following list describes the prerequisites for a certificate to be used with
 -   The certificate must have at least one of the following EKU (Extended Key Usage) properties:
 
     -   Client Authentication
-    -   As defined by RFC 5280, this is a well-defined OID with Value 1.3.6.1.5.5.7.3.2
+        -   As defined by RFC 5280, this is a well-defined OID with Value 1.3.6.1.5.5.7.3.2
     -   Any Purpose
-    -   An EKU Defined and published by Microsoft, is a well-defined OID with value 1.3.6.1.4.1.311.10.12.1. The inclusion of this OID implies that the certificate can be used for any purpose. The advantage of this EKU over the All Purpose EKU is that additional non-critical or custom EKUs can still be added to the certificate for effective filtering.
+        -   An EKU Defined and published by Microsoft, is a well-defined OID with value 1.3.6.1.4.1.311.10.12.1. The inclusion of this OID implies that the certificate can be used for any purpose. The advantage of this EKU over the All Purpose EKU is that additional non-critical or custom EKUs can still be added to the certificate for effective filtering.
     -   All Purpose
-    -   As defined by RFC 5280, If a CA includes extended key usages to satisfy some application needs, but does not want to restrict usage of the key, the CA can add an Extended Key Usage Value of 0. A certificate with such an EKU can be used for all purposes.
+        -   As defined by RFC 5280, If a CA includes extended key usages to satisfy some application needs, but does not want to restrict usage of the key, the CA can add an Extended Key Usage Value of 0. A certificate with such an EKU can be used for all purposes.
 -   The user or the computer certificate on the client chains to a trusted root CA
 -   The user or the computer certificate does not fail any one of the checks that are performed by the CryptoAPI certificate store, and the certificate passes requirements in the remote access policy.
 -   The user or the computer certificate does not fail any one of the certificate object identifier checks that are specified in the Internet Authentication Service (IAS)/Radius Server.

windows/client-management/mdm/enable-admx-backed-policies-in-mdm.md

@@ -64,7 +64,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
 > [!NOTE]
 > The \<Data> payload must be XML encoded. To avoid encoding, you can use CData if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect). If you are using Intune, select String as the data type.
      
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
     <Replace>
@@ -114,7 +114,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
     
       Here is the snippet from appv.admx:
 
-      ``` syntax
+      ```xml
       <!--  Publishing Server 2  -->
       <policy name="Publishing_Server2_Policy" class="Machine" displayName="$(string.PublishingServer2)" 
           explainText="$(string.Publishing_Server_Help)" presentation="$(presentation.Publishing_Server2)" 
@@ -206,7 +206,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
 
       Here is the example XML for Publishing_Server2_Policy :
         
-      ``` syntax
+      ```xml
       <data id="Publishing_Server2_Name_Prompt" value="Name"/>
       <data id="Publishing_Server_URL_Prompt" value="http://someuri"/>
       <data id="Global_Publishing_Refresh_Options" value="1"/>
@@ -226,7 +226,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
 > [!NOTE]
 > The \<Data> payload must be XML encoded. To avoid encoding, you can use CData if your MDM supports it. For more information, see [CDATA Sections](http://www.w3.org/TR/REC-xml/#sec-cdata-sect). If you are using Intune, select String as the data type.
     
-    ``` syntax
+    ```xml
     <?xml version="1.0" encoding="utf-8"?>
        <SyncML xmlns="SYNCML:SYNCML1.2">
          <SyncBody>
@@ -264,7 +264,7 @@ See [Support Tip: Ingesting Office ADMX-backed policies using Microsoft Intune](
 
 The \<Data> payload is \<disabled/>. Here is an example to disable AppVirtualization/PublishingAllowServer2.
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
     <Replace>

windows/client-management/mdm/enable-offline-updates-for-windows-embedded-8-1-handheld-devices-to-windows-10.md

@@ -275,7 +275,7 @@ After the installation of updates is completed, the IT Admin can use the DURepor
 <a href="" id="example-script"></a>
 ## Example PowerShell script
 
-``` syntax
+```powershell
 param (
 # [Parameter (Mandatory=$true, HelpMessage="Input File")]
         [String]$inputFile,

windows/client-management/mdm/enroll-a-windows-10-device-automatically-using-group-policy.md

@@ -50,7 +50,7 @@ Requirements:
 - Enterprise has MDM service already configured 
 - Enterprise AD must be registered with Azure AD
 
-1.	Run GPEdit.msc
+1. Run GPEdit.msc
 
     Click Start, then in the text box type gpedit. 
 
@@ -62,11 +62,11 @@ Requirements:
 
     ![MDM policies](images/autoenrollment-mdm-policies.png)
 
-4.	Double-click **Auto MDM Enrollment with AAD Token**.
+4. Double-click **Auto MDM Enrollment with AAD Token**.
 
     ![MDM autoenrollment policy](images/autoenrollment-policy.png)
 
-5.	Click **Enable**, then click **OK**.
+5. Click **Enable**, then click **OK**.
 
      A task is created and scheduled to run every 5 minutes for the duration of 1 day. The task is called " Schedule created by enrollment client for automatically enrolling in MDM from AAD." 
 
@@ -76,9 +76,9 @@ Requirements:
 
      ![Two-factor authentication notification](images/autoenrollment-2-factor-auth.png)
 
-6.	To verify successful enrollment to MDM , click **Start > Settings > Accounts > Access work or school**, then select your domain account.
+6. To verify successful enrollment to MDM , click **Start > Settings > Accounts > Access work or school**, then select your domain account.
 
-7.	Click **Info** to see the MDM enrollment information.
+7. Click **Info** to see the MDM enrollment information.
 
     ![Work School Settings](images/autoenrollment-settings-work-school.png)
 
@@ -91,9 +91,9 @@ Requirements:
 
    ![Task Scheduler search result](images/autoenrollment-task-schedulerapp.png)
 
-2.	Under **Best match**, click **Task Scheduler** to launch it.
+2. Under **Best match**, click **Task Scheduler** to launch it.
 
-3.	In **Task Scheduler Library**, open **Microsoft > Windows** , then click **EnterpriseMgmt**. 
+3. In **Task Scheduler Library**, open **Microsoft > Windows** , then click **EnterpriseMgmt**. 
 
     ![Auto-enrollment scheduled task](images/autoenrollment-scheduled-task.png)
 
@@ -122,11 +122,11 @@ Requirements:
 >   5. Restart the Primary Domain Controller for the policy to be available.
 >   This procedure will work for any future version as well.
 
-1.	Create a Group Policy Object (GPO) and enable the Group Policy **Computer Configuration** > **Policies** > **Administrative Templates** > **Windows Components** > **MDM** > **Enable automatic MDM enrollment using default Azure AD credentials**.
+1. Create a Group Policy Object (GPO) and enable the Group Policy **Computer Configuration** > **Policies** > **Administrative Templates** > **Windows Components** > **MDM** > **Enable automatic MDM enrollment using default Azure AD credentials**.
-2.	Create a Security Group for the PCs.
+2. Create a Security Group for the PCs.
-3.	Link the GPO.
+3. Link the GPO.
-4.	Filter using Security Groups.
+4. Filter using Security Groups.
-5.	Enforce a GPO link.
+5. Enforce a GPO link.
 
 > [!NOTE]
 > Version 1903 (March 2019) is actually on the Insider program and doesn't yet contain a downloadable version of Templates (version 1903).

windows/client-management/mdm/enterprise-app-management.md

@@ -78,7 +78,7 @@ Note that performing a full inventory of a device can be resource intensive on t
 
 Here is an example of a query for all apps on the device.
 
-``` syntax
+```xml
 <!-- Get all apps under AppManagement -->
 <Get>
    <CmdID>1</CmdID>
@@ -92,7 +92,7 @@ Here is an example of a query for all apps on the device.
 
 Here is an example of a query for a specific app for a user.
 
-``` syntax
+```xml
 <!-- Get all information of a specific app for a user -->
 <Get>
    <CmdID>1</CmdID>
@@ -121,7 +121,7 @@ For detailed descriptions of each node, see [EnterpriseModernAppManagement CSP](
 
 Here is an example of a query for all app licenses on a device.
 
-``` syntax
+```xml
 <!-- Get all app licenses for the device -->
 <Get>
    <CmdID>1</CmdID>
@@ -135,7 +135,7 @@ Here is an example of a query for all app licenses on a device.
 
 Here is an example of a query for all app licenses for a user.
 
-``` syntax
+```xml
 <!-- Get a specific app license for a user -->
 <Get>
    <CmdID>1</CmdID>
@@ -161,7 +161,7 @@ For more information about the AllowAllTrustedApps policy, see [Policy CSP](poli
 
 Here are some examples.
 
-``` syntax
+```xml
 <!-- Get policy (Default)-->
 <Get>
   <CmdID>1</CmdID>
@@ -199,7 +199,7 @@ For more information about the AllowDeveloperUnlock policy, see [Policy CSP](pol
 
 Here is an example.
 
-``` syntax
+```xml
 <!-- Get policy (Default)-->
 <Get>
   <CmdID>1</CmdID>
@@ -244,7 +244,7 @@ Here are the requirements for this scenario:
 
 Here are some examples.
 
-``` syntax
+```xml
 <Exec>
    <CmdID>1</CmdID>
           <Item>
@@ -281,7 +281,7 @@ In the SyncML, you need to specify the following information in the Exec command
 
 Here is an example of an offline license installation.
 
-``` syntax
+```xml
 <Exec>
    <CmdID>1</CmdID>
    <Item>
@@ -315,7 +315,7 @@ The Add command for the package family name is required to ensure proper removal
 
 Here is an example of a line-of-business app installation.
 
-``` syntax
+```xml
 <!-- Add PackageFamilyName -->
 <Add>
    <CmdID>0</CmdID>
@@ -342,7 +342,7 @@ Here is an example of a line-of-business app installation.
 
 Here is an example of an app installation with dependencies.
 
-``` syntax
+```xml
 <!-- Add PackageFamilyName -->
 <Add>
    <CmdID>0</CmdID>
@@ -376,7 +376,7 @@ Here is an example of an app installation with dependencies.
 
 Here is an example of an app installation with dependencies and optional packages.
 
-``` syntax
+```xml
 <!-- Add PackageFamilyName -->
 <Add>
    <CmdID>0</CmdID>
@@ -438,7 +438,7 @@ Here is an example of app installation.
 > **Note**  This is only supported in Windows 10 for desktop editions.
 
 
-``` syntax
+```xml
 <!-- Add PackageFamilyName -->
 <Add>
    <CmdID>0</CmdID>
@@ -475,7 +475,7 @@ Here is an example of app installation with dependencies.
 > **Note**  This is only supported in Windows 10 for desktop editions.
 
 
-``` syntax
+```xml
 <!-- Add PackageFamilyName -->
 <Add>
    <CmdID>0</CmdID>
@@ -526,7 +526,7 @@ When an app is installed successfully, the node is cleaned up and no longer pres
 
 Here is an example of a query for a specific app installation.
 
-``` syntax
+```xml
 <!-- Get all app status under AppInstallation for a specific app-->
 <Get>
    <CmdID>2</CmdID>
@@ -540,7 +540,7 @@ Here is an example of a query for a specific app installation.
 
 Here is an example of a query for all app installations.
 
-``` syntax
+```xml
 <!-- Get all app status under AppInstallation-->
 <Get>
    <CmdID>2</CmdID>
@@ -558,7 +558,7 @@ Application installations can take some time to complete, hence they are done as
 
 Here is an example of an alert.
 
-``` syntax
+```xml
 <Alert>
     <CmdID>4</CmdID>
     <Data>1226</Data>
@@ -594,7 +594,7 @@ To uninstall an app, you delete it under the origin node, package family name, a
 
 Here is an example for uninstalling all versions of an app for a user.
 
-``` syntax
+```xml
 <!-- Uninstall App for a Package Family-->
 <Delete>
    <CmdID>1</CmdID>
@@ -608,7 +608,7 @@ Here is an example for uninstalling all versions of an app for a user.
 
 Here is an example for uninstalling a specific version of the app for a user.
 
-``` syntax
+```xml
 <!-- Uninstall App for a specific package full name-->
 <Delete>
    <CmdID>1</CmdID>
@@ -631,7 +631,7 @@ Removing provisioned app occurs in the device context.
 
 Here is an example for removing a provisioned app from a device.
 
-``` syntax
+```xml
 <!— Remove Provisioned App for a Package Family-->
 <Delete>
    <CmdID>1</CmdID>
@@ -645,7 +645,7 @@ Here is an example for removing a provisioned app from a device.
 
 Here is an example for removing a specific version of a provisioned app from a device:
 
-``` syntax
+```xml
 <!-- Remove Provisioned App for a specific package full name-->
 <Delete>
    <CmdID>1</CmdID>
@@ -663,7 +663,7 @@ You can remove app licenses from a device per app based on the content ID.
 
 Here is an example for removing an app license for a user.
 
-``` syntax
+```xml
 <!-- Remove App License for a User-->
 <Delete>
    <CmdID>1</CmdID>
@@ -677,7 +677,7 @@ Here is an example for removing an app license for a user.
 
 Here is an example for removing an app license for a provisioned package (device context).
 
-``` syntax
+```xml
 <!-- Remove App License for a provisioned package (device) -->
 <Delete>
    <CmdID>1</CmdID>
@@ -697,7 +697,7 @@ For user-based uninstallation, use ./User in the LocURI, and for provisioning, u
 
 Here is an example. There is only one uninstall for hosted and store apps.
 
-``` syntax
+```xml
 <Alert>
     <Data>1226</Data>
     <Item>
@@ -723,7 +723,7 @@ To update an app from Microsoft Store, the device requires contact with the stor
 
 Here is an example of an update scan.
 
-``` syntax
+```xml
 <!— Initiate a update scan for a user-->
 <Exec>
    <CmdID>1</CmdID>
@@ -737,7 +737,7 @@ Here is an example of an update scan.
 
 Here is an example of a status check.
 
-``` syntax
+```xml
 <!— Get last error related to the update scan-->
 <Get>
    <CmdID>1</CmdID>
@@ -766,7 +766,7 @@ Turning off updates only applies to updates from the Microsoft Store at the devi
 
 Here is an example.
 
-``` syntax
+```xml
 <!— Prevent app from being automatically updated-->
 <Replace>
    <CmdID>1</CmdID>
@@ -795,7 +795,7 @@ You can install app on non-system volumes, such as a secondary partition or remo
 
 Here is an example.
 
-``` syntax
+```xml
 <!-- Get policy (Default)-->
 <Get>
    <CmdID>1</CmdID>
@@ -832,7 +832,7 @@ The RestrictAppDataToSystemVolume policy in [Policy CSP](policy-configuration-se
 
 Here is an example.
 
-``` syntax
+```xml
 <!-- Get policy (Default)-->
 <Get>
    <CmdID>1</CmdID>
@@ -873,7 +873,7 @@ The valid values are 0 (off, default value) and 1 (on).
 
 Here is an example.
 
-``` syntax
+```xml
 <!-- Get policy (Default)-->
 <Get>
    <CmdID>1</CmdID>

windows/client-management/mdm/enterpriseapn-csp.md

@@ -132,7 +132,7 @@ The following image shows the EnterpriseAPN configuration service provider in tr
 
 ## Examples
 
-``` syntax
+```xml
 <!--
 Copyright (c) Microsoft Corporation.  All rights reserved.
 -->

windows/client-management/mdm/enterpriseappmanagement-csp.md

@@ -209,7 +209,7 @@ The Microsoft Store application has a GUID of d5dc1ebb-a7f1-df11-9264-00237de2db
 
 Use the following SyncML format to query to see if the application is installed on a managed device:
 
-``` syntax
+```xml
 <Get>
       <CmdID>1</CmdID>
       <Item>
@@ -222,7 +222,7 @@ Use the following SyncML format to query to see if the application is installed
 
 Response from the device (it contains list of subnodes if this app is installed in the device).
 
-``` syntax
+```xml
 <Results>
    <CmdID>3</CmdID>
    <MsgRef>1</MsgRef>
@@ -266,7 +266,7 @@ The value actually applied to the device can be queried via the nodes under the
 
 Enroll enterprise ID “4000000001” for the first time:
 
-``` syntax
+```xml
 <Add>
    <CmdID>2</CmdID>
    <Item>
@@ -293,7 +293,7 @@ Enroll enterprise ID “4000000001” for the first time:
 
 Update the enrollment token (for example, to update an expired application enrollment token):
 
-``` syntax
+```xml
 <Replace>
    <CmdID>2</CmdID>
    <Item>
@@ -310,7 +310,7 @@ Update the enrollment token (for example, to update an expired application enrol
 
 Query all installed applications that belong to enterprise id “4000000001”:
 
-``` syntax
+```xml
 <Get>
    <CmdID>2</CmdID>
    <Item>
@@ -325,7 +325,7 @@ Query all installed applications that belong to enterprise id “4000000001”:
 
 Response from the device (that contains two installed applications):
 
-``` syntax
+```xml
 <Results>
    <CmdID>3</CmdID>
    <MsgRef>1</MsgRef>
@@ -444,7 +444,7 @@ To perform an XAP update, create the Name, URL, Version, and DownloadInstall nod
 
  
 
-``` syntax
+```xml
 <Atomic>
    <CmdID>2</CmdID>
    <!-- The Add command can be used if the download node does not have a matching product ID
@@ -514,7 +514,7 @@ To perform an XAP update, create the Name, URL, Version, and DownloadInstall nod
 
 Uninstall an installed enterprise application with product ID “{7BB316008A-141D-4A79-810F-8B764C4CFDFB }”:
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
     <Delete>

windows/client-management/mdm/enterpriseassignedaccess-csp.md

@@ -61,7 +61,7 @@ Application | <img src="images/enterpriseassignedaccess-csp.png" alt="modern app
 Application | Include PinToStart to display an app on the Start screen. For apps pinned to the Start screen, identify a tile size (small, medium, or large), and a location. The size of a small tile is 1 column x 1 row, a medium tile is 2 x 2, and a large tile is 4 x 2. For the tile location, the first value indicates the column and the second value indicates the row. A value of 0 (zero) indicates the first column, a value of 1 indicates the second column, and so on. Include autoRun as an attribute to configure the application to run automatically.
 
 Application example:
-``` syntax
+```xml
 <Application productId="{2A4E62D8-8809-4787-89F8-69D0F01654FB}" autoRun="true">
    <PinToStart>
       <Size>Large</Size>
@@ -78,7 +78,7 @@ Entry | Description
 Application | Multiple App Packages enable multiple apps to exist inside the same package. Since ProductIds identify packages and not applications, specifying a ProductId is not enough to distinguish between individual apps inside a multiple app package. Trying to include application from a multiple app package with just a ProductId can result in unexpected behavior. To support pinning applications in multiple app packages, use an AUMID parameter in lockdown XML. For the list of product ID and AUMID, see [ProductIDs in Windows 10 Mobile](#productid). The following example shows how to pin both Outlook mail and Outlook calendar.
 
 Application example:
-``` syntax
+```xml
 <Apps>
     <!-- Outlook Calendar -->
     <Application productId="{A558FEBA-85D7-4665-B5D8-A2FF9C19799B}"
@@ -110,7 +110,7 @@ Entry | Description
 Folder | A folder should be contained in `<Applications/>` node among with other `<Application/>` nodes, it shares most grammar with the Application Node, **folderId** is mandatory, **folderName** is optional, which is the folder name displayed on Start. **folderId** is a unique unsigned integer for each folder.
 
 Folder example:
-``` syntax
+```xml
 <Application folderId="4" folderName="foldername">
     <PinToStart>
         <Size>Large</Size>
@@ -123,7 +123,7 @@ Folder example:
 ```
 An application that belongs in the folder would add an optional attribute **ParentFolderId**, which maps to **folderId** of the folder. In this case, the location of this application will be located inside the folder.
 
-``` syntax
+```xml
 <Application productId="{2A4E62D8-8809-4787-89F8-69D0F01654FB}">
     <PinToStart>
         <Size>Medium</Size>
@@ -252,7 +252,7 @@ For example, in place of SettingPageDisplay, you would use ms-settings:display.
 
 Here is an example for Windows 10, version 1703.
 
-``` syntax
+```xml
 <Settings>
   <System name="ms-settings:display"/>
   <System name="ms-settings:appsforwebsites"/>
@@ -327,14 +327,14 @@ Starting in Windows 10, version 1703, Quick action settings no longer require an
 
 In this example, all settings pages and quick action settings are allowed. An empty \<Settings> node indicates that none of the settings are blocked.
 
-``` syntax
+```xml
 <Settings>
 </Settings>
 ```
 
 In this example for Windows 10, version 1511, all System setting pages are enabled. Note that the System page group is added as well as all of the System subpage names.
 
-``` syntax
+```xml
 <Settings>
   <System name="SettingsPageGroupPCSystem" />
   <System name="SettingsPageDisplay" />
@@ -350,7 +350,7 @@ In this example for Windows 10, version 1511, all System setting pages are ena
 ```
 Here is an example for Windows 10, version 1703.
 
-``` syntax
+```xml
 <Settings>
   <System name="ms-settings:display"/>
   <System name="ms-settings:appsforwebsites"/>
@@ -382,7 +382,7 @@ Buttons | The following list identifies the hardware buttons on the device that
 > Custom buttons are hardware buttons that can be added to devices by OEMs.
 
 Buttons example:
-``` syntax
+```xml
 <Buttons>
    <ButtonLockdownList>
       <!-- Lockdown all buttons -->
@@ -407,7 +407,7 @@ The Search and custom buttons can be <em>remapped</em> or configured to open a s
 
 To remap a button in lockdown XML, you supply the button name, the button event (typically "press"), and the product ID for the application the button will open.
 
-``` syntax
+```xml
 <ButtonRemapList>
    <Button name="Search">
       <ButtonEvent name="Press">
@@ -503,7 +503,7 @@ MenuItems | Use **DisableMenuItems** to prevent use of the context menu, which i
 
 MenuItems example:
 
-``` syntax
+```xml
 <MenuItems>
    <DisableMenuItems/>
 </MenuItems>
@@ -1196,7 +1196,7 @@ The XML examples in this section show how to perform various tasks by using OMA
 
 The following example shows how to add a new policy.
 
-``` syntax
+```xml
 <wap-provisioningdoc>
   <characteristic type="EnterpriseAssignedAccess">
     <characteristic type="AssignedAccess">
@@ -1211,7 +1211,7 @@ The following example shows how to add a new policy.
 
 The following example shows how to specify the language to display on the device.
 
-``` syntax
+```xml
 <wap-provisioningdoc>
    <characteristic type="EnterpriseAssignedAccess">
   <characteristic type="Language">
@@ -1230,7 +1230,7 @@ These XML examples show how to perform various tasks using OMA DM.
 
 The following example shows how to lock down a device.
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
    <SyncBody>
       <Add>
@@ -1251,7 +1251,7 @@ The following example shows how to lock down a device.
 
 The following example shows how to change the accent color to one of the standard colors.
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
    <SyncBody>
       <Replace>
@@ -1274,7 +1274,7 @@ The following example shows how to change the accent color to one of the standar
 
 The following example shows how to change the theme.
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
    <SyncBody>
        <Replace>
@@ -1297,7 +1297,7 @@ The following example shows how to change the theme.
 
 The following example shows how to set a custom theme accent color for the enterprise environment.
 
-``` syntax
+```xml
 <SyncBody>
    <Replace>
       <CmdID>1</CmdID>
@@ -1333,7 +1333,7 @@ The following example shows how to set a custom theme accent color for the enter
 
 Use the examples in this section to set a new lock screen and manage the lock screen features. If using a UNC path, format the LocURI as \\\\host\\share\\image.jpg.
 
-``` syntax
+```xml
 <Add>
   <CmdID>2</CmdID>
   <Item>
@@ -1351,7 +1351,7 @@ Use the examples in this section to set a new lock screen and manage the lock sc
 
 The following example shows how to query the device for the file being used as the lock screen.
 
-``` syntax
+```xml
 <Get>
   <CmdID>2</CmdID>
   <Item>
@@ -1364,7 +1364,7 @@ The following example shows how to query the device for the file being used as t
 
 The following example shows how to change the existing lock screen image to one of your choosing.
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
    <SyncBody>
       <Replace>
@@ -1389,7 +1389,7 @@ The following example shows how to change the existing lock screen image to one
 
 The following example shows how to set the time zone to UTC-07 Mountain Time (US & Canada).
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
    <SyncBody>
       <Replace>
@@ -1411,7 +1411,7 @@ The following example shows how to set the time zone to UTC-07 Mountain Time (US
 
 The following example shows how to set the time zone to Pacific Standard Time (UTC-08:00) without observing daylight savings time (UTC+01:00).
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
    <SyncBody>
       <Replace>
@@ -1435,7 +1435,7 @@ The following example shows how to set the time zone to Pacific Standard Time (U
 
 The following example shows how to set the language.
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
    <SyncBody>
       <Replace>

windows/client-management/mdm/enterprisedesktopappmanagement-csp.md

@@ -54,20 +54,14 @@ In Windows 10, version 1703 service release, a new tag \<DownloadFromAad\> was a
 
 Here is an example:
 
-```syntax
+```xml
-             <Enforcement>
+<Enforcement>
-
+  <CommandLine>/quiet</CommandLine>
-                <CommandLine>/quiet</CommandLine>
+  <TimeOut>5</TimeOut>
-
+  <RetryCount>3</RetryCount>
-                <TimeOut>5</TimeOut>
+  <RetryInterval>5</RetryInterval>
-
+  <DownloadFromAad>1</DownloadFromAad>
-                <RetryCount>3</RetryCount>
+</Enforcement>
-
-                <RetryInterval>5</RetryInterval>
-
-                <DownloadFromAad>1</DownloadFromAad>
-
-              </Enforcement>
 ```
 
 <a href="" id="msi-productid-status"></a>**MSI/*ProductID*/Status**
@@ -112,7 +106,7 @@ Value type is string. Supported operation is Get.
 
 **SyncML to request CSP version information**
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.1">
   <SyncBody>
     <Get>
@@ -140,7 +134,7 @@ The following table describes the fields in the previous sample:
 
 **SyncML to perform MSI operations for application uninstall**
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.1">
   <SyncBody>
     <Delete>
@@ -168,7 +162,7 @@ The following table describes the fields in the previous sample:
 
 **SyncML to perform MSI operations for application status reporting**
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.1">
   <SyncBody>
     <Get>
@@ -196,7 +190,7 @@ The following table describes the fields in the previous sample:
 
 **SyncML to perform MSI install operations for an application targeted to a specific user on the device. The Add command is required to preceed the Exec command.**
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.1">
   <SyncBody>
     <Add>
@@ -290,7 +284,7 @@ The following table describes the fields in the previous sample:
 
 **SyncML to perform MSI install operations for an application targeted to all users on the device (per-device installation)**
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.1">
   <SyncBody>
     <Add>
@@ -540,7 +534,7 @@ Here's a list of references:
 ## Alert example
 
 
-``` syntax
+```xml
 <Alert>
        <CmdID>4</CmdID>
        <Data>1224</Data>

windows/client-management/mdm/enterpriseextfilessystem-csp.md

@@ -70,7 +70,7 @@ Supported operations is Get.
 
 The following example shows how to retrieve a file from the device.
 
-``` syntax
+```xml
 <Get>
     <CmdID>2</CmdID>
     <Item>
@@ -83,7 +83,7 @@ The following example shows how to retrieve a file from the device.
 
 The following example shows the file name that is returned in the body of the response syncML code. In this example, the full path of the file on the device is C:/data/test/bin/filename.txt.
 
-``` syntax
+```xml
 <Results>
     <CmdID>3</CmdID>
     <MsgRef>1</MsgRef>
@@ -103,7 +103,7 @@ The following example shows the file name that is returned in the body of the re
 
 The following example shows how to push a file to the device.
 
-``` syntax
+```xml
 <Add>
    <CmdID>2</CmdID>
    <Item>

windows/client-management/mdm/enterprisemodernappmanagement-csp.md

@@ -52,7 +52,7 @@ Supported operation is Get.
 
 Here's an example of AppInventoryResults operation.
 
-``` syntax
+```xml
 <Get>
    <CmdID>11</CmdID>
    <Item>
@@ -100,7 +100,7 @@ Supported operation is Get and Replace.
 
 The following example sets the inventory query for the package names and checks the status for reinstallation for all main packages that are nonStore apps.
 
-``` syntax
+```xml
 <Replace>
    <CmdID>10</CmdID>
    <Item>
@@ -208,7 +208,7 @@ Supported operations are Get and Delete.
 
 Here's an example for uninstalling an app:
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
         <!-- Uninstall app -->
@@ -345,7 +345,7 @@ Value type is string. Supported operations are Add, Get, Replace, and Delete.
 
 The following example sets the value for the 'Server'
 
-``` syntax
+```xml
 <!— Configure app settings -->
 <Add>
    <CmdID>0</CmdID>
@@ -363,7 +363,7 @@ The following example sets the value for the 'Server'
 
 The following example gets all managed app settings for a specific app.
 
-``` syntax
+```xml
 <!—Get app settings -->
 <Get>
    <CmdID>0</CmdID>
@@ -583,7 +583,7 @@ For examples of how to use this CSP to for reporting apps inventory, installatio
 
 Query the device for a specific app subcategory, such as nonStore apps.
 
-``` syntax
+```xml
 <Get>
   <CmdID>1</CmdID>
   <Item>
@@ -598,8 +598,7 @@ The result contains a list of apps, such as \<Data>App1/App2/App\</Data\>.
 
 Subsequent query for a specific app for its properties.
 
-``` syntax
+```xml
-
 <Get>
    <CmdID>1</CmdID>
    <Item>

windows/client-management/mdm/federated-authentication-device-enrollment.md

@@ -92,7 +92,7 @@ https://EnterpriseEnrollment.Contoso.com/EnrollmentServer/Discovery.svc
 
 The following example shows the discovery service request.
 
-``` syntax
+```xml
     <?xml version="1.0"?>
     <s:Envelope xmlns:a="http://www.w3.org/2005/08/addressing"
        xmlns:s="http://www.w3.org/2003/05/soap-envelope">
@@ -198,7 +198,7 @@ The server has to send a POST to a redirect URL of the form ms-app://string (the
 
 The following example shows a response received from the discovery web service which requires authentication via WAB.
 
-``` syntax
+```xml
     <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
        xmlns:a="http://www.w3.org/2005/08/addressing">
       <s:Header>
@@ -252,7 +252,7 @@ wsse:BinarySecurityToken/attributes/EncodingType: The &lt;wsse:BinarySecurityTok
 
 The following is an enrollment policy request example with a received security token as client credential.
 
-``` syntax
+```xml
     <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
        xmlns:a="http://www.w3.org/2005/08/addressing"
        xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
@@ -305,7 +305,7 @@ MS-XCEP supports very flexible enrollment policies using various Complex Types a
 
 The following snippet shows the policy web service response.
 
-``` syntax
+```xml
       <s:Envelope
          xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
          xmlns:s="http://www.w3.org/2003/05/soap-envelope"
@@ -399,7 +399,7 @@ The RST may also specify a number of AdditionalContext items, such as DeviceType
 
 The following example shows the enrollment web service request for federated authentication.
 
-``` syntax
+```xml
     <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
        xmlns:a="http://www.w3.org/2005/08/addressing"
        xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
@@ -505,7 +505,7 @@ Here is a sample RSTR message and a sample of OMA client provisioning XML within
 
 The following example shows the enrollment web service response.
 
-``` syntax
+```xml
     <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" 
        xmlns:a="http://www.w3.org/2005/08/addressing" 
        xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

windows/client-management/mdm/hotspot-csp.md

@@ -134,7 +134,7 @@ Changes to this node require a reboot.
 
 For CDMA networks that use a separate Network Access Identity (NAI) for Internet sharing, a new parm, TetheringNAI, has been added in the [CM\_CellularEntries configuration service provider](cm-cellularentries-csp.md) configuration service provider. The following sample demonstrates how to specify the connection.
 
-``` syntax
+```xml
 <wap-provisioningdoc>
     <characteristic type="CM_CellularEntries">
         <characteristic type="TetheringNAIConn">

windows/client-management/mdm/implement-server-side-mobile-application-management.md

@@ -59,7 +59,7 @@ Below are protocol changes for MAM enrollment:
 
 Here is an example provisioning XML for MAM enrollment.  
 
-``` syntax
+```xml
 <wap-provisioningdoc version="1.1"> 
   <characteristic type="APPLICATION"> 
     <parm name="APPID" value="w7"/> 

windows/client-management/mdm/maps-csp.md

@@ -126,7 +126,7 @@ Here is a list of GUIDs of the most downloaded reqions.
 
 Here is an example queuing a map package of New York for download.
 
-``` syntax
+```xml
 <SyncML>
     <SyncBody>
        <Add>
@@ -144,7 +144,7 @@ Here is an example queuing a map package of New York for download.
 
 Here is an example that gets the status of the New York map package on the device.
 
-``` syntax
+```xml
 <SyncML>
     <SyncBody>
        <Get>

windows/client-management/mdm/messaging-csp.md

@@ -55,7 +55,7 @@ The following diagram shows the Messaging configuration service provider in tree
 
 **SyncML example**
 
-``` syntax
+```xml
  <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
     <Replace>

windows/client-management/mdm/mobile-device-enrollment.md

@@ -103,7 +103,7 @@ To manually trigger enrollment migration, you can run MDMMaintenenceTask.
 
 The enrollment server can decline enrollment messages using the SOAP Fault format. Errors created can be sent as follows:
 
-``` syntax
+```xml
 <s:envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
     <s:header>
         <a:action s:mustunderstand="1">http://schemas.microsoft.com/windows/pki/2009/01/enrollment/rstrc/wstep</a:action>
@@ -200,7 +200,7 @@ The enrollment server can decline enrollment messages using the SOAP Fault forma
 
 In Windows 10, version 1507, we added the deviceenrollmentserviceerror element. Here is an example:
 
-``` syntax
+```xml
 <s:envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" xmlns:a="http://www.w3.org/2005/08/addressing">
     <s:header>
         <a:action s:mustunderstand="1">http://schemas.microsoft.com/windows/pki/2009/01/enrollment/rstrc/wstep</a:action>

windows/client-management/mdm/multisim-csp.md

@@ -74,7 +74,7 @@ Supported operation is Get and Replace. Value type is bool.
 ## Examples
 
 Get modem
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
     <Get>
@@ -93,7 +93,7 @@ Get modem
 ```
 
 Get slots
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
     <Get>
@@ -112,7 +112,7 @@ Get slots
 ```
 
 Get slot state
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
     <Get>
@@ -131,7 +131,7 @@ Get slot state
 ```
 
 Select slot
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
     <Replace>

windows/client-management/mdm/new-in-windows-mdm-enrollment-management.md

@@ -1660,7 +1660,7 @@ The software version information from **DevDetail/SwV** does not match the versi
 
 Applies only to phone prior to build 10586.218: When ApplicationManagement/ApplicationRestrictions policy is deployed to Windows 10 Mobile, installation and update of apps dependent on Microsoft Frameworks may get blocked with error 0x80073CF9. To work around this issue, you must include the Microsoft Framework Id to your list of allowed apps.
 
-``` syntax
+```xml
 <App ProductId="{00000000-0000-0000-0000-000000000000}" PublisherName="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US"/>
 ```
 
@@ -1709,7 +1709,7 @@ The following XML sample explains the properties for the EAP TLS XML including c
 >For PEAP or TTLS Profiles the EAP TLS XML is embedded within some PEAP or TTLS specific elements.
 
  
-``` syntax
+```xml
 <EapHostConfig xmlns="http://www.microsoft.com/provisioning/EapHostConfig">
  <EapMethod>
   <Type xmlns="http://www.microsoft.com/provisioning/EapCommon">13</Type>

windows/client-management/mdm/nodecache-csp.md

@@ -19,7 +19,7 @@ The NodeCache configuration service provider is used to manage the client cache.
 
 NodeCache supports the comparison of hash values instead of actual node values:
 
-``` syntax
+```xml
 <Type xmlns="syncml:metinf">
 application/x-nodemon-sha256
 </type>
@@ -76,7 +76,7 @@ Supported operations are Get, Add, and Delete.
 
 Here's an example for setting the ExpectedValue to nonexistent.
 
-``` syntax
+```xml
 <Add>
    <CmdID>10</CmdID>
    <Item>
@@ -146,7 +146,7 @@ Supported operations are Add, Get, and Delete.
 
 Creating settings for node caching:
 
-``` syntax
+```xml
 <Add>
    <CmdID>2</CmdID>
    <Item>
@@ -222,7 +222,7 @@ Creating settings for node caching:
 
 Getting nodes under Provider ID MDMSRV1, cache version, changed nodes, node, expected value:
 
-``` syntax
+```xml
 <Get>
    <CmdID>18</CmdID>
    <Item>
@@ -267,7 +267,7 @@ Getting nodes under Provider ID MDMSRV1, cache version, changed nodes, node, exp
 
 Replacing the cache version, node URI, and expected value:
 
-``` syntax
+```xml
 <Replace>
    <CmdID>2</CmdID>
    <Item>
@@ -299,7 +299,7 @@ Replacing the cache version, node URI, and expected value:
 
 For AutoSetExpectedValue, a Replace operation with empty data will query the ./DevDetail/Ext/Microsoft/DeviceName.
 
-```syntax
+```xml
           <Add>
             <CmdID>2001</CmdID>
             <Item>
@@ -335,12 +335,12 @@ A Get operation on ./Vendor/MSFT/NodeCache/MDM%20SyncML%20Server/Nodes/20/Expect
 
 A Get operation on the ChangedNodesData returns an encoded XML. Here is example:
 
-```syntax
+```xml
 <Nodes><Node Id="10" Uri=""></Node><Node Id="20" Uri="./DevDetail/Ext/Microsoft/DeviceName">U09NRU5FV1ZBTFVF</Node></Nodes>
 ```
 It represents this:
 
-```syntax
+```xml
 <Nodes>
     <Node Id="10" Uri=""></Node>
     <Node Id="20" Uri="./DevDetail/Ext/Microsoft/DeviceName">U09NRU5FV1ZBTFVF</Node>

windows/client-management/mdm/office-csp.md

@@ -67,7 +67,7 @@ The only supported operation is Get.
 
 Sample SyncML to install Office 365 Business Retail from current channel.
 
-```syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
     <Exec>
@@ -89,7 +89,7 @@ Sample SyncML to install Office 365 Business Retail from current channel.
 
 To uninstall the Office 365 from the system:
 
-```syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
     <Exec>
@@ -111,7 +111,7 @@ To uninstall the Office 365 from the system:
 
 To get the current status of Office 365 on the device.
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
     <Get>

windows/client-management/mdm/on-premise-authentication-device-enrollment.md

@@ -86,7 +86,7 @@ https://EnterpriseEnrollment.Contoso.com/EnrollmentServer/Discovery.svc
 
 The following example shows the discovery service request.
 
-``` syntax
+```xml
     <?xml version="1.0"?>
     <s:Envelope xmlns:a="http://www.w3.org/2005/08/addressing"
        xmlns:s="http://www.w3.org/2003/05/soap-envelope">
@@ -134,7 +134,7 @@ The discovery response is in the XML format and includes the following fields:
 
 The following example shows a response received from the discovery web service for OnPremise authentication:
 
-``` syntax
+```xml
     <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
        xmlns:a="http://www.w3.org/2005/08/addressing">
       <s:Header>
@@ -171,7 +171,7 @@ For the OnPremise authentication policy, the UsernameToken in GetPolicies contai
 
 The following example shows the policy web service request.
 
-``` syntax
+```xml
     <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"
        xmlns:a="http://www.w3.org/2005/08/addressing"
        xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
@@ -219,7 +219,7 @@ MS-XCEP supports very flexible enrollment policies using various Complex Types a
 
 The following snippet shows the policy web service response.
 
-``` syntax
+```xml
       <s:Envelope
          xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
          xmlns:s="http://www.w3.org/2003/05/soap-envelope"
@@ -311,7 +311,7 @@ The RST may also specify a number of AdditionalContext items, such as DeviceType
 
 The following example shows the enrollment web service request for OnPremise authentication.
 
-``` syntax
+```xml
     <s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope" 
        xmlns:a="http://www.w3.org/2005/08/addressing" 
        xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
@@ -396,7 +396,7 @@ The following example shows the enrollment web service request for OnPremise aut
 
 The following example shows the enrollment web service response.
 
-``` syntax
+```xml
     <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" 
        xmlns:a="http://www.w3.org/2005/08/addressing" 
        xmlns:u="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">

windows/client-management/mdm/passportforwork-csp.md

@@ -273,7 +273,7 @@ Value type is string. Supported operations are Add, Get, Replace, and Delete.
 
 Here's an example for setting Windows Hello for Business and setting the PIN policies. It also turns on the use of biometrics and TPM.
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
           <SyncBody>
             <Add>

windows/client-management/mdm/personalization-csp.md

@@ -71,7 +71,7 @@ The following diagram shows the Personalization configuration service provider i
 
 ## Example SyncML
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
     <Replace>

windows/client-management/mdm/policy-configuration-service-provider.md

@@ -5456,7 +5456,7 @@ The following diagram shows the Policy configuration service provider in tree fo
 
 Set the minimum password length to 4 characters.
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
     <SyncBody>
         <Replace>
@@ -5478,7 +5478,7 @@ Set the minimum password length to 4 characters.
 
 Do not allow NFC.
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
     <SyncBody>
         <Replace>

windows/client-management/mdm/policy-csp-applicationmanagement.md

@@ -594,7 +594,7 @@ List of semi-colon delimited Package Family Names of Windows apps. Listed Window
 
 For this policy to work, the Windows apps need to declare in their manifest that they will use the start up task. Example of the declaration here: 
 
-``` syntax
+```xml
 <desktop:Extension Category="windows.startupTask"> 
    <desktop:StartupTask TaskId="CoffeeStartupTask" Enabled="true" DisplayName="ms-resource:Description" /> 
 </desktop:Extension>
@@ -972,7 +972,7 @@ Value type is string.
 <!--Example-->
 Sample SyncML:
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.1"> 
   <SyncBody> 
     <Add> 
@@ -999,7 +999,7 @@ Sample SyncML:
 ```
 XSD:
 
-``` syntax
+```xml
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema">
   <xs:simpleType name="recurrence" final="restriction">
     <xs:restriction base="xs:string">

windows/client-management/mdm/policy-csp-deviceinstallation.md

@@ -121,7 +121,7 @@ ADMX Info:
 To enable this policy, use the following SyncML. This example allows Windows to install compatible devices with a device ID of USB\Composite or USB\Class_FF. To configure multiple classes, use `` as a delimiter. 
 
 
-``` syntax
+```xml
 <SyncML>
     <SyncBody>
         <Replace>
@@ -238,7 +238,7 @@ To enable this policy, use the following SyncML. This example allows Windows to
 Enclose the class GUID within curly brackets {}. To configure multiple classes, use `&#xF000;` as a delimiter. 
 
 
-``` syntax
+```xml
 <SyncML>
     <SyncBody>
         <Replace>
@@ -417,7 +417,7 @@ ADMX Info:
 To enable this policy, use the following SyncML. This example prevents Windows from installing devices that are not specifically described by any other policy setting. 
 
 
-``` syntax
+```xml
 <SyncML>
     <SyncBody>
         <Replace>
@@ -519,7 +519,7 @@ ADMX Info:
 To enable this policy, use the following SyncML. This example prevents Windows from installing compatible devices with a device ID of USB\Composite or USB\Class_FF. To configure multiple classes, use <code>&amp;#xF000;</code> as a delimiter. To apply the policy to matching device classes that are already installed, set DeviceInstall_IDs_Deny_Retroactive to true. 
 
 
-``` syntax
+```xml
 <SyncML>
     <SyncBody>
         <Replace>
@@ -626,7 +626,7 @@ To enable this policy, use the following SyncML. This example prevents Windows f
 Enclose the class GUID within curly brackets {}. To configure multiple classes, use `&#xF000;` as a delimiter. To apply the policy to matching device classes that are already installed, set DeviceInstall_Classes_Deny_Retroactive to true. 
 
 
-``` syntax
+```xml
 <SyncML>
     <SyncBody>
         <Replace>

windows/client-management/mdm/policy-csp-experience.md

@@ -1463,13 +1463,13 @@ _**Sync the browser settings automatically**_
 
 _**Prevent syncing of browser settings and prevent users from turning it on**_
 
-1.	Set **DoNotSyncBrowserSettings** to 2 (Prevented/turned off).
+1. Set **DoNotSyncBrowserSettings** to 2 (Prevented/turned off).
-2.	Set **PreventUsersFromTurningOnBrowserSyncing** to 1 (Prevented/turned off).
+2. Set **PreventUsersFromTurningOnBrowserSyncing** to 1 (Prevented/turned off).
 
 _**Prevent syncing of browser settings and let users turn on syncing**_
 
-1.	Set **DoNotSyncBrowserSettings** to 2 (Prevented/turned off).
+1. Set **DoNotSyncBrowserSettings** to 2 (Prevented/turned off).
-2.	Set **PreventUsersFromTurningOnBrowserSyncing** to 0 (Allowed/turned on).
+2. Set **PreventUsersFromTurningOnBrowserSyncing** to 0 (Allowed/turned on).
 
 _**Turn syncing off by default but don’t disable**_
 
@@ -1550,13 +1550,13 @@ _**Sync the browser settings automatically**_
 
 _**Prevent syncing of browser settings and prevent users from turning it on**_
 
-1.	Set **DoNotSyncBrowserSettings** to 2 (Prevented/turned off).
+1. Set **DoNotSyncBrowserSettings** to 2 (Prevented/turned off).
-2.	Set **PreventUsersFromTurningOnBrowserSyncing** to 1 (Prevented/turned off).
+2. Set **PreventUsersFromTurningOnBrowserSyncing** to 1 (Prevented/turned off).
 
 _**Prevent syncing of browser settings and let users turn on syncing**_
 
-1.	Set **DoNotSyncBrowserSettings** to 2 (Prevented/turned off).
+1. Set **DoNotSyncBrowserSettings** to 2 (Prevented/turned off).
-2.	Set **PreventUsersFromTurningOnBrowserSyncing** to 0 (Allowed/turned on).
+2. Set **PreventUsersFromTurningOnBrowserSyncing** to 0 (Allowed/turned on).
 
 <!--/SupportedValues-->
 <!--Example-->

windows/client-management/mdm/policy-csp-internetexplorer.md

@@ -2249,7 +2249,7 @@ ADMX Info:
 
 <!--/ADMXBacked-->
 <!--Example-->
-```syntax
+```xml
   <SyncBody>
       <Replace>
           <CmdID>2</CmdID>

windows/client-management/mdm/policy-csp-restrictedgroups.md

@@ -76,7 +76,7 @@ Caution: If a Restricted Groups policy is applied, any current member not on the
 
 Starting in Windows 10, version 1809, you can use this schema for retrieval and application of the RestrictedGroups/ConfigureGroupMembership policy. A minimum occurrence of 0 members when applying the policy implies clearing the access group and should be used with caution.
 
-``` syntax
+```xml
 <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" version="1.0">  
   <xs:simpleType name="member_name">
     <xs:restriction base="xs:string">

windows/client-management/mdm/policy-csp-smartscreen.md

@@ -73,6 +73,9 @@ manager: dansimp
 <!--Description-->
 Added in Windows 10, version 1703. Allows IT Admins to control whether users are allowed to install apps from places other than the Store.
 
+> [!Note]
+> This policy will block installation only while the device is online. To block offline installation too, **SmartScreen/PreventOverrideForFilesInShell** and **SmartScreen/EnableSmartScreenInShell** policies should also be enabled.
+
 <!--/Description-->
 <!--ADMXMapped-->
 ADMX Info:  

windows/client-management/mdm/policy-csp-userrights.md

@@ -20,7 +20,7 @@ User rights are assigned for user accounts or groups. The name of the policy def
 
 Here is an example syncml for setting the user right BackupFilesAndDirectories for Administrators and Authenticated Users groups.
 
-```syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
 
 <SyncBody>

windows/client-management/mdm/policy-csp-windowslogon.md

@@ -305,7 +305,7 @@ If you disable or don't configure this policy setting, any user can disconnect t
 
 Here is an example to enable this policy:
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
   <SyncBody>
     <Atomic>

windows/client-management/mdm/registry-ddf-file.md

@@ -17,7 +17,7 @@ ms.date: 06/26/2017
 
 This topic shows the OMA DM device description framework (DDF) for the **Registry** configuration service provider. DDF files are used only with OMA DM provisioning XML.
 
-``` syntax
+```xml
 <MgmtTree xmlns:MSFT="http://schemas.microsoft.com/MobileDevice/DM">
     <VerDTD>1.2</VerDTD>
     <Node>

windows/client-management/mdm/remotefind-csp.md

@@ -102,7 +102,7 @@ Supported operation is Get.
 ## Examples
 
 
-``` syntax
+```xml
 <SyncML xmlns="SYNCML:SYNCML1.2">
     <SyncBody>
         <Atomic>