Merge pull request #289209 from MicrosoftDocs/main

Publish to live, Friday 4 AM PST, 10/25

Author: ttorble

articles/application-gateway/application-gateway-secure-flag-session-affinity.md

@@ -0,0 +1,55 @@
+---
+title: Setting HTTPOnly or Secure flag for Session Affinity cookie
+titleSuffix: Azure Application Gateway
+description: Learn how to set HTTPOnly or Secure flag for Session Affinity cookie
+services: application-gateway
+author: jaesoni
+ms.service: azure-application-gateway
+ms.topic: how-to
+ms.date: 10/22/2024
+ms.author: jaysoni 
+---
+
+# Setting HTTPOnly or Secure flag for Session Affinity cookie
+In this guide you learn to create a Rewrite set for your Application Gateway and configure Secure and HttpOnly [ApplicationGatewayAffinity cookie](configuration-http-settings.md#cookie-based-affinity).
+
+
+## Prerequisites
+* You must have an Azure subscription. You can create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) before you begin.
+* An existing Application Gateway resource configured with at least one Listener, Rule, Backend Setting and Backend Pool configuration. If you don't have one, you can create one by following the [QuickStart guide](quick-create-portal.md).
+
+## Creating a Rewrite set
+
+1. Sign in to the Azure portal.
+1. Navigate to the required Application Gateway resource.
+1. Select Rewrites in the left pane.
+1. Select Rewrite set.
+1. Under the Name and Association tab
+    1. Specify a name for this new rewrite set.
+    1. Select the routing rules for which you wish to rewrite the ApplicationGatewayAffinity cookie's flag.
+    1. Select Next.
+1. Select "Add rewrite rule"
+    1. Enter a name for the rewrite rule.
+    1. Enter a numeric value for Rule Sequence field.
+1. Select "Add condition"
+1. Now open the "If" condition box and use the following details.
+    1. Type of variable to check - HTTP header
+    1. Header type - Response header
+    1. Header name - Common header
+    1. Common header - Set-Cookie
+    1. Case-sensitive - No
+    1. Operator - equal (=)
+    1. Pattern to match - (.*)
+    1. To save these details, select **OK**.
+1. Go to the **Then** box to specify action details.
+    1. Rewrite type - Response header
+    1. Action type - Set
+    1. Header name - Common header
+    1. Common header - Set-Cookie
+    1. Header value - {http_resp_Set-Cookie_1}; HttpOnly; Secure
+    1. Select **OK**
+1. Select Update to save the rewrite set configurations.
+
+
+## Next steps
+[Visit other configurations of a Backend Setting](configuration-http-settings.md)

articles/application-gateway/rewrite-http-headers-url.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: azure-application-gateway
 ms.topic: how-to
-ms.date: 4/05/2021
+ms.date: 10/22/2024
 ms.author: greglin
 ---
 
@@ -72,7 +72,7 @@ In the below example whenever the request URL contains */article*, the URL path
 
     f. Enter a regular expression pattern. In this example, we'll use the pattern `.*article/(.*)/(.*)`
 
-      ( ) is used to capture the substring for later use in composing the expression for rewriting the URL path. For more information, see [here](rewrite-http-headers-url.md#capturing).
+      ( ) is used to capture the substring for later use in composing the expression for rewriting the URL path. For more information, see [Pattern matching and capturing](rewrite-http-headers-url.md#pattern-matching-and-capturing).
 
     g. Select **OK**.
 

articles/application-gateway/rewrite-url-portal.md

@@ -267,6 +267,8 @@
           href: add-http-header-rewrite-rule-powershell.md
         - name: Create and rewrite HTTP headers
           href: tutorial-http-header-rewrite-powershell.md
+        - name: Add secure flag for cookies 
+          href: application-gateway-secure-flag-session-affinity.md       
     - name: URL rewrite
       items:
         - name: Azure portal

articles/application-gateway/toc.yml

@@ -6,7 +6,7 @@ author: jianleishen
 ms.subservice: data-movement
 ms.custom: synapse
 ms.topic: conceptual
-ms.date: 10/09/2024
+ms.date: 10/24/2024
 ms.author: jianleishen
 ---
 
@@ -82,6 +82,8 @@ If you use the recommended driver version, the following properties are supporte
 | database | Your MariaDB database name. | Yes |
 | username | Your user name. | Yes |
 | password | The password for the user name. Mark this field as SecureString to store it securely. Or, you can [reference a secret stored in Azure Key Vault](store-credentials-in-key-vault.md). | Yes |
+| sslMode | This option specifies whether the driver uses TLS encryption and verification when connecting to MariaDB. E.g., `SSLMode=<0/1/2/3/4>`.<br/>Options: DISABLED (0) / PREFERRED (1) / REQUIRED (2) / VERIFY_CA (3) / VERIFY_IDENTITY (4) **(Default)** | Yes |
+| useSystemTrustStore | This option specifies whether to use a CA certificate from the system trust store, or from a specified PEM file. E.g. `UseSystemTrustStore=<0/1>`;<br/>Options: Enabled (1) / Disabled (0) **(Default)** | No |
 | connectVia | The [Integration Runtime](concepts-integration-runtime.md) to be used to connect to the data store. Learn more from [Prerequisites](#prerequisites) section. If not specified, it uses the default Azure Integration Runtime. |No |
 
 **Example:**
@@ -100,7 +102,9 @@ If you use the recommended driver version, the following properties are supporte
                 "type": "SecureString",
                 "value": "<password>"
             },
-            "driverVersion": "v2"
+            "driverVersion": "v2",
+            "sslMode": <sslmode>,
+            "useSystemTrustStore": <UseSystemTrustStore>
         },
         "connectVia": {
             "referenceName": "<name of Integration Runtime>",
@@ -130,7 +134,9 @@ If you use the recommended driver version, the following properties are supporte
                 },
                 "secretName": "<secretName>"
             },
-            "driverVersion": "v2"
+            "driverVersion": "v2",
+            "sslMode": <sslmode>,
+            "useSystemTrustStore": <UseSystemTrustStore>
         },
         "connectVia": {
             "referenceName": "<name of Integration Runtime>",

articles/data-factory/connector-mariadb.md

@@ -6,8 +6,8 @@ ms.author: vibansa
 ms.manager: abhemraj
 ms.service: azure-migrate
 ms.topic: conceptual
-ms.date: 02/24/2023
-ms.custom: engagement-fy23, devx-track-extended-java
+ms.date: 10/25/2024
+ms.custom: engagement-fy25, devx-track-extended-java
 ---
 
 # Metadata discovered by Azure Migrate appliance 
@@ -16,11 +16,11 @@ This article provides details of the metadata discovered by Azure Migrate applia
 
 The [Azure Migrate appliance](migrate-appliance.md) is a lightweight appliance that the Azure Migrate: Discovery and assessment tool uses to discover servers running in your environment and send server configuration and performance metadata to Azure.
 
-Metadata discovered by the Azure Migrate appliance helps you to assess server readiness for migration to Azure, right-size servers and plans costs. Microsoft doesn't use this data in any license compliance audit.
+Metadata discovered by the Azure Migrate appliance helps you to assess server readiness for migration to Azure, right-size servers, and plan costs. Microsoft doesn't use this data in any license compliance audit.
 
 ## Collected metadata for VMware servers
 
-The appliance collects configuration, performance metadata, data about installed applications, roles and features (software inventory) and dependency data (if agentless dependency analysis is enabled) from servers running in your VMware environment.
+The appliance collects configuration, performance metadata, data about installed applications, roles, and features (software inventory) and dependency data (if agentless dependency analysis is enabled) from servers running in your VMware environment.
 
 Here's the full list of server metadata that the appliance collects and sends to Azure:
 
@@ -88,7 +88,7 @@ NIC writes throughput (MB per second) | net.transmitted.average  |Calculation fo
 
 ## Collected metadata for Hyper-V servers
 
-The appliance collects configuration, performance metadata, data about installed applications, roles and features (software inventory) and dependency data (if agentless dependency analysis is enabled) from servers running in your Hyper-V environment.
+The appliance collects configuration, performance metadata, data about installed applications, roles, and features (software inventory) and dependency data (if agentless dependency analysis is enabled) from servers running in your Hyper-V environment.
 
 Here's the full list of server metadata that the appliance collects and sends to Azure.
 
@@ -100,7 +100,7 @@ Server type (Gen 1 or 2) | Msvm_VirtualSystemSettingData | VirtualSystemSubType
 Server display name | Msvm_VirtualSystemSettingData | ElementName
 Server version | Msvm_ProcessorSettingData | VirtualQuantity
 Memory (bytes) | Msvm_MemorySettingData | VirtualQuantity
-Maximum memory that can be consumed by server | Msvm_MemorySettingData | Limit
+Maximum memory that the server can consume | Msvm_MemorySettingData | Limit
 Dynamic memory enabled | Msvm_MemorySettingData | DynamicMemoryEnabled
 Operating system name/version/FQDN | Msvm_KvpExchangeComponent | GuestIntrinsicExchangeItems Name Data
 Server power status | Msvm_ComputerSystem | EnabledState
@@ -136,7 +136,7 @@ Hyper-V Virtual Network Adapter | Bytes Sent/Second | Calculation for server siz
 
 ## Collected data for Physical servers
 
-The appliance collects configuration, performance metadata, data about installed applications, roles and features (software inventory) and dependency data (if agentless [dependency analysis](concepts-dependency-visualization.md) is enabled) from physical servers or server running on other clouds like AWS, GCP, etc.
+The appliance collects configuration, performance metadata, data about installed applications, roles, and features (software inventory) and dependency data (if agentless [dependency analysis](concepts-dependency-visualization.md) is enabled) from physical servers or server running on other clouds like AWS, GCP, etc.
 
 ### Windows server metadata
 
@@ -180,7 +180,7 @@ Here's the full list of Linux server metadata that the appliance collects and se
 **Data** | **Commands**
 --- | ---
 FQDN | cat /proc/sys/kernel/hostname, hostname -f
-Processor core count |  cat/proc/cpuinfo \| awk '/^processor/{print $3}' \| wc -l
+Processor core count |  cat /proc/cpuinfo \| awk '/^processor/{print $3}' \| wc -l
 Memory allocated | cat /proc/meminfo \| grep MemTotal \| awk '{printf "%.0f", $2/1024}'
 BIOS serial number | lshw \| grep "serial:" \| head -n1 \| awk '{print $2}' <br/> /usr/sbin/dmidecode -t 1 \| grep 'Serial' \| awk '{ $1="" ; $2=""; print}'
 BIOS GUID | cat /sys/class/dmi/id/product_uuid
@@ -210,7 +210,7 @@ Here's the Linux server performance data that the appliance collects and sends t
 
 ## Software inventory data
 
-The appliance collects data about installed applications, roles and features (software inventory) from servers running in VMware environment/Hyper-V environment/physical servers or servers running on other clouds like AWS, GCP etc.
+The appliance collects data about installed applications, roles, and features (software inventory) from servers running in VMware environment/Hyper-V environment/physical servers or servers running on other clouds like AWS, GCP etc.
 
 ### Windows server applications data
 

articles/data-factory/media/connector-mariadb/configure-mariadb-linked-service.png

@@ -43,7 +43,7 @@ gcc --version
 To complete this tutorial on Windows, install the following software on your local Windows environment:
 
 * [Visual Studio (Community, Professional, or Enterprise)](https://visualstudio.microsoft.com/downloads/) - make sure you include the **Desktop Development with C++** workload when you [install](/cpp/build/vscpp-step-0-installation?preserve-view=true&view=vs-2019) Visual Studio.
-* [Git](https://git-scm.com/download/).
+* [Git](https://git-scm.com/downloads).
 * [CMake](https://cmake.org/download/).
 
 ## Download the code

articles/migrate/discovered-metadata.md

@@ -43,7 +43,7 @@ gcc --version
 To complete this tutorial on Windows, install the following software in your local Windows environment:
 
 * [Visual Studio (Community, Professional, or Enterprise)](https://visualstudio.microsoft.com/downloads/) - make sure you include the **Desktop Development with C++** workload when you [install](/cpp/build/vscpp-step-0-installation?preserve-view=true&view=vs-2019) Visual Studio.
-* [Git](https://git-scm.com/download/).
+* [Git](https://git-scm.com/downloads).
 * [CMake](https://cmake.org/download/).
 
 ## Download the code

includes/iot-central-connect-device-c.md

@@ -17,7 +17,7 @@ This tutorial shows you how to build a sample IoT Plug and Play device applicati
 You can run this tutorial on Linux or Windows. The shell commands in this tutorial follow the Linux convention for path separators '`/`', if you're following along on Windows be sure to swap these separators for '`\`'.
 
 * The latest [.NET SDK](https://dotnet.microsoft.com/download) for your platform.
-* [Git](https://git-scm.com/download/).
+* [Git](https://git-scm.com/downloads).
 
 ## Download the code