Merging changes synced from https://github.com/MicrosoftDocs/azure-docs-pr (branch live)

Author: Banani-Rath

.openpublishing.redirection.json

@@ -9,6 +9,11 @@
             "source_path_from_root": "/articles/api-management/developer-portal-use-community-widgets.md",
             "redirect_url": "/azure/api-management/developer-portal-extend-custom-functionality",
             "redirect_document_id": false
+        },       
+        {
+            "source_path":  "articles/sentinel/whats-new-archive.md",
+            "redirect_url":  "/azure/sentinel/whats-new",
+            "redirect_document_id":  false   
         },
         {
             "source_path":  "articles/backup/sap-hana-db-manage.md",

articles/active-directory/develop/app-objects-and-service-principals.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: develop
 ms.topic: conceptual
 ms.workload: identity
-ms.date: 07/20/2022
+ms.date: 11/02/2022
 ms.author: ryanwi
 ms.custom: contperf-fy21q4-portal, aaddev, identityplatformtop40
 ms.reviewer: sureshja

articles/active-directory/develop/application-model.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: develop
 ms.topic: conceptual
 ms.workload: identity
-ms.date: 09/27/2021
+ms.date: 11/02/2022
 ms.author: ryanwi
 ms.reviewer: jmprieur, saeeda, sureshja, ludwignick
 ms.custom: aaddev, identityplatformtop40, scenarios:getting-started

articles/active-directory/develop/authentication-vs-authorization.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: develop
 ms.topic: conceptual
 ms.workload: identity
-ms.date: 08/26/2022
+ms.date: 11/02/2022
 ms.author: ryanwi
 ms.reviewer: jmprieur, saeeda, sureshja, ludwignick
 ms.custom: aaddev, identityplatformtop40, scenarios:getting-started

articles/active-directory/develop/howto-modify-supported-accounts.md

@@ -9,10 +9,10 @@ ms.service: active-directory
 ms.subservice: develop
 ms.topic: how-to
 ms.workload: identity
-ms.date: 11/15/2020
+ms.date: 11/02/2022
 ms.author: ryanwi
 ms.custom: aaddev
-ms.reviewer: marsma, aragra, lenalepa, sureshja
+ms.reviewer: aragra, sureshja
 # Customer intent: As an application developer, I need to know how to modify which account types can sign in to or access my application or API.
 ---
 
@@ -33,14 +33,17 @@ To specify a different setting for the account types supported by an existing ap
 1. Sign in to the <a href="https://portal.azure.com/" target="_blank">Azure portal</a>.
 1. If you have access to multiple tenants, use the **Directories + subscriptions** filter :::image type="icon" source="./media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to switch to the tenant in which the app is registered.
 1. Search for and select **Azure Active Directory**.
-1. Under **Manage**, select **App registrations**, then select your application.
-1. Now, specify who can use the application, sometimes referred to as the *sign-in audience*.
-
-    | Supported account types | Description |
-    |-------------------------|-------------|
-    | **Accounts in this organizational directory only** | Select this option if you're building an application for use only by users (or guests) in *your* tenant.<br><br>Often called a *line-of-business* (LOB) application, this is a **single-tenant** application in the Microsoft identity platform. |
-    | **Accounts in any organizational directory** | Select this option if you'd like users in *any* Azure AD tenant to be able to use your application. This option is appropriate if, for example, you're building a software-as-a-service (SaaS) application that you intend to provide to multiple organizations.<br><br>This is known as a **multi-tenant** application in the Microsoft identity platform. |
-1. Select **Save**.
+1. Under **Manage**, select **App registrations**, select your application, and then select **Manifest** to use the manifest editor.
+1. Download the manifest JSON file locally.
+1. Now, specify who can use the application, sometimes referred to as the *sign-in audience*.  Find the *signInAudience* property in the manifest JSON file and set it to one of the following property values:
+
+    | Property value | Supported account types | Description |
+    |----------------|-------------------------|-------------|
+    | **AzureADMyOrg** | Accounts in this organizational directory only (Microsoft only - Single tenant) |All user and guest accounts in your directory can use your application or API. Use this option if your target audience is internal to your organization. |
+    | **AzureADMultipleOrgs** | Accounts in any organizational directory (Any Azure AD directory - Multitenant) | All users with a work or school account from Microsoft can use your application or API. This includes schools and businesses that use Office 365. Use this option if your target audience is business or educational customers and to enable multitenancy. |
+    | **AzureADandPersonalMicrosoftAccount** | Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox) | All users with a work or school, or personal Microsoft account can use your application or API. It includes schools and businesses that use Office 365 as well as personal accounts that are used to sign in to services like Xbox and Skype. Use this option to target the widest set of Microsoft identities and to enable multitenancy.|
+    | **PersonalMicrosoftAccount** | Personal Microsoft accounts only | Personal accounts that are used to sign in to services like Xbox and Skype. Use this option to target the widest set of Microsoft identities.|
+1. Save your changes to the JSON file locally, then select **Upload** in the manifest editor to upload the updated manifest JSON file.
 
 ### Why changing to multi-tenant can fail
 

articles/active-directory/develop/single-and-multi-tenant-apps.md

@@ -9,7 +9,7 @@ ms.service: active-directory
 ms.subservice: develop
 ms.topic: conceptual
 ms.workload: identity
-ms.date: 10/13/2021
+ms.date: 11/02/2022
 ms.author: ryanwi
 ms.reviewer: justhu
 ms.custom: aaddev

articles/active-directory/develop/workload-identities-overview.md

@@ -7,7 +7,7 @@ ms.service: active-directory
 ms.subservice: develop
 ms.workload: identity
 ms.topic: conceptual
-ms.date: 12/06/2021
+ms.date: 11/02/2022
 ms.author: ryanwi
 ms.reviewer: udayh, ilanas
 ms.custom: aaddev 

articles/advisor/advisor-how-to-performance-resize-high-usage-vm-recommendations.md

@@ -0,0 +1,68 @@
+---
+author: madewithsmiles
+ms.author: ngdiarra
+title: Improve the performance of highly used VMs using Azure Advisor
+description: Use Azure Advisor to improve the performance of your Azure virtual machines with consistent high utilization.
+ms.topic: article
+ms.date: 10/27/2022
+---
+
+# Improve the performance of highly used VMs using Azure Advisor
+
+Azure Advisor helps you improve the speed and responsiveness of your business-critical applications. You can get performance recommendations from the **Performance** tab on the Advisor dashboard.
+
+1. Sign in to the [**Azure portal**](https://portal.azure.com).
+
+1. Search for and select [**Advisor**](https://aka.ms/azureadvisordashboard) from any page.
+
+1. On the **Advisor** dashboard, select the **Performance** tab.
+
+## Optimize virtual machine (VM) performance by right-sizing highly utilized instances 
+
+You can improve the quality of your workload and prevent many performance-related issues (i.e., throttling, high latency) by regularly assessing your [performance efficiency](/azure/architecture/framework/scalability/overview). Performance efficiency is defined by the [Azure Well-Architected Framework](/azure/architecture/framework/) as the ability of your workload to adapt to changes in load. Performance efficiency is one of the five pillars of architectural excellence on Azure.  
+
+Unless by design, we recommend keeping your application's usage well below your virtual machine's size limits, so it can better operate and easily accommodate changes.
+
+Advisor aggregates various metrics over a minimum of 7 days, identifies virtual machines with consistent high utilization across those metrics, and finds better sizes (SKUs) for improved performance. Finally, Advisor examines capacity signals in Azure to frequently refresh the recommended SKUs, ensuring that they are available for deployment in the region.
+
+### Resize SKU recommendations
+
+Advisor recommends resizing virtual machines when use is consistently high (above predefined thresholds) given the running virtual machine's size limits.
+
+-	The recommendation algorithm evaluates **CPU**, **Memory**, **VM Cached IOPS Consumed Percentage**, and **VM Uncached Bandwidth Consumed Percentage** usage metrics
+- The observation period is the past 7 days from the day of the recommendation
+- Metrics are sampled every 30 seconds, aggregated to 1 minute and then further aggregated to 30 minutes (taking the average of 1-minute average values while aggregating to 30 minutes)
+- A SKU upgrade for virtual machines is decided given the following criteria: 
+  - For each metric, we create a new feature from the P50 (median) of its 30-mins averages aggregated over the observation period. Therefore, a virtual machine is identified as a candidate for a resize if:
+    * _Both_ `CPU` and `Memory` features are >= *90%* of the current SKU's limits
+    * Otherwise, _either_ 
+        * The `VM Cached IOPS` feature is >= to *95%* of the current SKU's limits, and the current SKU's max local disk IOPS is >= to its network disk IOPS. _or_
+        * the `VM Uncached Bandwidth` feature is >= *95%* of the current SKU's limits, and the current SKU's max network disk throttle limits are >= to its local disk throttle units  
+- We ensure the following:
+  - The current workload utilization will be better on the new SKU's given that it has higher limits and better performance guarantees
+  - The new SKU has the same Accelerated Networking and Premium Storage capabilities 
+  - The new SKU is supported and ready for deployment in the same region as the running virtual machine
+
+
+In some cases, recommendations can't be adopted or might not be applicable, such as some of these common scenarios (there may be other cases):
+- The virtual machine is short-lived
+- The current virtual machine has already been provisioned to accommodate upcoming traffic
+- Specific testing being done using the current SKU, even if not utilized efficiently
+- There's a need to keep the virtual machine as-is
+
+In such cases, simply use the Dismiss/Postpone options associated with the recommendation. 
+
+We're constantly working on improving these recommendations. Feel free to share feedback on [Advisor Forum](https://aka.ms/advisorfeedback).
+
+## Next steps
+
+To learn more about Advisor recommendations and best practices, see:
+* [Get started with Advisor](advisor-get-started.md)
+* [Introduction to Advisor](advisor-overview.md)
+* [Advisor score](azure-advisor-score.md)
+* [Advisor performance recommendations](advisor-reference-performance-recommendations.md)
+* [Advisor cost recommendations (full list)](advisor-reference-cost-recommendations.md)
+* [Advisor reliability recommendations](advisor-reference-reliability-recommendations.md)
+* [Advisor security recommendations](advisor-security-recommendations.md)
+* [Advisor operational excellence recommendations](advisor-reference-operational-excellence-recommendations.md)
+* [The Microsoft Azure Well-Architected Framework](/azure/architecture/framework/)

articles/advisor/advisor-reference-performance-recommendations.md

@@ -247,6 +247,12 @@ Ultra disk is available in the same region as your database workload. Ultra disk
 
 Learn more about [Virtual machine - AzureStorageVmUltraDisk (Take advantage of Ultra Disk low latency for your log disks and improve your database workload performance.)](../virtual-machines/disks-enable-ultra-ssd.md?tabs=azure-portal).
 
+### Upgrade the size of your virtual machines close to resource exhaustion
+
+We analyzed data for the past 7 days and identified virtual machines (VMs) with high utilization across different metrics (i.e., CPU, Memory, and VM IO). Those VMs may experience performance issues since they are nearing/at their SKU's limits. Consider upgrading their SKU to improve performance.
+
+Learn more about [Virtual machine - Improve the performance of highly used VMs using Azure Advisor](https://aka.ms/aa_resizehighusagevmrec_learnmore)
+
 ## Kubernetes
 
 ### Unsupported Kubernetes version is detected

articles/advisor/toc.yml

@@ -46,6 +46,8 @@
     href: advisor-cost-recommendations.md
   - name: Improve security
     href: advisor-security-recommendations.md
+  - name: Improve the performance of highly used VMs
+    href: advisor-how-to-performance-resize-high-usage-vm-recommendations.md
   - name: Use tags to filter recommendations and score
     href: advisor-tag-filtering.md
   - name: Configure recommendations