Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-aadroles-protected-actions-preview

Author: rolyon

.openpublishing.redirection.json

@@ -22522,7 +22522,11 @@
             "source_path_from_root": "/articles/sentinel/data-connectors/microsoft-defender-threat-intelligence.md",
             "redirect_url": "/azure/sentinel/understand-threat-intelligence",
             "redirect_document_id": false
-        }
-       
+        },
+        {
+            "source_path_from_root": "/articles/principles-for-ai-generated-content.md",
+            "redirect_url": "https://aka.ms/ai-content-principles",
+            "redirect_document_id": false
+        } 
     ]
 }

articles/azure-monitor/agents/azure-monitor-agent-performance.md

@@ -0,0 +1,58 @@
+---
+title: Performance Benchmark for forwarding Gateway using Azure Monitor Agent 
+description: Performance data for the AMA running in a gateway scenario
+ms.topic: conceptual
+author: guywi-ms
+ms.author: guywild
+ms.date: 4/07/2023
+ms.reviewer: jeffwo
+
+#customer-intent: As a deployment engineer, I can scope the resources required to scale my gateway data colletors the use the Azure Monitor Agent. 
+
+---
+# Azure Monitor Agent Performance Benchmark
+ 
+The agent can handle many thousands of events per second in the gateway event forwarding scenario. The exact throughput rate depends on various factors such as the size of each event, the specific data type, and physical hardware resources. This article will describe the Microsoft internal benchmark used for testing the agent throughput of 10k Syslog events in the forwarder scenario. The benchmark results should provide a guide to size the resources that you will need in your environment. 
+ 
+> [!NOTE]
+> The results in this article are informational about the performance of AMA in the forwarding scenario only and do not constitute any service agreement on the part of Microsoft.   
+
+## Best practices for agent as a forwarder. 
+
+- The forwarder should be on a dedicated system to eliminate potential interference from other workloads. 
+- The forwarder system should be monitored for CPU, memory, and disk utilization to prevent overloads from causing data loss. 
+- Where possible use a load balancer and redundant forwarder systems to improve reliability and scalability. 
+- For other considerations for forwarders see the Log Analytics Gateway documentation. 
+
+## Agent Performance 
+
+The benchmark is run in a controlled environment to get repeatable, accurate, and statistically significant results. The resources consumed by the agent are measured under a load of 10,000 simulated Syslog events per second. The simulated load is run on the same physical hardware that the agent under test is on. Test trials are run for seven days. For each trial, performance metrics are sampled every second to collect CPU, memory, and network maximum and average usage. This approach provides the right information to help you estimate the resources needed for your environment. 
+
+> [!NOTE]
+> The results do not measure the end-to-end throughput ingested by a Log Analytics Workspace (or other telemetry sinks), as there may be end-to-end variability due to network and backend pipeline performance.   
+
+The benchmarks are run on an Azure VM Standard_F8s_v2 system using AMA Linux version 1.25.2 and 10 GB of disk space for the event cache. 
+
+- vCPU’s:	8 with HyperThreading (800% CPU is possible) 
+- Memory: 	16 GiB 
+- Temp Storage:	64 GiB 
+- Max Disk IOPS:	6400 
+- Network:	12500 Mbp Max on all 4 physical NICs 
+
+ 
+
+## Results 
+
+| Perf Metric | Ave (Max) Med |
+|:---|:---:|
+| CPU %           | 51 (262)     |
+| Mem RSS MB      | 276 (1,017)  |
+| Network KBps    | 338 (18,033) |
+
+
+## Next steps
+
+- [Connect computers without internet access by using the Log Analytics gateway in Azure Monitor](gateway.md)
+- [Install the Azure Monitor Agent](azure-monitor-agent-manage.md) on Windows and Linux virtual machines.
+- [Create a data collection rule](data-collection-rule-azure-monitor-agent.md) to collect data from the agent and send it to Azure Monitor.
+

articles/azure-monitor/toc.yml

@@ -231,6 +231,9 @@ items:
         href: agents/azure-monitor-agent-migration.md
       - name: Migration tools
         href: agents/azure-monitor-agent-migration-tools.md
+    - name: Performance
+      displayName: Performance
+      href: /azure/azure-monitor/agents/azure-monitor-agent-performance.md
     - name: FAQ
       displayName: Azure Monitor agent FAQ
       href: /azure/azure-monitor/faq#azure-monitor-agent

articles/container-apps/ingress-overview.md

@@ -65,12 +65,12 @@ HTTP ingress adds headers to pass metadata about the client request to your cont
 | `X-Forwarded-For` | The IP address of the client that sent the request. |  |
 | `X-Forwarded-Host` | The host name the client used to connect with the Container Apps service. |  |
 
-### <a name="tcp"></a>TCP (preview) 
+### <a name="tcp"></a>TCP
 
 Container Apps supports TCP-based protocols other than HTTP or HTTPS. For example, you can use TCP ingress to expose a container app that uses the [Redis protocol](https://redis.io/topics/protocol).
 
 > [!NOTE]
-> TCP ingress is in public preview.  External TCP ingress setting is only supported in Container Apps environments that use a [custom VNET](vnet-custom.md).
+> External TCP ingress is only supported for Container Apps environments that use a [custom VNET](vnet-custom.md).
 
 With TCP ingress enabled, your container app:
 

articles/principles-for-ai-generated-content.md

@@ -41,6 +41,8 @@ items:
   expanded: true
 - name: Resources
   items:
+  - name: Troubleshooting job run error codes
+    href: status-code.md
   - name: Collect a support bundle
     href: troubleshooting.md
   - name: Release notes

articles/storage-mover/TOC.yml

@@ -0,0 +1,60 @@
+---
+title: Troubleshooting Azure Storage Mover job run error codes
+description: Learn how to understand and remediate errors raised by the Azure Storage Mover Agent.
+author: stevenmatthew
+ms.author: shaas
+ms.service: storage-mover
+ms.topic: how-to
+ms.date: 03/20/2023
+ms.custom: template-how-to
+---
+
+<!-- 
+!########################################################
+STATUS: IN REVIEW
+
+CONTENT: final       
+
+REVIEW Stephen/Fabian: completed
+REVIEW Engineering: not reviewed
+EDIT PASS: completed
+
+Initial doc score: 79
+Current doc score: 100 (552, 0)
+
+!########################################################
+-->
+
+# Troubleshooting Storage Mover job run error codes
+
+An Azure Storage Mover agent uses string status codes for statuses that are conveyed to the end user. All status codes have the prefix *AZSM* followed by four decimal digits. The first decimal digit indicates the high-level scope of the status. Each status code should belong to one of the following scopes:
+
+- Status that applies to the entire agent.<br />These codes use the scope digit '0', and therefore and have the prefix "AZSM0".
+- Status that applies to a specific job run by the agent.<br />These codes use the scope digit '1' and therefore have the prefix "AZSM1".
+- Status that applies to a specific file or directory transferred by a job run by the agent.<br />These codes use the scope digit '2' and therefore have the prefix "AZSM2".
+
+Each of these scopes further divides statuses into categories and subcategories. Each subcategory typically reserves 20 status codes to accommodate future expansion.
+
+> [!TIP]
+> *AZSM0000* is the special scope-agnostic status code indicating successful operation. This should be used to signify successful operation at any scope/level.
+
+|Error Code                       |Error Message | Details/Troubleshooting steps/Mitigation |
+|---------------------------------|--------------|------------------------------------------|
+| <a name="AZSM1001"></a>AZSM1001 |Failed to mount source path | Verify the provided server information, name or IP-address, is valid, or the source location is correct. |
+| <a name="AZSM1002"></a>AZSM1002 |Encountered an error while scanning the source  | Retry or create a support ticket. |
+| <a name="AZSM1003"></a>AZSM1003 |Failed to access source folder due to permission issues | Check if the agent has been granted permissions correctly to the source file share. |
+| <a name="AZSM1004"></a>AZSM1004 |Source path provided is invalid | Create a new endpoint with a valid source share path and update the job definition and retry. |
+| <a name="AZSM1020"></a>AZSM1020 |Miscellaneous error while accessing source  | Retry or create a support ticket. |
+| <a name="AZSM1021"></a>AZSM1021 |Failed to access target folder due to permission issues  | Retry or create a support ticket. |
+| <a name="AZSM1022"></a>AZSM1022 |Target path provided is invalid | Create a new endpoint with a valid target container and path and update the job definition and retry. |
+| <a name="AZSM1023"></a>AZSM1023 |Lease expired for this agent on the target container  | Retry or create a support ticket. |
+| <a name="AZSM1024"></a>AZSM1024 |Authorization failure on claiming the target container | The agent doesn't have the permission to access the target container. The role assignment is performed automatically while running jobs from the portal. If you're using the APIs/Powershell cmdlets/SDKs, then manually create a 'Storage Blob Data Contributor' role assignment for the agent to access the target storage account blob container. The [Assign an Azure role for access to blob data](/azure/storage/blobs/assign-azure-role-data-access) article may help resolve this issue. |
+| <a name="AZSM1025"></a>AZSM1025 |Authentication failure on claiming the target container  | Retry or create a support ticket. |
+| <a name="AZSM1026"></a>AZSM1026 |Blob type in the target container not supported by the agent | This blob type is unsupported by the current Storage Mover agent. |
+| <a name="AZSM1040"></a>AZSM1040 |Miscellaneous error while accessing target  | Retry or create a support ticket. |
+| <a name="AZSM1041"></a>AZSM1041 |Failed to send job progress  | Retry or create a support ticket. |
+| <a name="AZSM1042"></a>AZSM1042 |Failed to create job  | Retry or create a support ticket. |
+| <a name="AZSM1043"></a>AZSM1043 |Failed to resume job  | Retry or create a support ticket. |
+| <a name="AZSM1044"></a>AZSM1044 |Failed to finalize the job  | Retry or create a support ticket. |
+| <a name="AZSM1045"></a>AZSM1045 |Job was aborted while it was still running  | Retry or create a support ticket. |
+| <a name="AZSM1060"></a>AZSM1060 |Miscellaneous error during job execution  | Retry or create a support ticket. |

articles/storage-mover/status-code.md

@@ -28,6 +28,10 @@ The following issues are ones we're already aware of, so you won't need to repor
 
 - You might run into issue where you are stuck in the loading state on every video site. This is a known issue that we're currently investigating. To temporarily mitigate this issue, sign out of Azure Virtual Desktop and restart your session.
 
+- If you aren't using the default Windows size settings for video players, such as not fitting the player to window, not maximizing the window, and so on), parts of video players may not appear correctly. If you encounter this issue, you should change the settings back to Default mode.
+
+- If your monitor or browser scale factor isn't set to 100%, you may see a gray pattern appear on the video screen.
+
 ### The MSI installer doesn't work
 
 - There's a small chance that the MSI installer won't be able to install the extension during internal testing. If you run into this issue, you'll need to install the multimedia redirection extension from the Microsoft Edge Store or Google Chrome Store.