Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into heidist-privacy

Author: HeidiSteen

articles/azure-monitor/agents/azure-monitor-agent-data-collection-endpoint.md

@@ -4,7 +4,7 @@ description: Define network settings and enable network isolation for Azure Moni
 ms.topic: conceptual
 author: shseth
 ms.author: shseth
-ms.date: 11/01/2022
+ms.date: 12/19/2022
 ms.custom: references_region
 ms.reviewer: shseth
 
@@ -47,7 +47,7 @@ The Azure Monitor Agent extensions for Windows and Linux can communicate either
     ![Diagram that shows a flowchart to determine the values of settings and protectedSettings parameters when you enable the extension.](media/azure-monitor-agent-overview/proxy-flowchart.png)
 
     > [!NOTE]
-    > Azure Monitor Agent for Linux doesn't support system proxy via environment variables such as `http_proxy` and `https_proxy`.
+    > Setting Linux system proxy via environment variables such as `http_proxy` and `https_proxy` is only supported using Azure Monitor Agent for Linux version 1.24.2 and above.
 
 1. After you determine the `Settings` and `ProtectedSettings` parameter values, provide these other parameters when you deploy Azure Monitor Agent. Use PowerShell commands, as shown in the following examples:
 

articles/azure-monitor/agents/azure-monitor-agent-extension-versions.md

@@ -4,7 +4,7 @@ description: This article describes the version details for the Azure Monitor ag
 ms.topic: conceptual
 author: shseth
 ms.author: shseth
-ms.date: 11/14/2022
+ms.date: 12/19/2022
 ms.custom: references_region
 ms.reviewer: shseth
 
@@ -20,7 +20,7 @@ We strongly recommended to update to the latest version at all times, or opt in
 ## Version details
 | Release Date | Release notes | Windows | Linux |
 |:---|:---|:---|:---|
-| Oct 2022 | <ul><li>Increased default retry timeout for data upload from 4 to 8 hours</li><li>Data quality improvements</li></ul>  | 1.10.0.0 | None | 
+| Oct 2022 | **Windows** <ul><li>Increased default retry timeout for data upload from 4 to 8 hours</li><li>Data quality improvements</li></ul> **Linux** <ul><li>Support for `http_proxy` and `https_proxy` environment variables for [network proxy configurations](./azure-monitor-agent-data-collection-endpoint.md#proxy-configuration) for the agent</li><li>[Text logs](./data-collection-text-log.md) <ul><li>Network proxy support enabled</li><li>Fixed missing `_ResourceId`</li><li>Increased maximum line size support to 1MB</li></ul></li><li>Support ingestion of syslog events whose timestamp is in the future</li><li>Performance improvements</li><li>Fixed `diskio` metrics instance name dimension to use the disk mount path(s) instead of the device name(s)</li></ul>  | 1.10.0.0 | 1.24.2 | 
 | Sep 2022 | Reliability improvements | 1.9.0.0 | None | 
 | August 2022 | **Common updates** <ul><li>Improved resiliency: Default lookback (retry) time updated to last 3 days (72 hours) up from 60 minutes, for agent to collect data post interruption. This is subject to default offline cache size of 10gigabytes</li><li>Fixes the preview custom text log feature that was incorrectly removing the *TimeGenerated* field from the raw data of each event. All events are now additionally stamped with agent (local) upload time</li><li>Reliability and supportability improvements</li></ul> **Windows** <ul><li>Fixed datetime format to UTC</li><li>Fix to use default location for firewall log collection, if not provided</li><li>Reliability and supportability improvements</li></ul> **Linux** <ul><li>Support for OpenSuse 15, Debian 11 ARM64</li><li>Support for coexistence of Azure Monitor agent with legacy Azure Diagnostic extension for Linux (LAD)</li><li>Increased max-size of UDP payload for Telegraf output to prevent dimension truncation</li><li>Prevent unconfigured upload to Azure Monitor Metrics destination</li><li>Fix for disk metrics wherein *instance name* dimension will use the disk mount path(s) instead of the device name(s), to provide parity with legacy agent</li><li>Fixed *disk free MB* metric to report megabytes instead of bytes</li></ul> | 1.8.0.0 | 1.22.2 |
 | July 2022 | Fix for mismatch event timestamps for Sentinel Windows Event Forwarding | 1.7.0.0 | None |

articles/azure-video-indexer/.openpublishing.redirection.azure-video-indexer.json

@@ -122,7 +122,7 @@
         },
         {
             "source_path_from_root": "/articles/azure-video-analyzer/video-analyzer-for-media-docs/invite-users.md",
-            "redirect_url": "/azure/azure-video-indexer/invite-users",
+            "redirect_url": "/azure/azure-video-indexer/restricted-viewer-role",
             "redirect_document_id": false
         },
         {
@@ -249,6 +249,11 @@
             "source_path_from_root": "/articles/azure-video-indexer/compliance-privacy-security.md",
             "redirect_url": "/azure/azure-video-indexer/video-indexer-overview",
             "redirect_document_id": false
-        }
+        },
+        {
+            "source_path_from_root": "/articles/azure-video-indexer/invite-users.md",
+            "redirect_url": "/azure/azure-video-indexer/restricted-viewer-role",
+            "redirect_document_id": false
+        }        
     ]
 }

articles/azure-video-indexer/accounts-overview.md

@@ -53,7 +53,7 @@ When creating a new paid account, you need to connect the Azure Video Indexer ac
 |   | ARM-based |Classic| Trial|
 |---|---|---|---|
 |Get access token | [ARM REST API](https://aka.ms/avam-arm-api) |[Get access token](https://api-portal.videoindexer.ai/api-details#api=Operations&operation=Get-Account-Access-Token)|Same as classic|
-|Share account| [Azure RBAC(role based access control)](../role-based-access-control/overview.md)| [Invite users](invite-users.md) |Same as classic|
+|Share account| [Azure RBAC(role based access control)](../role-based-access-control/overview.md)| [Invite users](restricted-viewer-role.md#share-the-account) |Same as classic|
 
 ## Limited access features
 

articles/azure-video-indexer/connect-classic-account-to-arm.md

@@ -32,7 +32,7 @@ Connecting a classic account to be ARM-based triggers a 30 days of a transition
 
 The transition state moves all account management functionality to be managed by ARM and will be handled by [Azure RBAC][docs-rbac-overview]. 
 
-The [invite users](invite-users.md) feature in the [Azure Video Indexer website](https://www.videoindexer.ai/) gets disabled. The invited users on this account lose their access to the Azure Video Indexer account Media in the portal.  
+The [invite users](restricted-viewer-role.md#share-the-account) feature in the [Azure Video Indexer website](https://www.videoindexer.ai/) gets disabled. The invited users on this account lose their access to the Azure Video Indexer account Media in the portal.  
 However, this can be resolved by assigning the right role-assignment to these users through Azure RBAC, see [How to assign RBAC][docs-rbac-assignment]. 
 
 Only the account owner, who performed the connect action, is automatically assigned as the owner on the connected account. When [Azure policies][docs-governance-policy] are enforced, they override the settings on the account.

articles/azure-video-indexer/index.yml

@@ -42,8 +42,6 @@ landingContent:
         links: 
           - text: Sign up and upload a video
             url: video-indexer-get-started.md 
-          - text: Invite users
-            url: invite-users.md
       - linkListType: how-to-guide
         links:
           - text: Create an ARM-based account