Merge pull request #8568 from MicrosoftDocs/main

Publish main to live on 9/28 @ 10:30 am

Author: v-stsavell

memdocs/get-support.md

@@ -119,9 +119,6 @@ You can use filters for all compliance policies on the following platforms:
 - macOS
 - Windows 10 and later
 
-[!NOTE]
-> The Custom compliance (preview) feature for Windows 10 and later devices is not currently supported. If you assign a policy with custom compliance settings, targeted users and devices will process the policy and ignore assignment filering.
-
 ## Device configuration profiles and Endpoint security
 
 You can use filters for some common device configuration policies on the following platforms. For a list of what's not supported, see [not supported](#not-supported) (in this article).

memdocs/intune/fundamentals/filters-supported-workloads.md

@@ -291,14 +291,6 @@ Features of the reusable settings groups will include:
 
 Reusable groups will be configured on a new Tab for *Reusable settings* that will be available when you view endpoint security Firewall policy.  In the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431) > **Endpoint security** > **Firewall**.
 
-<!-- ***********************************************-->
-
-## Monitor and troubleshoot
-
-### Open Help and Support without losing your context in the Microsoft Endpoint Manager admin center<!-- 12469338 -->
-You’ll soon be able to use the **?** icon in the Microsoft Endpoint Manager admin center to  open a help and support session without losing your current node of focus in the admin center. The **?** icon is always available in the upper right of the admin center title bar. This change will add an additional method for accessing *Help and support*.
-
-When you select  **?**, the admin center will open a new and separate side-by-side pane you use to navigate the support experience. By opening this separate pane, you’ll be free to navigate the support experience without affecting your original location and focus on the admin center. You will however be free to navigate through the admin center in that original pane if you choose.
 
 <!-- ***********************************************-->
 

memdocs/intune/fundamentals/in-development.md

@@ -61,6 +61,15 @@ You can use RSS to be notified when this page is updated. For more information,
 ### Scripts
 ### Tenant administration
 -->
+## Week of September 26, 2022
+
+### Monitor and troubleshoot
+
+#### Open Help and Support without losing your context in the Microsoft Endpoint Manager admin center<!-- 12469338 -->
+
+You can now use the **?** icon in the Microsoft Endpoint Manager admin center to open a [help and support](../../get-support.md) session without losing your current node of focus in the admin center. The **?** icon is always available in the upper right of the title bar of the admin center. This change adds an additional method for accessing *Help and support*.
+
+When you select **?**, the admin center opens the help and support view in a new and separate side-by-side pane. By opening this separate pane, you’ll be free to navigate the support experience without affecting your original location and focus on the admin center.
 
 ## Week of September 19, 2022 (Service release 2209)
 

memdocs/intune/fundamentals/whats-new.md

@@ -222,9 +222,8 @@ Policy conflicts can occur when multiple Intune policies are applied to a device
 
 - If you have deployed multiple compliance policies, Intune uses the most secure of these policies.
 
-## Next steps
-
-[Compliance policies overview](device-compliance-get-started.md)
-
+To learn more about conflict resolution for policies, see [If multiple policies are assigned to the same user or device, how do I know which settings gets applied?](../configuration/device-profile-troubleshoot.md#if-multiple-policies-are-assigned-to-the-same-user-or-device-how-do-i-know-which-settings-gets-applied).
 
+## Next steps
 
+[Compliance policies overview](device-compliance-get-started.md)

memdocs/intune/protect/compliance-policy-monitor.md

@@ -37,14 +37,16 @@ Compliance policies in Intune:
 - Define the rules and settings that users and devices must meet to be compliant.
 - Include actions that apply to devices that are noncompliant. Actions for noncompliance can alert users to the conditions of noncompliance and safeguard data on noncompliant devices.
 - Can be [combined with Conditional Access](#integrate-with-conditional-access), which can then block users and devices that don't meet the rules.
+- Can override the configuration of settings that you also manage through device configuration policies. To learn more about conflict resolution for policies, see [If multiple policies are assigned to the same user or device, how do I know which settings gets applied?](../configuration/device-profile-troubleshoot.md#if-multiple-policies-are-assigned-to-the-same-user-or-device-how-do-i-know-which-settings-gets-applied).
 
 There are two parts to compliance policies in Intune:
 
 - **Compliance policy settings** – Tenant-wide settings that are like a built-in compliance policy that every device receives. Compliance policy settings set a baseline for how compliance policy works in your Intune environment, including whether devices that haven’t received any device compliance policies are compliant or noncompliant.
 
 - **Device compliance policy** – Platform-specific rules you configure and deploy to groups of users or devices.  These rules define requirements for devices, like minimum operating systems or the use of disk encryption. Devices must meet these rules to be considered compliant.
 
-Like other Intune policies, compliance policy evaluations for a device depend on when the device checks-in with Intune, and [policy and profile refresh cycles](../configuration/device-profile-troubleshoot.md#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned).
+Like other Intune policies, compliance policy evaluations for a device depend on when the device checks-in with Intune, and [policy and profile refresh cycles](../configuration/device-profile-troubleshoot.md#how-long-does-it-take-for-devices-to-get-a-policy-profile-or-app-after-they-are-assigned). 
+ 
 
 ## Compliance policy settings
 

memdocs/intune/protect/device-compliance-get-started.md

@@ -232,7 +232,6 @@ When creating the Server configuration for the tunnel, you can specify a differe
   - Security Token Service: `*.sts.windows.net`
   - Azure storage for tunnel logs: `*.blob.core.windows.net`
   - Additional storage endpoint urls: 
-  - `*.mwh03prdstr02a.store.core.windows.net`
   - `*.blob.storage.azure.net`
 
 

memdocs/intune/protect/microsoft-tunnel-prerequisites.md

@@ -144,6 +144,21 @@ After an update releases, it rolls out to tenants over the following days. This
 
 The Microsoft Tunnel version for a server isn’t available in the Intune UI at this time. Instead, run the following command on the Linux server that hosts the tunnel to identify the hash values of  *agentImageDigest* and *serverImageDiegest*: `cat /etc/mstunnel/images_configured`
 
+### September 23, 2022
+
+Image hash values:
+
+- **agentImageDigest**:  sha256:df03d4ad8469511a4b649dcbbad5dbaa5c7f10cdc9640b7801190623090a67ae
+
+- **serverImageDigest**: sha256:0f66f2b5463e283c1621fc4250f69fac97ebda77bef8f570ed181b78000d762c
+
+Changes in this release:
+- Minor bug fixes
+- Security improvements
+- Mst-readiness script enhancements
+- Add Azure storage endpoint 
+
+
 ### August 22, 2022
 
 Image hash values: