Merge pull request #6368 from MicrosoftDocs/main

12/10/2021 PM Publish

Author: Taojunshen

memdocs/autopilot/autopilot-faq.yml

@@ -158,7 +158,6 @@ sections:
           | How many ways are there to register a device for Windows Autopilot|There are six ways to register a device, depending on who is doing the registering: <br><br>1. OEM Direct API (only available to TVOs) <br>2. MPC using the MPC API (must be a CSP) <br>3. MPC using manual upload of CSV file in the UI (must be a CSP) <br>4. MSfB using CSV file upload <br>5. Intune using CSV file upload <br>6. Microsoft 365 Business Premium portal using CSV file upload|
           |How many ways are there to create a Windows Autopilot profile?|There are four ways to create and assign a Windows Autopilot profile: <br><br>1. Through MPC (must be a CSP) <br>2. Through MSfB <br>3. Through Intune (or another MDM) <br>4. Microsoft 365 Business Premium portal <br><br>Microsoft recommends creation and assignment of profiles through Intune. |
           | What are some common causes of registration failures? |1. Bad or missing hardware hash entries can lead to faulty registration attempts <br>2. Hidden special characters in CSV files. <br><br>To avoid this issue, after creating your CSV file, open it in Notepad to look for hidden characters or trailing spaces or other corruptions.|
-          | Is Autopilot supported on IoT devices? | Autopilot isn't supported on IoT Core devices, and there are currently no plans to add this support. Autopilot is supported on Windows 10 IoT Enterprise SAC devices.|
           | Is Autopilot supported in all regions/countries? | Autopilot only supports customers using global Azure. Global Azure doesn't include the three entities listed below:<br>- Azure Germany <br>- Azure China 21Vianet<br>- Azure Government<br>So, if a customer is set up in global Azure, there are no region restrictions. For example, if Contoso uses global Azure but has employees working in China, the Contoso employees working in China could use Autopilot to deploy devices. If Contoso uses Azure China 21Vianet, the Contoso employees couldn't use Autopilot.|
           | Why does TPM provisioning/attestatstion take longer during the first boot on a device? | TPM provisioning involves generating and processing strong cryptographic keys and depending on characteristics of TPM hardware used on a device, it may take longer than 1 minute on first boot.|
           

memdocs/index.yml

@@ -30,6 +30,9 @@ highlightedContent:
     - title: Secure your remote workforce
       itemType: get-started
       url: /enterprise-mobility-security/remote-work/
+    - title: Microsoft Endpoint Manager fundamentals
+      itemType: learn
+      url: /learn/paths/endpoint-manager-fundamentals/
 
 conceptualContent:
   items:

memdocs/intune/apps/app-protection-policy.md

@@ -8,7 +8,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 07/13/2021
+ms.date: 12/02/2021
 ms.topic: overview
 ms.service: microsoft-intune
 ms.subservice: apps
@@ -219,6 +219,9 @@ While the **Global** policy applies to all users in your tenant, any standard In
 
 Multi-identity support allows an app to support multiple audiences. These audiences are both "corporate" users and "personal" users. Work and school accounts are used by "corporate" audiences, whereas personal accounts would be used for consumer audiences, such as Microsoft Office users. An app that supports multi-identity can be released publicly, where app protection policies apply only when the app is used in the work and school ("corporate") context. Multi-identity support uses the [Intune SDK](../developer/app-sdk.md) to only apply app protection policies to the work or school account signed into the app. If a personal account is signed into the app, the data is untouched. App protection policies can be used to prevent the transfer of work or school account data to personal accounts within the multi-identity app, personal accounts within other apps, or personal apps.
 
+> [!IMPORTANT]
+> Regardless of whether an app supports multi-identity, only a single "corporate" identity can have an Intune App Protection Policy applied.
+
 For an example of "personal" context, consider a user who starts a new document in Word, this is considered personal context so Intune App Protection policies are not applied. Once the document is saved on the "corporate" OneDrive account, then it is considered "corporate" context and Intune App Protection policies are applied.
 
 Consider the following examples for the work or "corporate" context:

memdocs/intune/apps/company-portal-app.md

@@ -178,6 +178,9 @@ The following actions are available:
 > [!NOTE]
 > These actions can be used to restrict device actions in the Company Portal app and website and do not implement any device restriction policies. To restrict users from performing factory reset or MDM removal from settings, you must configure device restriction policies.
 
+### Device compliance status in Company Portal website
+End users can see the compliance status of their devices from the Company Portal website. End users can navigate to the [Company Portal](https://portal.manage.microsoft.com/devices) website and select the **Devices** page to see device status. Devices will be listed with a status of **Can access company resources**, **Checking access**, or **Can't access company resources**. For related information, see [Manage apps from the Company Portal website](../user-help/manage-apps-cpweb.md).
+
 ## Opening Web Company Portal applications
 For Web Company Portal applications, if the end user has the Company Portal application installed, the end users will see a dialog box asking how they want to open the application when opening outside of the browser. If the app is not in the path of the Company Portal, then the Company Portal will open the homepage. If the app is in the path, then the Company Portal will open the specific app. 
 

memdocs/intune/developer/app-wrapper-prepare-android.md

@@ -7,7 +7,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 11/11/2021
+ms.date: 12/01/2021
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
@@ -54,7 +54,7 @@ Before running the tool, review [Security considerations for running the App Wra
   > [!NOTE]
   > If your input app is an Android App Bundle (.aab), you will need to convert it to an APK before using the Intune App Wrapping Tool. For details, see [Convert Android App Bundle (AAB) to APK](#convert-android-app-bundle-aab-to-apk). As of August 2021, [new private apps can still be published to the Google Play Store as APKs](https://support.google.com/googleplay/work/answer/6145139?hl=en).
   
-- The app must be developed by or for your company. You cannot use this tool on apps downloaded from the Google Play Store.
+- The app must be developed by or for your company. You cannot use this tool on apps that are available in the Google Play Store. This includes downloading or obtaining the app from the Google Play Store.
 
 - To run the App Wrapping Tool, you must install the latest version of the [Java Runtime Environment](https://java.com/download/) and then ensure that the Java path variable has been set to C:\ProgramData\Oracle\Java\javapath in your Windows environment variables. For more help, see the [Java documentation](https://java.com/en/download/help/index.html).
 

memdocs/intune/developer/apps-prepare-mobile-application-management.md

@@ -7,7 +7,7 @@ keywords:
 author: Erikre
 ms.author: erikre
 manager: dougeby
-ms.date: 08/06/2021
+ms.date: 12/01/2021
 ms.topic: reference
 ms.service: microsoft-intune
 ms.subservice: developer
@@ -38,7 +38,7 @@ The App Wrapping Tool is used primarily for **internal** line-of-business (LOB)
 
 You don't need the source code to use the tool, but you do need signing credentials. For more about signing credentials, see the [Intune blog](https://blogs.technet.microsoft.com/enterprisemobility/2015/02/25/how-to-obtain-the-prerequisites-for-the-intune-app-wrapping-tool-for-ios/). For the App Wrapping Tool documentation, see [Android App Wrapping Tool](app-wrapper-prepare-android.md) and [iOS App Wrapping Tool](app-wrapper-prepare-ios.md).
 
-The App Wrapping Tool does **not** support apps in the Apple App Store or Google Play Store. It also doesn't support certain features that require developer integration (see the following feature comparison table).
+The App Wrapping Tool does **not** support apps in or available in the Apple App Store or Google Play Store. It also doesn't support certain features that require developer integration (see the following feature comparison table).
 
 For more information about the App Wrapping Tool for app protection policies on devices that are not enrolled in Intune, see [Protect line-of-business apps and data on devices not enrolled in Microsoft Intune](../apps/apps-add.md).
 
@@ -48,7 +48,7 @@ For more information about the App Wrapping Tool for app protection policies on
 ### Reasons to use the App Wrapping Tool
 
 * Your app does not have built-in data protection features
-* Your app is deployed internally
+* Your app is deployed internally and the app is not available in the Apple App Store or Google Play Store
 * You don't have access to the app's source code
 * You didn't develop the app
 * Your app has minimal user authentication experiences

memdocs/intune/fundamentals/whats-new.md

@@ -86,6 +86,9 @@ For more information, see [Configure the Microsoft Managed Home Screen app for A
 #### New event viewer for Windows 10 diagnostics <!-- 10741116 -->
 We've added a new event viewer to Windows device diagnostics called *Microsoft-Windows-Windows Firewall with Advanced Security/Firewall*. The event viewer can assist you in troubleshooting issues with the firewall. For more information about Windows device diagnostics, see [Collect diagnostics from a Windows device](../remote-actions/collect-diagnostics.md).   
 
+#### Device compliance status in Company Portal website<!-- 8782968 -->
+End users can more easily see the compliance status of their devices from the Company Portal website. End users can navigate to the [Company Portal](https://portal.manage.microsoft.com/devices) website and select the **Devices** page to see device status. Devices will be listed with a status of **Can access company resources**, **Checking access**, or **Can't access company resources**. For related information, see [Manage apps from the Company Portal website](../user-help/manage-apps-cpweb.md) and [How to configure the Intune Company Portal apps, Company Portal website, and Intune app](../apps/company-portal-app.md).
+
 ## Week of November 22, 2021  
 
 <!-- vvvvvvvvvvvvvvvvvvvvvv -->

memdocs/intune/user-help/manage-apps-cpweb.md

@@ -7,7 +7,7 @@ keywords:
 author: lenewsad
 ms.author: lanewsad
 manager: dougeby
-ms.date: 11/25/2020
+ms.date: 12/10/2021
 ms.topic: end-user-help
 ms.prod:
 ms.service: microsoft-intune
@@ -110,5 +110,8 @@ Select an app on the **Apps** or **Installed apps** page to view its details. Yo
 
    ![Screenshot of Company Portal website, App details page.](./media/intune-app-details-1907.png)  
 
+## Device compliance status
+View the compliance status of your devices from the Company Portal website. You can navigate to the [Company Portal](https://portal.manage.microsoft.com/devices) website and select the **Devices** page to see device status. Devices will be listed with a status of **Can access company resources**, **Checking access**, or **Can't access company resources**.
+
 ## Next steps
 Need more help? Contact your company support. For contact information, check the [Company Portal website](https://go.microsoft.com/fwlink/?linkid=2010980).