Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into vnet-peer-update

Author: asudbring

articles/ai-services/document-intelligence/containers/install-run.md

@@ -66,6 +66,10 @@ The host is a x64-based computer that runs the Docker container. It can be a com
 * [Azure Container Instances](../../../container-instances/index.yml).
 * A [Kubernetes](https://kubernetes.io/) cluster deployed to [Azure Stack](/azure-stack/operator). For more information, see [Deploy Kubernetes to Azure Stack](/azure-stack/user/azure-stack-solution-template-kubernetes-deploy).
 
+> [!NOTE]
+>
+> Note that Studio container cannot be deployed and run in Azure Kubernetes Service. Studio container is only supported to be run on local machine.
+
 ### Container requirements and recommendations
 
 #### Required supporting containers

articles/aks/start-stop-cluster.md

@@ -2,7 +2,7 @@
 title: Stop and start an Azure Kubernetes Service (AKS) cluster
 description: Learn how to stop and start an Azure Kubernetes Service (AKS) cluster.
 ms.topic: article
-ms.date: 03/14/2023
+ms.date: 07/01/2024
 author: palma21
 ---
 
@@ -100,7 +100,7 @@ When using the cluster stop/start feature, the following conditions apply:
 ## Start an AKS cluster
 
 > [!CAUTION]
-> Don't repeatedly stop and start your clusters. This can result in errors. Once your cluster is stopped, you should wait at least 15-30 minutes before starting it again.
+> After utilizing the start/stop feature on AKS, it is essential to wait 15-30 minutes before restarting your AKS cluster. This waiting period is necessary because it takes several minutes for the relevant services to fully stop. Attempting to restart your cluster during this process can disrupt the shutdown process and potentially cause issues with the cluster or its workloads.
 
 ### [Azure CLI](#tab/azure-cli)
 

articles/application-gateway/ingress-controller-migration.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: application-gateway
 ms.topic: article
-ms.date: 07/28/2023
+ms.date: 07/01/2024
 ms.author: greglin
 ---
 
@@ -40,6 +40,9 @@ You can now enable the AGIC add-on in your AKS cluster to target your existing A
 ```azurecli-interactive
 az aks enable-addons -n myCluster -g myResourceGroup -a ingress-appgw --appgw-id $appgwId
 ```
+Alternatively, you can navigate to your [AKS cluster in the Azure portal](https://portal.azure.com/?feature.aksagic=true) and enable the AGIC add-on in the **Virtual network integration** tab of your cluster. Select your existing Application Gateway when you choose which Application Gateway that the add-on should target. 
+
+![Application Gateway Ingress Controller Portal](./media/tutorial-ingress-controller-add-on-existing/portal-ingress-controller-add-on.png)
 
 ## Next Steps
 - [**Application Gateway Ingress Controller Troubleshooting**](ingress-controller-troubleshoot.md): Troubleshooting guide for AGIC 

articles/application-gateway/media/tutorial-ingress-controller-add-on-existing/portal-ingress-controller-add-on.png

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: application-gateway
 ms.topic: tutorial
-ms.date: 11/28/2023
+ms.date: 07/01/2024
 ms.author: greglin
 ms.custom: template-tutorial, devx-track-azurecli
 ---
@@ -78,9 +78,14 @@ If you'd like to continue using Azure CLI, you can continue to enable the AGIC a
 appgwId=$(az network application-gateway show --name myApplicationGateway --resource-group myResourceGroup -o tsv --query "id") 
 az aks enable-addons --name myCluster --resource-group myResourceGroup --addon ingress-appgw --appgw-id $appgwId
 ```
+## Enable the AGIC add-on in existing AKS cluster through Azure portal 
+
+If you'd like to use Azure portal to enable AGIC add-on, go to [(https://aka.ms/azure/portal/aks/agic)](https://aka.ms/azure/portal/aks/agic) and navigate to your AKS cluster through the portal link. Select the **Networking** menu item under **Settings**. From there, go to the **Virtual network integration** tab within your AKS cluster. You'll see an **Application gateway ingress controller** section, which allows you to enable and disable the ingress controller add-on. Select the **Manage** button, then the checkbox next to **Enable ingress controller**. Select the application gateway you created, **myApplicationGateway** and then select **Save**.
+
+:::image type="content" source="./media/tutorial-ingress-controller-add-on-existing/portal-ingress-controller-add-on.png" alt-text="Screenshot showing how to enable application gateway ingress controller from the networking page of the Azure Kubernetes Service.":::
 
 > [!IMPORTANT]
-> When you use an application gateway in a different resource group than the AKS cluster resource group, the managed identity **_ingressapplicationgateway-{AKSNAME}_** that is created must have **Network Contributor** and **Reader** roles set in the application gateway resource group.
+> If you use an application gateway in a different resource group than the AKS cluster resource group, the managed identity **_ingressapplicationgateway-{AKSNAME}_** that is created must have **Network Contributor** and **Reader** roles set in the application gateway resource group.
 
 ## Peer the two virtual networks together
 

articles/application-gateway/tutorial-ingress-controller-add-on-existing.md

@@ -1,17 +1,17 @@
 ---
-title: Quickstart for adding feature flags to Python with Azure App Configuration (Preview)
+title: Quickstart for adding feature flags to Python with Azure App Configuration
 description: Add feature flags to Python apps and manage them using Azure App Configuration.
 author: mrm9084
 ms.service: azure-app-configuration
 ms.devlang: python
 ms.topic: quickstart
-ms.date: 05/29/2024
+ms.date: 07/01/2024
 ms.author: mametcal
 ms.custom: devx-track-python, mode-other
 #Customer intent: As an Python developer, I want to use feature flags to control feature availability quickly and confidently.
 ---
 
-# Quickstart: Add feature flags to a Python app (preview)
+# Quickstart: Add feature flags to a Python app
 
  In this quickstart, you'll create a feature flag in Azure App Configuration and use it to dynamically control Python apps to create an end-to-end implementation of feature management.
 

articles/azure-app-configuration/quickstart-feature-flag-python.md

@@ -172,16 +172,48 @@
     - name: Azure Application Consistent Snapshot (AzAcSnap) tool
       items: 
       - name: What is AzAcSnap?
-        href: azacsnap-introduction.md
-      - name: Release Notes for AzAcSnap
-        href: azacsnap-release-notes.md
+        items:
+        - name: Introduction to AzAcSnap
+          href: azacsnap-introduction.md
+        - name: Release Notes for AzAcSnap
+          href: azacsnap-release-notes.md
       - name: Get started with AzAcSnap
-        href: azacsnap-get-started.md
-      - name: Install AzAcSnap
-        href: azacsnap-installation.md
+        items:
+        - name: Overall workflow
+          href: azacsnap-get-started.md
+        - name: Install AzAcSnap
+          href: azacsnap-installation.md
+        - name: Configure Database
+          items:
+          - name: All databases
+            href: azacsnap-configure-database.md
+          - name: SAP HANA
+            href: azacsnap-configure-database.md?tabs=sap-hana
+          - name: Oracle Database
+            href: azacsnap-configure-database.md?tabs=oracle
+          - name: IBM Db2
+            href: azacsnap-configure-database.md?tabs=db2
+          - name: Microsoft SQL Server (PREVIEW)
+            href: azacsnap-preview.md?tabs=mssql#microsoft-sql-server
+        - name: Configure Storage
+          items:
+          - name: All storage
+            href: azacsnap-configure-storage.md
+          - name: Azure NetApp Files
+            href: azacsnap-configure-storage.md?tabs=azure-netapp-files
+          - name: Azure Large Instance
+            href: azacsnap-configure-storage.md?tabs=azure-large-instance
+          - name: Azure Managed Disk (PREVIEW)
+            href: azacsnap-preview.md?tabs=mssql#azure-managed-disks
+        - name: Configure AzAcSnap
+          href: azacsnap-cmd-ref-configure.md
+        - name: Test configuration of AzAcSnap
+          href: azacsnap-cmd-ref-test.md
+        - name: Backup your database with AzAcSnap
+          href: azacsnap-cmd-ref-backup.md
       - name: Disaster recovery using AzAcSnap
         href: azacsnap-disaster-recovery.md
-      - name: Tips and tricks for using AzAcSnap
+      - name: Tips for using AzAcSnap
         href: azacsnap-tips.md
       - name: Troubleshoot AzAcSnap
         href: azacsnap-troubleshoot.md

articles/azure-monitor/media/self-help/log-analytics/billing/high-res/log-analytics-workspaces.png

@@ -5,7 +5,7 @@ services: azure-netapp-files
 author: Phil-Jensen
 ms.service: azure-netapp-files
 ms.topic: reference
-ms.date: 07/29/2022
+ms.date: 05/15/2024
 ms.author: phjensen
 ---
 
@@ -15,9 +15,9 @@ This article provides a guide for running the backup command of the Azure Applic
 
 ## Introduction
 
-A storage snapshot based backup is run using the `azacsnap -c backup` command.  This command performs the orchestration of a database consistent storage snapshot on the DATA volumes, and a storage snapshot (without any database consistency setup) on the OTHER volumes.  
+A storage snapshot based backup is run using the `azacsnap -c backup` command. This command performs the orchestration of a database consistent storage snapshot on the DATA volumes, and a storage snapshot (without any database consistency setup) on the OTHER volumes. 
 
-For DATA volumes `azacsnap` will prepare the database for a storage snapshot, then it will take the storage snapshot for all configured volumes, finally it will advise the database the snapshot is complete.  It will also manage any database entries which record snapshot backup activity (e.g. SAP HANA backup catalog).
+For DATA volumes `azacsnap` prepares the database for a storage snapshot, then it takes a storage snapshot for all configured volumes, finally it tells the database the snapshot is complete. It also manages any database entries which record snapshot backup activity (for example, SAP HANA backup catalog).
 
 ## Command options
 
@@ -27,36 +27,36 @@ The `-c backup` command takes the following arguments:
   - `data` snapshots the volumes within the `dataVolume` stanza of the configuration file.
     1. **data** Volume Snapshot process
        1. put the database into *backup-mode*.
-       1. take snapshots of the Volume(s) listed in the configuration file's `"dataVolume"` stanza.
+       1. take snapshots of the Volumes listed in the configuration file's `"dataVolume"` stanza.
        1. take the database out of *backup-mode*.
        1. perform snapshot management.
   - `other` snapshots the volumes within the `otherVolume` stanza of the configuration file.
     1. **other** Volume Snapshot process
-       1. take snapshots of the Volume(s) listed in the configuration file's `"otherVolume"` stanza.
+       1. take snapshots of the Volumes listed in the configuration file's `"otherVolume"` stanza.
        1. perform snapshot management.
-  - `all` snapshots all the volumes in the `dataVolume` stanza and then all the volumes in the `otherVolume` stanza of the configuration file.  The 
+  - `all` snapshots all the volumes in the `dataVolume` stanza and then all the volumes in the `otherVolume` stanza of the configuration file. The 
     processing is handled in the order outlined as follows:
     1. **all** Volumes Snapshot process
        1. **data** Volume Snapshot (same as the normal `--volume data` option)
           1. put the database into *backup-mode*.
-          1. take snapshots of the Volume(s) listed in the configuration file's `"dataVolume"` stanza.
+          1. take snapshots of the Volumes listed in the configuration file's `"dataVolume"` stanza.
           1. take the database out of *backup-mode*.
           1. perform snapshot management.
        1. **other** Volume Snapshot (same as the normal `--volume other` option)
-          1. take snapshots of the Volume(s) listed in the configuration file's `"otherVolume"` stanza.
+          1. take snapshots of the Volumes listed in the configuration file's `"otherVolume"` stanza.
           1. perform snapshot management.
 
   > [!NOTE]
   > By creating a separate config file with the boot volume as the otherVolume, it's possible for `boot` snapshots to be taken on an entirely different schedule (for example, daily).
 
-- `--prefix=` the customer snapshot prefix for the snapshot name. This parameter has two purposes. Firstly purpose is to provide a unique name for grouping of snapshots. Secondly to determine the `--retention` number of storage snapshots that are kept for the specified `--prefix`.
+- `--prefix=` the customer snapshot prefix for the snapshot name. This parameter has two purposes. Firstly provide a unique name for grouping of snapshots. Secondly to determine the `--retention` number of storage snapshots that are kept for the specified `--prefix`.
 
     > [!IMPORTANT]
     > Only alpha numeric ("A-Z,a-z,0-9"), underscore ("_") and dash ("-") characters are allowed.
 
-- `--retention` the number of snapshots of the defined `--prefix` to be kept. Any additional snapshots are removed after a new snapshot is taken for this `--prefix`.
+- `--retention` the number of snapshots of the defined `--prefix` to be kept. Any extra snapshots are removed after a new snapshot is taken for this `--prefix`.
 
-- `--trim` available for SAP HANA v2 and later, this option maintains the backup catalog and on disk catalog and log backups. The number of entries to keep in the backup catalog is determined by the `--retention` option above, and deletes older entries for the defined prefix (`--prefix`) from the backup catalog, and the related physical logs backup. It also deletes any log backup entries that are older than the oldest non-log backup entry. This operations helps to prevent the log backups from using up all available disk space.
+- `--trim` available for SAP HANA v2 and later, this option maintains the backup catalog and on disk catalog and log backups. The number of entries to keep in the backup catalog is determined by the `--retention` option above, and deletes older entries for the defined prefix (`--prefix`) from the backup catalog, and the related physical logs backup. It also deletes any log backup entries that are older than the oldest non-log backup entry. This `--trim` operation helps to prevent the log backups from using up all available disk space.
 
   > [!NOTE]
   > The following example command will keep 9 storage snapshots and ensure the backup catalog is continuously trimmed to match the 9 storage snapshots being retained.
@@ -68,7 +68,7 @@ The `-c backup` command takes the following arguments:
 - `[--ssl=]` an optional parameter that defines the encryption method used to communicate
     with SAP HANA, either `openssl` or `commoncrypto`. If defined, then the `azacsnap -c backup`
     command expects to find two files in the same directory, these files must be named after
-    the corresponding SID. Refer to [Using SSL for communication with SAP HANA](azacsnap-installation.md#using-ssl-for-communication-with-sap-hana). The following example takes a `hana` type snapshot with a prefix of `hana_TEST` and will keep `9` of them communicating with SAP HANA using SSL (`openssl`).
+    the corresponding SID. Refer to [Using SSL for communication with SAP HANA](azacsnap-configure-database.md#using-ssl-for-communication-with-sap-hana). The following example takes a `hana` type snapshot with a prefix of `hana_TEST` and keeps `9` of them communicating with SAP HANA using SSL (`openssl`).
 
     ```bash
     azacsnap -c backup --volume data --prefix hana_TEST --retention 9 --trim --ssl=openssl
@@ -79,13 +79,13 @@ The `-c backup` command takes the following arguments:
 ## Snapshot backups are fast
 
 The duration of a snapshot backup is independent of the volume size, with a 10-TB volume being snapped
-within the same approximate time as a 10-GB volume.  
+within the same approximate time as a 10-GB volume.
 
 The primary factors impacting overall execution time are the number of volumes to be snapshot and any
 changes in the `--retention` parameter (where a reduction can increase the execution time as excess
 snapshots are removed).
 
-In the example configuration above (for **Azure Large Instance**), snapshots for the
+In the example configuration provided for **Azure Large Instance**, snapshots for the
 two volumes took less than 5 seconds to complete. For **Azure NetApp Files**, snapshots for the two volumes
 would take about 60 seconds.
 
@@ -100,15 +100,15 @@ needs to remove the extra snapshots.
 azacsnap -c backup --volume data --prefix hana_TEST --retention 9 --trim
 ```
 
-The command does not output to the console, but does write to a log file, a result file,
+The command doesn't output to the console, but does write to a log file, a result file,
 and `/var/log/messages`.
 
-In this example the *log file* name is `azacsnap-backup-azacsnap.log` (see [Log files](#log-files))
+In this example, the *log file* name is `azacsnap-backup-azacsnap.log` (see [Log files](#log-files)).
 
-When running the `-c backup` with the `--volume data` option a result file is also generated as a file to allow
-for quickly checking the result of a backup.  The *result* file has the same base name as the log file, with `.result` as its suffix.
+When running the command `-c backup` with the `--volume data` option, a result file is also generated as a file to allow
+for quickly checking the result of a backup. The *result* file has the same base name as the log file, with `.result` as its suffix.
 
-In this example the *result file* name is `azacsnap-backup-azacsnap.result` and contains the following output:
+In this example, the *result file* name is `azacsnap-backup-azacsnap.result` and contains the following output:
 
 ```bash
 cat logs/azacsnap-backup-azacsnap.result
@@ -144,10 +144,10 @@ Jul  2 06:02:06 server01 azacsnap[114280]: Database # 1 (H80) : completed ok
 azacsnap -c backup --volume other --prefix logs_TEST --retention 9
 ```
 
-The command does not output to the console, but does write to a log file only.  It does _not_ write
+The command doesn't output to the console, but does write to a log file only. It does _not_ write
 to a result file or `/var/log/messages`.
 
-In this example the *log file* name is `azacsnap-backup-azacsnap.log` (see [Log files](#log-files)).
+In this example, the *log file* name is `azacsnap-backup-azacsnap.log` (see [Log files](#log-files)).
 
 ## Example with `other` parameter (to backup host OS)
 
@@ -163,14 +163,14 @@ azacsnap -c backup --volume other --prefix boot_TEST --retention 9 --configfile
 > For Azure Large Instance, the configuration file volume parameter for the boot volume might not be visible at the host operating system level.
 > This value can be provided by Microsoft Operations.
 
-The command does not output to the console, but does write to a log file only.  It does _not_ write
+The command doesn't output to the console, but does write to a log file only. It does _not_ write
 to a result file or `/var/log/messages`.
 
-In this example the *log file* name is `azacsnap-backup-bootVol.log` (see [Log files](#log-files)).
+In this example, the *log file* name is `azacsnap-backup-bootVol.log` (see [Log files](#log-files)).
 
 ## Log files
 
-The log file name is constructed from the following "(command name)-(the `-c` option)-(the config filename)".  For example, if running the command `azacsnap -c backup --configfile h80.json --retention 5 --prefix one-off` then the log file will be called `azacsnap-backup-h80.log`.  Or if using the `-c test` option with the same configuration file (e.g. `azacsnap -c test --configfile h80.json`) then the log file will be called `azacsnap-test-h80.log`.
+The log file name is constructed from the following "(command name)-(the `-c` option)-(the config filename)". For example, if running the command `azacsnap -c backup --configfile h80.json --retention 5 --prefix one-off` then the log file is called `azacsnap-backup-h80.log`. Or if using the `-c test` option with the same configuration file (e.g. `azacsnap -c test --configfile h80.json`) then the log file is called `azacsnap-test-h80.log`.
 
 > [!NOTE]
 > Log files can be automatically maintained using [this guide](azacsnap-tips.md#manage-azacsnap-log-files).