Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-role-assignments-portal-classic

Author: rolyon

.openpublishing.publish.config.json

@@ -955,6 +955,12 @@
       "url": "https://github.com/Azure-Samples/cosmos-db-mongodb-api-dotnet-samples",
       "branch": "main",
       "branch_mapping": {}
+    },
+    {
+      "path_to_root": "reusable-content",
+      "url": "https://github.com/MicrosoftDocs/reusable-content",
+      "branch": "main",
+      "branch_mapping": {}
     }
   ],
   "branch_target_mapping": {

.openpublishing.redirection.json

@@ -6223,6 +6223,41 @@
             "redirect_url": "/azure/azure-cache-for-redis/scripts/create-manage-cache",
             "redirect_document_id": false
         },
+        { 
+            "source_path_from_root": "/articles/storage/common/storage-auth-abac-attributes.md",
+            "redirect_url": "/azure/storage/blobs/storage-auth-abac-attributes",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/storage/common/storage-auth-abac-cli.md",
+            "redirect_url": "/azure/storage/blobs/storage-auth-abac-cli",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/storage/common/storage-auth-abac-examples.md",
+            "redirect_url": "/azure/storage/blobs/storage-auth-abac-examples",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/storage/common/storage-auth-abac-portal.md",
+            "redirect_url": "/azure/storage/blobs/storage-auth-abac-portal",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/storage/common/storage-auth-abac-powershell.md",
+            "redirect_url": "/azure/storage/blobs/storage-auth-abac-powershell",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/storage/common/storage-auth-abac-security.md",
+            "redirect_url": "/azure/storage/blobs/storage-auth-abac-security",
+            "redirect_document_id": false
+        },
+        {
+            "source_path_from_root": "/articles/storage/common/storage-auth-abac.md",
+            "redirect_url": "/azure/storage/blobs/storage-auth-abac",
+            "redirect_document_id": false
+        },
         {
             "source_path_from_root": "/articles/storage/storage-client-side-encryption.md",
             "redirect_url": "/azure/storage/common/storage-client-side-encryption",

articles/app-service/security-controls-policy.md

@@ -1,7 +1,7 @@
 ---
 title: Azure Policy Regulatory Compliance controls for Azure App Service
 description: Lists Azure Policy Regulatory Compliance controls available for Azure App Service. These built-in policy definitions provide common approaches to managing the compliance of your Azure resources.
-ms.date: 09/19/2022
+ms.date: 10/01/2022
 ms.topic: sample
 ms.service: app-service
 ms.custom: subject-policy-compliancecontrols
@@ -21,6 +21,59 @@ compliant with the specific standard.
 
 ## Release notes
 
+### October 2022
+
+- **Function app slots should have remote debugging turned off**
+  - New policy created
+- **App Service app slots should have remote debugging turned off**
+  - New policy created
+- **Function app slots should use latest 'HTTP Version'**
+  - New policy created
+- **Function app slots should use the latest TLS version**
+  - New policy created
+- **App Service app slots should use the latest TLS version**
+  - New policy created
+- **App Service app slots should have resource logs enabled**
+  - New policy created
+- **App Service app slots should enable outbound non-RFC 1918 traffic to Azure Virtual Network**
+  - New policy created
+- **App Service app slots should use managed identity**
+  - New policy created
+- **App Service app slots should use latest 'HTTP Version'**
+  - New policy created
+- Deprecation of policy **Configure App Services to disable public network access**
+  - Replaced by "Configure App Service apps to disable public network access"
+- Deprecation of policy **App Services should disable public network access**
+  - Replaced by "App Service apps should disable public network access" to support _Deny_ effect
+- **App Service apps should disable public network access**
+  - New policy created
+- **App Service app slots should disable public network access**
+  - New policy created
+- **Configure App Service apps to disable public network access**
+  - New policy created
+- **Configure App Service app slots to disable public network access**
+  - New policy created
+- **Function apps should disable public network access**
+  - New policy created
+- **Function app slots should disable public network access**
+  - New policy created
+- **Configure Function apps to disable public network access**
+  - New policy created
+- **Configure Function app slots to disable public network access**
+  - New policy created
+- **Configure App Service app slots to turn off remote debugging**
+  - New policy created
+- **Configure Function app slots to turn off remote debugging**
+  - New policy created
+- **Configure App Service app slots to use the latest TLS version**
+  - New policy created
+- **Configure Function app slots to use the latest TLS version**
+  - New policy created
+- **App Service apps should use latest 'HTTP Version'**
+  - Updated scope to include Windows apps
+- **Function apps should use latest 'HTTP Version'**
+  - Updated scope to include Windows apps
+
 ### September 2022
 
 - **App Service apps should be injected into a virtual network**

articles/azure-functions/functions-create-function-linux-custom-image.md

@@ -1,7 +1,7 @@
 ---
 title: Create Azure Functions on Linux using a custom image
 description: Learn how to create Azure Functions running on a custom Linux image.
-ms.date: 06/10/2022
+ms.date: 09/28/2022
 ms.topic: tutorial
 ms.custom: "devx-track-csharp, mvc, devx-track-python, devx-track-azurepowershell, devx-track-azurecli, devdivchpfy22"
 zone_pivot_groups: programming-languages-set-functions-full
@@ -518,7 +518,7 @@ A function app on Azure manages the execution of your functions in your hosting
 1. The function can now use this connection string to access the storage account.
 
 > [!NOTE]
-> If you publish your custom image to a private container registry, you must use environment variables in the *Dockerfile* for the connection string instead. For more information, see the [ENV instruction](https://docs.docker.com/engine/reference/builder/#env). You must also set the `DOCKER_REGISTRY_SERVER_USERNAME` and `DOCKER_REGISTRY_SERVER_PASSWORD` variables. To use the values, you must rebuild the image, push the image to the registry, and then restart the function app on Azure.
+> If you publish your custom image to a private container registry, you must also set the `DOCKER_REGISTRY_SERVER_USERNAME` and `DOCKER_REGISTRY_SERVER_PASSWORD` variables. For more information, see [Custom containers](../app-service/reference-app-settings.md#custom-containers) in the App Service settings reference.
 
 ## Verify your functions on Azure
 

articles/azure-monitor/agents/agents-overview.md

@@ -56,7 +56,10 @@ Azure Monitor Agent uses [data collection rules](../essentials/data-collection-r
     | Text logs | Log Analytics workspace - custom table | Events sent to log file on agent machine |
 
     <sup>1</sup> On Linux, using Azure Monitor Metrics as the only destination is supported in v1.10.9.0 or higher.<br>
-    <sup>2</sup> Azure Monitor Linux Agent v1.15.2 or higher supports syslog RFC formats including Cisco Meraki, Cisco ASA, Cisco FTD, Sophos XG, Juniper Networks, Corelight Zeek, CipherTrust, NXLog, McAfee, and Common Event Format (CEF). 
+    <sup>2</sup> Azure Monitor Linux Agent versions 1.15.2 and higher support syslog RFC formats including Cisco Meraki, Cisco ASA, Cisco FTD, Sophos XG, Juniper Networks, Corelight Zeek, CipherTrust, NXLog, McAfee, and Common Event Format (CEF).
+
+    >[!NOTE]
+    >On rsyslog-based systems, Azure Monitor Linux Agent adds forwarding rules to the default ruleset defined in the rsyslog configuration. If multiple rulesets are used, inputs bound to non-default ruleset(s) are **not** forwarded to Azure Monitor Agent. For more information about multiple rulesets in rsyslog, see the [official documentation](https://www.rsyslog.com/doc/master/concepts/multi_ruleset.html).
 
 ## Supported services and features
 

articles/azure-monitor/agents/azure-monitor-agent-troubleshoot-linux-vm.md

@@ -95,6 +95,7 @@ Here's how AMA collects syslog events:
 	3. If none of the above helps, [file a ticket](#file-a-ticket) with **Summary** as 'Syslog DCR not available' and **Problem type** as 'I need help configuring data collection from a VM'.
 3. Validate the layout of the Syslog collection workflow to ensure all necessary pieces are in place and accessible:
 	1. For `rsyslog` users, ensure the `/etc/rsyslog.d/10-azuremonitoragent.conf` file is present, isn't empty, and is accessible by the `rsyslog` daemon (syslog user).
+		1. Check your rsyslog configuration at `/etc/rsyslog.conf` and `/etc/rsyslog.d/*` to see if you have any inputs bound to a non-default ruleset, as messages from these inputs will not be forwarded to Azure Monitor Agent. For instance, messages from an input configured with a non-default ruleset like `input(type="imtcp" port="514" `**`ruleset="myruleset"`**`)` will not be forward.
 	2. For `syslog-ng` users, ensure the `/etc/syslog-ng/conf.d/azuremonitoragent.conf` file is present, isn't empty, and is accessible by the `syslog-ng` daemon (syslog user).
 	3. Ensure the file `/run/azuremonitoragent/default_syslog.socket` exists and is accessible by `rsyslog` or `syslog-ng` respectively.
 	4. Check for a corresponding drop in count of processed syslog events in `/var/opt/microsoft/azuremonitoragent/log/mdsd.qos`. If such drop isn't indicated in the file, [file a ticket](#file-a-ticket) with **Summary** as 'Syslog data dropped in pipeline' and **Problem type** as 'I need help with Azure Monitor Linux Agent'.

articles/azure-vmware/attach-disk-pools-to-azure-vmware-solution-hosts.md

@@ -1,5 +1,5 @@
 ---
-title: Attach Azure disk pools to Azure VMware Solution hosts (Preview)
+title: Attach Azure disk pools to Azure VMware Solution hosts 
 description: Learn how to attach an Azure disk pool surfaced through an iSCSI target as the VMware vSphere datastore of an Azure VMware Solution private cloud. Once the datastore is configured, you can create volumes on it and consume them from your Azure VMware Solution private cloud.
 ms.topic: how-to
 ms.service: azure-vmware
@@ -9,14 +9,14 @@ ms.custom: ignite-fall-2021, devx-track-azurecli
 ms.devlang: azurecli
 ---
 
-# Attach disk pools to Azure VMware Solution hosts (Preview)
+# Attach disk pools to Azure VMware Solution hosts 
 
 [Azure disk pools](../virtual-machines/disks-pools.md) offer persistent block storage to applications and workloads backed by Azure Disks. You can use disks as the persistent storage for Azure VMware Solution for optimal cost and performance. For example, you can scale up by using disk pools instead of scaling clusters if you host storage-intensive workloads. You can also use disks to replicate data from on-premises or primary VMware vSphere environments to disk storage for the secondary site. To scale storage independent of the Azure VMware Solution hosts, we support surfacing [ultra disks](../virtual-machines/disks-types.md#ultra-disks), [premium SSD](../virtual-machines/disks-types.md#premium-ssds) and [standard SSD](../virtual-machines/disks-types.md#standard-ssds) as the datastores.  
 
 >[!IMPORTANT]
->Azure disk pools on Azure VMware Solution (Preview) is currently in public preview.
->This preview version is provided without a service level agreement, and it's not recommended for production workloads. Certain features might not be supported or might have constrained capabilities.
->For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
+>We are officially halting the preview of Azure Disk Pools, and it will not be made generally available.
+>New customers will not be able to register the `Microsoft.StoragePool` resource provider on their subscription and deploy new Disk Pools.
+> Existing subscriptions registered with Microsoft.StoragePool may continue to deploy and manage disk pools for the time being.
 
 Azure managed disks are attached to one iSCSI controller virtual machine deployed under the Azure VMware Solution resource group. Disks get deployed as storage targets to a disk pool, and each storage target shows as an iSCSI LUN under the iSCSI target. You can expose a disk pool as an iSCSI target connected to Azure VMware Solution hosts as a datastore. A disk pool surfaces as a single endpoint for all underlying disks added as storage targets. Each disk pool can have only one iSCSI controller.
 

articles/cdn/cdn-verizon-premium-rules-engine-reference-features.md

@@ -30,7 +30,6 @@ The available types of features are:
 * [Origin](#origin)
 * [Specialty](#specialty)
 * [URL](#url)
-* [Web Application Firewall](#waf)
 
 ### <a name="access"></a>Access
 
@@ -158,12 +157,6 @@ These features allow a request to be redirected or rewritten to a different URL.
 
 **[Back to the top](#top)**
 
-### <a name="waf"></a>Web Application Firewall
-
-The [Web Application Firewall](https://docs.edgecast.com/pci-cdn/Content/Web-Security/Web-Application-Firewall-WAF.htm) feature determines whether a request will be screened by Web Application Firewall.
-
-**[Back to the top](#top)**
-
 For the most recent features, see the [Verizon Rules Engine documentation](https://docs.vdms.com/cdn/index.html#Quick_References/HRE_QR.htm#Actions).
 
 ## Next steps

articles/cognitive-services/Speech-Service/includes/quickstarts/platform/python-requirements.md

@@ -26,7 +26,9 @@ A macOS version 10.14 or later is required.
 
 ---
 
-Install a version of [Python from 3.7 to 3.10](https://www.python.org/downloads/). To check your installation, open a terminal and run the command `python --version`. If it's installed properly, you'll get a response like "Python 3.8.2".
+Install a version of [Python from 3.7 to 3.10](https://www.python.org/downloads/). 
 
 > [!IMPORTANT]
-> Make sure that packages of the same platform (x64 or x86) are installed. For example, if you install the x64 redistributable package, then you need to install the x64 Python package. 
+> Make sure that packages of the same platform (x64 or x86) are installed. For example, if you install the x64 redistributable package, then you need to install the x64 Python package. 
+
+To check your installation, open a terminal and run the command `python --version`. If it's installed properly, you'll get a response like "Python 3.8.10". If you're using macOS or Linux, you might need to run the command `python3 --version` instead. To enable use of `python` instead of `python3`, run `alias python='python3'` to set up an alias. The Speech SDK quickstart samples specify `python` usage. 

articles/connectors/built-in.md

@@ -5,6 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: conceptual
+ms.custom: engagement-fy23
 ms.date: 09/14/2022
 ---