Merge pull request #9804 from MicrosoftDocs/main

Angela Fleischmann · web-flow · commit 997beee0afd0 · 2023-02-13T16:45:17.000-07:00
Publish 02/13/2023 3:30 PM PT
diff --git a/memdocs/autopilot/windows-autopilot-hybrid.md b/memdocs/autopilot/windows-autopilot-hybrid.md
@@ -152,6 +152,12 @@ Before beginning the installation, make sure that all of the [Intune connector s
 > - After you sign in to the Connector, it can take several minutes to appear in the [Microsoft Endpoint Manager admin center](https://endpoint.microsoft.com/). It appears only if it can successfully communicate with the Intune service.
 > - Inactive Intune connectors still appear in the Intune Connectors blade and will automatically be cleaned up after 30 days.
 
+After installing the Intune Connector, it will start logging in the **Event Viewer** under the path **Applications and Services Logs** > **Microsoft** > **Intune** > **ODJConnectorService**. Under this path you will find **Admin** and **Operational** logs.
+
+> [!NOTE]
+>
+> The Intune Connector originally logged in the **Event Viewer** directly under **Applications and Services Logs** in a log called **ODJ Connector Service**. However, logging for the Intune Connector has since moved to the path **Applications and Services Logs** > **Microsoft** > **Intune** > **ODJConnectorService**. If you find that the **ODJ Connector Service** log at the original location is empty or not updating, please check the new path location instead.
+
 ### Configure web proxy settings
 
 If you have a web proxy in your networking environment, ensure that the Intune Connector for Active Directory works properly by referring to [Work with existing on-premises proxy servers](../intune/enrollment/autopilot-hybrid-connector-proxy.md).
diff --git a/memdocs/breadcrumb/toc.yml b/memdocs/breadcrumb/toc.yml
@@ -82,4 +82,4 @@ items:
     topicHref: /mem/autopilot/
   - name: Solutions
     tocHref: /mem/#solutions---scenarios
-    topicHref: /mem/solutions/
+    topicHref: /mem/#solutions---scenarios
diff --git a/memdocs/intune/configuration/oemconfig-zebra-android-devices.md b/memdocs/intune/configuration/oemconfig-zebra-android-devices.md
@@ -50,7 +50,7 @@ Create an [OEMConfig configuration profile](android-oem-configuration-overview.m
 
 On Zebra devices, you can have many profiles on each device simultaneously. This feature allows you to split your Zebra OEMConfig settings into smaller profiles. For example, create a baseline profile that affects all devices. Then, create more profiles that configure settings specific to a device.
 
-Zebra’s OEMConfig schema also uses **Actions**. Actions are operations that run on the device. They don’t configure any settings. Use these actions to trigger a file download, clear the clipboard, and more. For a full list of the supported actions, see [Zebra’s documentation](https://techdocs.zebra.com/oemconfig/about/) (opens Zebra's web site).
+Zebra’s OEMConfig schema also uses **Actions**. Actions are operations that run on the device. They don’t configure any settings. Use these actions to trigger a file download, clear the clipboard, and more. For a full list of the supported actions, see [Zebra’s documentation](https://techdocs.zebra.com/oemconfig/) (opens Zebra's web site).
 
 For example, you create a Zebra OEMConfig profile that applies some settings to the device. Another Zebra OEMConfig profile includes an action that clears the clipboard. You assign the first profile to a Zebra devices group. Later, you need to clear the clipboard on those devices. You assign the second profile to the same devices group, without changing the first profile. The device clipboard gets cleared without resending or affecting the configuration settings created in the first profile.
 
@@ -60,17 +60,17 @@ Multiple profiles will take longer to deploy than a single profile. If the speed
 
 ## Ordering
 
-With multiple profiles on each device, the order that profiles are deployed isn’t guaranteed. This behavior is a Google Play limitation. To run operations in sequence, you can use [Zebra's Transaction Step feature](https://techdocs.zebra.com/oemconfig/mc/#Transaction-Steps) (opens Zebra's web site). 
+With multiple profiles on each device, the order that profiles are deployed isn’t guaranteed. This behavior is a Google Play limitation. To run operations in sequence, you can use [Zebra's Transaction Step feature](https://techdocs.zebra.com/oemconfig/11-4/mc/#transactionsteps) (opens Zebra's web site). 
 
-To summarize, if order matters, use [Zebra's Transaction Step feature](https://techdocs.zebra.com/oemconfig/mc/#Transaction-Steps) (opens Zebra's web site). If order doesn't matter, use multiple Intune profiles. 
+To summarize, if order matters, use [Zebra's Transaction Step feature](https://techdocs.zebra.com/oemconfig/11-4/mc/#transactionsteps) (opens Zebra's web site). If order doesn't matter, use multiple Intune profiles. 
 
 Let's look at some examples:
 
 - You want to turn on Bluetooth for all newly-enrolled Zebra devices before configuring any other setting on these devices. To run operations in sequence, use the **Steps** feature in Zebra’s schema.
 
   Create one Intune profile that has two Transaction Steps. The first step includes Bluetooth settings, and the second step configures the other setting. When Zebra’s OEMConfig app receives the profile, it runs the steps in order.
 
-  For more information, see [Zebra's transaction steps](https://techdocs.zebra.com/oemconfig/mc/#Transaction-Steps) (opens Zebra's web site).
+  For more information, see [Zebra's transaction steps](https://techdocs.zebra.com/oemconfig/11-4/mc/#transactionsteps) (opens Zebra's web site).
 
 - You want all Zebra devices to display time in 24-hour format. For some of these devices, you want to turn the camera off. The time and camera settings don't depend on each other.
 
diff --git a/memdocs/intune/developer/app-sdk-xamarin.md b/memdocs/intune/developer/app-sdk-xamarin.md
@@ -34,7 +34,7 @@ ms.collection:
 # Microsoft Intune App SDK Xamarin Bindings
 
 > [!NOTE]
-> The current Xamarin bindings for Android platform only support apps targeting Android 9.0 and lower and Xamarin Forms 4.4 and lower. Microsoft is working on improving support for newer versions on Android starting Q2CY2023. More information on the support plan to be provided in Q1CY2023.
+> The current Xamarin bindings for Android platform only support apps targeting Android 9.0 and lower and Xamarin Forms 4.4 and lower. Microsoft is working on improving support for newer versions on Android starting Q2CY2023. We anticipate having a beta release for .NET MAUI support available in March 2023. For more information about migrating your apps from Xamarin Forms to .NET MAUI, see [Migrate your app from Xamarin.Forms](/dotnet/maui/get-started/migrate). 
 
 > [!NOTE]
 > You may wish to first read the [Get Started with Intune App SDK](app-sdk-get-started.md) article, which explains how to prepare for integration on each supported platform.
@@ -84,7 +84,7 @@ for more information.
 * Secure the output directory that contains the Xamarin app. Consider using a user-level directory for the output.
 
 
-## Enabling Intune app protection polices in your iOS mobile app
+## Enabling Intune app protection policies in your iOS mobile app
 
 > [!IMPORTANT]
 > Intune regularly releases updates to the Intune App SDK. Regularly check the [Intune App SDK Xamarin Bindings](https://github.com/msintuneappsdk/intune-app-sdk-xamarin) for updates and incorporate into your software development release cycle to ensure your apps support the latest App Protection Policy settings.
diff --git a/windows-365/enterprise/introduction-windows-365-government.md b/windows-365/enterprise/introduction-windows-365-government.md
@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 11/11/2022
+ms.date: 02/13/2023
 ms.topic: overview
 ms.service: windows-365
 ms.subservice:
@@ -55,6 +55,7 @@ The following features are not yet supported for Windows 365 GCC or GCCH.
 - Windows 365 System based alerting on Microsoft Endpoint Manager for Cloud PCs
 - User initiated feedback in End User Portal and Windows 365 Web Client
 - Resize VM
+- Citrix HDX Plus for Windows 365
 
 ## Next steps
 
diff --git a/windows-365/enterprise/requirements-citrix.md b/windows-365/enterprise/requirements-citrix.md
@@ -7,7 +7,7 @@ keywords:
 author: ErikjeMS  
 ms.author: erikje
 manager: dougeby
-ms.date: 10/12/2022
+ms.date: 02/13/2023
 ms.topic: overview
 ms.service: windows-365
 ms.subservice:
@@ -48,6 +48,7 @@ To use Citrix HDX Plus for Windows 365, you must meet the following requirements
 - For Hybrid Azure Active Directory (Azure AD) joined deployments:
   - The Azure AD domain must be synchronized from the Azure AD domain that the Cloud PCs belong to.
   - Cloud Connectors to allow Citrix Cloud to connect to your Active Directory domain. For more information, see [Citrix Cloud Connector](https://docs.citrix.com/en-us/citrix-cloud/citrix-cloud-resource-locations/citrix-cloud-connector.html).
+- Allowlist endpoint required for VDA registation: \*.apps.cloud.com
 
 ## Microsoft requirements
 
