Merge pull request #217957 from MicrosoftDocs/main

11/10 OOB Publish at 11AM

Author: huypub

articles/active-directory/authentication/concept-registration-mfa-sspr-combined.md

@@ -6,7 +6,7 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: authentication
 ms.topic: conceptual
-ms.date: 09/23/2022
+ms.date: 11/10/2022
 
 ms.author: justinha
 author: justinha
@@ -93,7 +93,7 @@ For both modes, users who have previously registered a method that can be used f
 
 ### Interrupt mode
 
-Combined registration adheres to both multifactor authentication and SSPR policies, if both are enabled for your tenant. These policies control whether a user is interrupted for registration during sign-in and which methods are available for registration. If only an SSPR policy is enabled, then users will be able to skip the registration interruption and complete it at a later time.
+Combined registration adheres to both multifactor authentication and SSPR policies, if both are enabled for your tenant. These policies control whether a user is interrupted for registration during sign-in and which methods are available for registration. If only an SSPR policy is enabled, then users will be able to skip (indefinitely) the registration interruption and complete it at a later time.
 
 The following are sample scenarios where users might be prompted to register or refresh their security info:
 

articles/active-directory/authentication/concept-sspr-policy.md

@@ -6,7 +6,7 @@ services: active-directory
 ms.service: active-directory
 ms.subservice: authentication
 ms.topic: conceptual
-ms.date: 05/04/2022
+ms.date: 11/10/2022
 
 ms.author: justinha
 author: justinha
@@ -51,7 +51,7 @@ The following Azure AD password policy options are defined. Unless noted, you ca
 | Characters allowed |<ul><li>A – Z</li><li>a - z</li><li>0 – 9</li> <li>@ # $ % ^ & * - _ ! + = [ ] { } &#124; \ : ' , . ? / \` ~ " ( ) ; < ></li> <li>blank space</li></ul> |
 | Characters not allowed | Unicode characters. |
 | Password restrictions |<ul><li>A minimum of 8 characters and a maximum of 256 characters.</li><li>Requires three out of four of the following:<ul><li>Lowercase characters.</li><li>Uppercase characters.</li><li>Numbers (0-9).</li><li>Symbols (see the previous password restrictions).</li></ul></li></ul> |
-| Password expiry duration (Maximum password age) |<ul><li>Default value: **90** days.</li><li>The value is configurable by using the `Set-MsolPasswordPolicy` cmdlet from the Azure Active Directory Module for Windows PowerShell.</li></ul> |
+| Password expiry duration (Maximum password age) |<ul><li>Default value: **90** days. If the tenant was created after 2021, it has no default expiration value. You can check current policy with [Get-MsolPasswordPolicy](/powershell/module/msonline/get-msolpasswordpolicy).</li><li>The value is configurable by using the `Set-MsolPasswordPolicy` cmdlet from the Azure Active Directory Module for Windows PowerShell.</li></ul> |
 | Password expiry notification (When users are notified of password expiration) |<ul><li>Default value: **14** days (before password expires).</li><li>The value is configurable by using the `Set-MsolPasswordPolicy` cmdlet.</li></ul> |
 | Password expiry (Let passwords never expire) |<ul><li>Default value: **false** (indicates that password's have an expiration date).</li><li>The value can be configured for individual user accounts by using the `Set-MsolUser` cmdlet.</li></ul> |
 | Password change history | The last password *can't* be used again when the user changes a password. |

articles/azure-maps/weather-coverage.md

@@ -5,7 +5,7 @@ author: yvonne-dq
 ms.author: amiyouss
 ms.service: azure-percept
 ms.topic: overview
-ms.date: 11/09/2022
+ms.date: 11/10/2022
 ---
 
 # Retirement of Azure Percept DK
@@ -36,4 +36,4 @@ If you have questions regarding Azure Percept DK, please refer to the below **FA
 | When is this change occurring?                 | On March 30, 2023. Until this date your DK and Studio will function as-is and updates and customer support will be offered. After this date, all updates and customer support will stop.    | 
 | Will my projects be deleted?                   | Your projects remain in the underlying Azure Services they were created in (example: Custom Vision, Speech Studio, etc.). They won't be deleted due to this retirement. You can no longer modify or use your project with Percept Studio.   | 
 | Do I need to do anything before March 30, 2023?    | Yes, you will need to close the resources and projects associated with the Azure Percept Studio and DK to avoid future billing, as these backend resources and projects will continue to bill after retirement.    | 
-| Will my device still power on?                | The various backend services that allow the DK and Audio Accessory to fully function will be shut down upon retirement, rending the DK and Audio Accessory effectively unusable. The SoMs, such as the camera and Audio Accessory, will no longer be identified by the DK after retirement and thus effectively unusable.  | 
+ 

articles/azure-percept/retirement-of-azure-percept-dk.md

@@ -4,7 +4,7 @@ titleSuffix: Azure Machine Learning
 description: Learn how to attach and manage Spark pools with Azure Synapse 
 author: ynpandey
 ms.author: franksolomon
-ms.reviewer: scottpolly
+ms.reviewer: franksolomon
 ms.service: machine-learning
 ms.subservice: mldata
 ms.topic: how-to 

articles/machine-learning/how-to-manage-synapse-spark-pool.md

@@ -4,7 +4,7 @@ titleSuffix: Azure Machine Learning
 description: Learn how to submit standalone and pipeline Spark jobs in Azure Machine Learning 
 author: ynpandey
 ms.author: franksolomon
-ms.reviewer: scottpolly
+ms.reviewer: franksolomon
 ms.service: machine-learning
 ms.subservice: mldata
 ms.topic: how-to 

articles/machine-learning/how-to-submit-spark-jobs.md

@@ -4,7 +4,7 @@ titleSuffix: Azure Machine Learning
 description: Learn how to use Apache Spark to wrangle data with Azure Machine Learning
 author: ynpandey
 ms.author: franksolomon
-ms.reviewer: scottpolly
+ms.reviewer: franksolomon
 ms.service: machine-learning
 ms.subservice: mldata
 ms.topic: how-to 

articles/machine-learning/interactive-data-wrangling-with-apache-spark-azure-ml.md

@@ -38,8 +38,7 @@ Register each data source with Microsoft Purview to later define access policies
 
 1. **Select a collection** to put this registration in. 
 
-1. Enable Data Use Management. Data Use Management needs certain permissions and can affect the security of your data, as it delegates to certain Microsoft Purview roles to manage access to the data sources. **Go through the secure practices related to Data Use Management in this guide**: [How to enable Data Use Management]
-(./how-to-enable-data-use-management.md)
+1. Enable Data Use Management. Data Use Management needs certain permissions and can affect the security of your data, as it delegates to certain Microsoft Purview roles to manage access to the data sources. **Go through the secure practices related to Data Use Management in this guide**: [How to enable Data Use Management](./how-to-enable-data-use-management.md)
 
 1. Upon enabling Data Use Management, Microsoft Purview will automatically capture the **Application ID** of the App Registration related to this Arc-enabled SQL server. Come back to this screen and hit the refresh button on the side of it to refresh, in case the association between the Arc-enabled SQL server and the App Registration changes in the future.
 

articles/purview/how-to-policies-data-owner-arc-sql-server.md

@@ -56,6 +56,8 @@
     href: stay-informed-security.md 
   - name: Resource health types and checks
     href: resource-health-checks-resource-types.md
+  - name: Impacted Resources Support for Outages
+    href: impacted-resources-outage.md
   - name: Resource Health FAQ
     href: resource-health-faq.yml
   - name: Resource Health VM status annotations

articles/service-health/TOC.yml

@@ -0,0 +1,80 @@
+---
+title: Impacted resources support for outages
+description: This article details what is communicated to users and where they can view information about their impacted resources.
+ms.topic: conceptual
+ms.date: 11/9/2022
+---
+
+# Impacted Resources for Azure Outages
+
+[Azure Service Health](https://azure.microsoft.com/get-started/azure-portal/service-health/) helps customers view any health events that impact their Subscriptions and Tenants. The Service Issues blade on Service Health shows any ongoing problems in Azure services that are impacting your resources. You can understand when the issue began, and what services and regions are impacted. Previously, the Potential Impact tab on the Service Issues blade was within the details of an incident. It showed any resources under a customer's Subscriptions or Tenants that may be impacted by an outage, and their resource health signal to help customers evaluate impact.
+
+**In support of the impacted resource experience, Service Health has enabled a new feature to:**
+
+- Replace “Potential Impact” tab with “Impacted Resources” tab on Service Issues.
+- Display resources that are confirmed to be impacted by an outage.
+- Display resources that are not confirmed to be impacted by an outage but could be impacted because they fall under a service or region that is confirmed to be impacted by an outage.
+- Resource Health status of both confirmed and potential impacted resources showing the availability of the resource.
+
+This article details what is communicated to users and where they can view information about their impacted resources.
+
+>[!Note]
+>This feature will be enabled to users in phases. Only selected subscription-level customers will start seeing the experience initially and gradually expand to 100% of subscription customers. In future this capability will be live for tenant level customers.
+
+## Impacted Resources for Outages on the Service Health Portal
+
+The impacted resources tab under Azure portal-> Service Health ->Service Issues will display resources that are Confirmed to be impacted by an outage and resources that could Potentially be impacted by an outage. Below is an example of impacted resources tab for an incident on Service Issues with Confirmed and Potential impact resources.
+
+:::image type="content" source="./media/impacted-resource-outage/ir-portal.PNG" alt-text="Screenshot of Azure Service Health impacted resources information.":::
+
+##### Service Health provides the below information to users whose resources are impacted by an outage:
+
+|Column  |Description |
+|---------|---------|
+|Resource Name|Name of resource|
+|Resource Health|Health status of a resource at that point in time|
+|Impact Type|Tells customers if their resource is confirmed to be impacted or potentially impacted|
+|Resource Type|Type of resource impacted (.ie Virtual Machines)|
+|Resource Group|Resource group which contains the impacted resource|
+|Location|Location which contains the impacted resource|
+|Subscription ID|Unique ID for the subscription that contains the impacted resource|
+|Subscription Name|Subscription name for the subscription which contains the impacted resource|
+|Tenant ID|Unique ID for the tenant that contains the impacted resource|
+
+## Resource Name
+
+This will be the resource name of the resource. The resource name will be a clickable link that links to Resource Health page for this resource.
+
+It will be text only if there is no Resource Health signal available for this resource.
+
+## Impact Type
+
+This column will display values “Confirmed vs Potential”
+
+- *Confirmed*: Resource that was confirmed to be impacted by an outage. Customers should check the Summary section to make sure customer action items (if any) are taken to remediate the issue.
+- *Potential*: Resource that is not confirmed to be impacted by an outage but could potentially be impacted as it is under a service or region which is impacted by an outage. Customers are advised to look at the resource health and make sure everything is working as planned.
+
+## Resource Health
+
+The health status listed under **[Resource Health](../service-health/resource-health-overview.md)** refers to the status of a given resource at that point in time.
+
+- A health status of available means your resource is healthy but it may have been affected by the service event at a previous point in time.
+- A health status of degraded or unavailable (caused by a customer-initiated action or platform-initiated action) means your resource is impacted but could be now healthy and pending a status update.
+
+:::image type="content" source="./media/impacted-resource-outage/icons.PNG" alt-text="Screenshot of Impacted Resources health status icons and impact type":::
+
+
+>[!Note]
+>Not all resources will show resource health status. This will be shown on resources for which we have a resource health signal available only. The status of resources where the health signal is not available is shown as **“N/A”** and corresponding Resource name value will be text only not a clickable link.
+
+## Filters
+
+Customers can filter on the results using the below filters:
+
+- Impact type: Confirmed or Potential
+- Subscription ID: All Subscription IDs the user has access to
+- Status: Resource Health status column that shows Available, Unavailable, Degraded, Unknown, N/A
+
+## Export to CSV
+
+The list of impacted resources can be exported to an excel file by clicking on this option.