Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into ip-multi-vm-config

Author: asudbring

articles/active-directory/cloud-infrastructure-entitlement-management/TOC.yml

@@ -8,6 +8,8 @@
   - name: How-to guides
     expanded: true
     items:
+    - name: Trial Playbook - Microsoft Entra Permissions Management
+      href: permissions-management-trial-playbook.md  
     - name: Onboard Permissions Management on the Azure AD tenant
       expanded: true
       items:

articles/active-directory/cloud-infrastructure-entitlement-management/media/permissions-management-trial-playbook/custom-alerts-1.png

@@ -106,7 +106,6 @@ The following features are supported for Linux containers:
 - Mapping `/mounts`, `mounts/foo/bar`, `/`, and `/mounts/foo.bar/` to custom-mounted storage is not supported (you can only use /mounts/pathname for mounting custom storage to your web app.)
 - Storage mounts cannot be used together with clone settings option during [deployment slot](deploy-staging-slots.md) creation.
 - Storage mounts are not backed up when you [back up your app](manage-backup.md). Be sure to follow best practices to back up the Azure Storage accounts. 
-- Only Azure Files [SMB](../storage/files/files-smb-protocol.md) are supported.  Azure Files [NFS](../storage/files/files-nfs-protocol.md) is not currently supported for Linux App Services.
 
 ::: zone-end
 
@@ -118,7 +117,7 @@ The following features are supported for Linux containers:
 - FTP/FTPS access to mounted storage not supported (use [Azure Storage Explorer](https://azure.microsoft.com/features/storage-explorer/)).
 - Mapping `[C-Z]:\`, `[C-Z]:\home`, `/`, and `/home` to custom-mounted storage is not supported.
 - Storage mounts cannot be used together with clone settings option during [deployment slot](deploy-staging-slots.md) creation.
-- Storage mounts are not backed up when you [back up your app](manage-backup.md). Be sure to follow best practices to back up the Azure Storage accounts. 
+- Storage mounts are not backed up when you [back up your app](manage-backup.md). Be sure to follow best practices to back up the Azure Storage accounts.
 
 > [!NOTE]
 > Ensure ports 80 and 445 are open when using Azure Files with VNET integration.
@@ -134,6 +133,7 @@ The following features are supported for Linux containers:
 - Don't map the custom storage mount to `/tmp` or its subdirectories as this may cause timeout during app startup.
 - Storage mounts cannot be used together with clone settings option during [deployment slot](deploy-staging-slots.md) creation.
 - Storage mounts are not backed up when you [back up your app](manage-backup.md). Be sure to follow best practices to back up the Azure Storage accounts. 
+- Only Azure Files [SMB](../storage/files/files-smb-protocol.md) are supported.  Azure Files [NFS](../storage/files/files-nfs-protocol.md) is not currently supported for Linux App Services.
 
 > [!NOTE]
 > When VNET integration is used, ensure the following ports are open:
@@ -343,4 +343,4 @@ To validate that the Azure Storage is mounted successfully for the app:
 - [Configure a custom container](configure-custom-container.md?pivots=platform-linux).
 - [Video: How to mount Azure Storage as a local share](https://www.youtube.com/watch?v=OJkvpWYr57Y).
 
-::: zone-end
+::: zone-end

articles/active-directory/cloud-infrastructure-entitlement-management/media/permissions-management-trial-playbook/custom-alerts-2.png

@@ -57,15 +57,15 @@ items:
   - name: Migrate to Form Recognizer v3.0
     displayName: get started, confidence, bounding box, boundingBox, polygon, analyze, AnalyzeResult, train, build, sas, compose, copy
     href: v3-migration-guide.md
-  - name: Use the prebuilt-read model
+  - name: Use the prebuilt-read model (v3.0)
     displayName: documentAnalysisClient, document analysis client, AnalyzeResult, analyze, output
     href: how-to-guides/use-prebuilt-read.md
-  - name: Use SDKs and the REST API (v2.1)
-    displayName: formRecognizerClient, form recognizer client, boundingBox, bounding box, begin_analyze
-    href: how-to-guides/try-sdk-rest-api.md
   - name: Create SAS tokens for storage containers
     displayName: blob, delegation, shared, explorer
     href:  create-sas-tokens.md
+  - name: Use SDKs and the REST API (v2.1)
+    displayName: formRecognizerClient, form recognizer client, boundingBox, bounding box, begin_analyze
+    href: how-to-guides/try-sdk-rest-api.md
   - name: Custom models
     items:
     - name: Build a custom model (v3.0)
@@ -222,27 +222,27 @@ items:
     href: tutorial-azure-function.md
 - name: Reference
   items:
-  - name: Azure Form Recognizer REST API v3.0
+  - name: Azure Form Recognizer REST API v3.0 (GA)
     items:
     - name: REST API v3.0 reference
       href: https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-2022-08-31/operations/AnalyzeDocument
-    - name: Client libraries and SDKs
+    - name: Error codes and messages v3.0
+      href: v3-error-guide.md
+    - name: Supported REST API v3.0 SDKs
       items:
       - name: .NET
-        href: https://azuresdkdocs.blob.core.windows.net/$web/dotnet/Azure.AI.FormRecognizer/4.0.0-beta.4/index.html
-      - name: Python
-        href: https://azuresdkdocs.blob.core.windows.net/$web/python/azure-ai-formrecognizer/3.2.0b5/index.html
+        href: https://azure.github.io/azure-sdk/releases/latest/dotnet.html
       - name: Java
-        href: https://azuresdkdocs.blob.core.windows.net/$web/java/azure-ai-formrecognizer/4.0.0-beta.5/index.html
+        href: https://azure.github.io/azure-sdk/releases/latest/java.html
       - name: JavaScript
-        href: https://azuresdkdocs.blob.core.windows.net/$web/javascript/azure-ai-form-recognizer/4.0.0-beta.4/index.html
-  - name: Error codes and messages v3.0
-    href: v3-error-guide.md
-  - name: Azure Form Recognizer REST API v2.1
+        href: https://azure.github.io/azure-sdk/releases/latest/js.html
+      - name: Python
+        href: https://azure.github.io/azure-sdk/releases/latest/python.html
+  - name: Azure Form Recognizer REST API v2.1 (GA)
     items:
     - name: REST API v2.1 reference
       href: https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v2-1/operations/AnalyzeWithCustomForm
-    - name: Client libraries and SDKs
+    - name: Supported REST API v2.1 SDKs
       items:
       - name: .NET
         href: /dotnet/api/overview/azure/ai.formrecognizer-readme
@@ -252,18 +252,10 @@ items:
         href: /java/api/overview/azure/ai-formrecognizer-readme
       - name: JavaScript
         href: /javascript/api/overview/azure/ai-form-recognizer-readme
-  - name: Azure Form Recognizer REST API v2.0
-    items:
-    - name: REST API v2.0 reference
-      href: https://westus2.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v2/operations/AnalyzeWithCustomForm
-    - name: SDK guide
-      href: api-v2-0/reference-sdk-api-v2-0.md
 - name: Resources
   items:
   - name:  Customer spotlight
     href: resource-customer-stories.md
-  - name: Azure roadmap
-    href: https://azure.microsoft.com/updates/?product=cognitive-services
   - name: Enterprise readiness
     items:
     - name: Region support

articles/active-directory/cloud-infrastructure-entitlement-management/media/permissions-management-trial-playbook/custom-alerts-3.png

@@ -181,7 +181,7 @@ The `useTrackEvent` Hook is used to track any custom event that an application m
 -   Application Insights instance (which can be obtained from the `useAppInsightsContext` Hook).
 -   Name for the event.
 -   Event data object that encapsulates the changes that has to be tracked.
--   skipFirstRun (optional) flag to skip calling the `trackEvent` call on initialization. Default value is set to `true`.
+-   skipFirstRun (optional) flag to skip calling the `trackEvent` call on initialization. Default value is set to `true` to mimic more closely the way the non-hook version works. With `useEffect` hooks, the effect is triggered on each value update _including_ the initial setting of the value, thereby starting the tracking too early causing potentially unwanted events to be tracked.
 
 ```javascript
 import React, { useState, useEffect } from "react";