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

Author: duongau

articles/azure-resource-manager/bicep/data-types.md

@@ -2,7 +2,7 @@
 title: Data types in Bicep
 description: This article describes the data types that are available in Bicep.
 ms.topic: reference
-ms.date: 06/30/2025
+ms.date: 07/07/2025
 ms.custom: devx-track-bicep
 ---
 
@@ -437,6 +437,16 @@ The union type has some limitations:
 
 You can use the union type syntax in [user-defined data types](./user-defined-data-types.md).
 
+## Nullable types
+
+You can make any primitive or complex type nullable by appending a `?` to the type name. This allows the parameter, variable, or output to accept null as a valid value. For example:
+
+```bicep
+output description string? = null
+output config object? = null
+output optionalValue int? = null
+```
+
 ## Secure strings and objects
 
 Secure strings use the same format as string, and secure objects use the same format as object. With Bicep, you add the `@secure()` [decorator](./parameters.md#use-decorators) to a string or object.

articles/azure-resource-manager/templates/template-functions-array.md

@@ -3,7 +3,7 @@ title: Template functions - arrays
 description: Describes the functions to use in an Azure Resource Manager template (ARM template) for working with arrays.
 ms.topic: reference
 ms.custom: devx-track-arm-template
-ms.date: 02/12/2025
+ms.date: 07/07/2025
 ---
 
 # Array functions for ARM templates
@@ -223,6 +223,57 @@ The output from the preceding example with the default values is:
 | arrayOutput | String | one |
 | stringOutput | String | O |
 
+## indexFromEnd
+
+`indexFromEnd(sourceArray, reverseIndex)`
+
+Returns an element of the array by counting backwards from the end. This is useful when you want to reference elements starting from the end of a list, rather than the beginning. The [`tryIndexFromEnd`](#tryindexfromend) function is a safe version of `indexFromEnd`.
+
+In Bicep, use the [Reserved index accessor](../bicep/operators-access.md#reverse-index-accessor) operator.
+
+### Parameters
+
+| Parameter | Required | Type | Description |
+|:--- |:--- |:--- |:--- |
+| sourceArray |Yes |array |The value to retrieve the element by counting backwards from the end. |
+| reverseIndex |Yes |integer |The one-based index from the end of the array. |
+
+### Return value
+
+A single element from an array, selected by counting backward from the end of the array.
+
+### Example
+
+The following example shows how to use the `indexFromEnd` function.
+
+```json
+{
+  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
+  "contentVersion": "1.0.0.0",
+  "variables": {
+    "items": [
+      "apple",
+      "banana",
+      "orange",
+      "grape"
+    ]
+  },
+  "resources": [],
+  "outputs": {
+    "secondToLast": {
+      "type": "string",
+      "value": "[indexFromEnd(variables('items'), 2)]"
+    }
+  }
+}
+```
+
+The output from the preceding example with the default values is:
+
+| Name | Type | Value |
+| ---- | ---- | ----- |
+| secondToLast | String | orange |
+
 ## indexOf
 
 `indexOf(arrayToSearch, itemToFind)`
@@ -693,6 +744,92 @@ The output from the preceding example with the default values is:
 | arrayOutput | Array | ["one", "two"] |
 | stringOutput | String | on |
 
+## tryIndexFromEnd
+
+`tryndexFromEnd(sourceArray, reverseIndex)`
+
+The `tryIndexFromEnd` function is a safe version of [`indexFromEnd`](#indexfromend). It retrieves a value from an array by counting backward from the end without throwing an error if the index is out of range.
+
+In Bicep, use the [Reserved index accessor](../bicep/operators-access.md#reverse-index-accessor) operator and the [Safe dereference](../bicep/operator-safe-dereference.md#safe-dereference) operator.
+
+### Parameters
+
+| Parameter | Required | Type | Description |
+|:--- |:--- |:--- |:--- |
+| sourceArray |Yes |array |The value to retrieve the element by counting backwards from the end. |
+| reverseIndex |Yes |integer |The one-based index from the end of the array. |
+
+### Return value
+
+If the index is valid (within array bounds), returns the array element at that reverse index. If the index is out of range, returns null instead of throwing an error.
+
+### Example
+
+The following example shows how to use the `tryIndexFromEnd` function:
+
+```json
+{
+  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
+  "contentVersion": "1.0.0.0",
+  "variables": {
+    "items": [
+      "apple",
+      "banana",
+      "orange",
+      "grape"
+    ]
+  },
+  "resources": [],
+  "outputs": {
+    "secondToLast": {
+      "type": "string",
+      "value": "[tryIndexFromEnd(variables('items'), 2)]"
+    }
+  }
+}
+```
+
+The output from the preceding example with the default values is:
+
+| Name | Type | Value |
+| ---- | ---- | ----- |
+| secondToLast | String | orange |
+
+The following example shows an out-of-bound scenario:
+
+```json
+{
+  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
+  "languageVersion": "2.0",
+  "contentVersion": "1.0.0.0",
+  "parameters": {
+    "items": {
+      "type": "array",
+      "defaultValue": [
+        "apple",
+        "banana",
+        "orange",
+        "grape"
+      ]
+    }
+  },
+  "resources": {},
+  "outputs": {
+    "outOfBound": {
+      "type": "string",
+      "nullable": true,
+      "value": "[tryIndexFromEnd(parameters('items'), 5)]"
+    }
+  }
+}
+```
+
+The output from the preceding example with the default values is:
+
+| Name | Type | Value |
+| ---- | ---- | ----- |
+| outOfBound | String | (null) |
+
 ## union
 
 `union(arg1, arg2, arg3, ...)`

articles/azure-resource-manager/templates/template-functions.md

@@ -3,7 +3,7 @@ title: Template functions
 description: Describes the functions to use in an Azure Resource Manager template (ARM template) to retrieve values, work with strings and numerics, and retrieve deployment information.
 ms.topic: reference
 ms.custom: devx-track-arm-template
-ms.date: 02/12/2025
+ms.date: 07/07/2025
 ---
 
 # ARM template functions
@@ -29,6 +29,7 @@ The [any function](../bicep/bicep-functions-any.md) is available in Bicep to hel
 <a id="createarray" aria-hidden="true"></a>
 <a id="empty" aria-hidden="true"></a>
 <a id="first" aria-hidden="true"></a>
+<a id="indexfromend" aria-hidden="true"></a>
 <a id="indexof" aria-hidden="true"></a>
 <a id="intersection" aria-hidden="true"></a>
 <a id="last" aria-hidden="true"></a>
@@ -39,6 +40,7 @@ The [any function](../bicep/bicep-functions-any.md) is available in Bicep to hel
 <a id="range" aria-hidden="true"></a>
 <a id="skip" aria-hidden="true"></a>
 <a id="take" aria-hidden="true"></a>
+<a id="tryindexfromend" aria-hidden="true"></a>
 <a id="union" aria-hidden="true"></a>
 
 ## Array functions
@@ -51,6 +53,7 @@ Resource Manager provides several functions for working with arrays.
 * [createArray](template-functions-array.md#createarray)
 * [empty](template-functions-array.md#empty)
 * [first](template-functions-array.md#first)
+* [indexFromEnd](template-functions-array.md#indexfromend)
 * [indexOf](template-functions-array.md#indexof)
 * [intersection](template-functions-array.md#intersection)
 * [last](template-functions-array.md#last)
@@ -61,6 +64,7 @@ Resource Manager provides several functions for working with arrays.
 * [range](template-functions-array.md#range)
 * [skip](template-functions-array.md#skip)
 * [take](template-functions-array.md#take)
+* [tryIndexFromEnd](template-functions-array.md#tryindexfromend)
 * [union](template-functions-array.md#union)
 
 For Bicep files, use the [array](../bicep/bicep-functions-array.md) functions.

articles/azure-resource-manager/templates/toc.yml

@@ -293,6 +293,7 @@ items:
   - name: Template best practices
     href: best-practices.md
   - name: Data types
+    displayName: nullable types,union type,secure strings,secure objects,data type assignability
     href: data-types.md
   - name: Frequently asked questions
     href: frequently-asked-questions.yml
@@ -469,7 +470,7 @@ items:
     - name: All functions
       href: template-functions.md
     - name: Array functions
-      displayName: array,concat,contains,createArray,empty,first,indexOf,intersection,last,lastIndexOf,length,max,min,range,skip,take,union
+      displayName: array,concat,contains,createArray,empty,first,indexFromEnd,indexOf,intersection,last,lastIndexOf,length,max,min,range,skip,take,tryIndexFromEdn,union
       href: template-functions-array.md
     - name: CIDR functions
       displayName: parseCidr,cidrSubnet,cidrHost

articles/cost-management-billing/reservations/prepare-buy-reservation.md

@@ -6,7 +6,7 @@ ms.reviewer: primittal
 ms.service: cost-management-billing
 ms.subservice: reservations
 ms.topic: how-to
-ms.date: 03/26/2025
+ms.date: 07/08/2025
 ms.author: primittal
 ---
 
@@ -24,7 +24,7 @@ You can't buy a reservation if you have a custom role that mimics owner role or
 
 Enterprise Agreement (EA) customers can limit purchases to EA admins by disabling the **Reserved Instances** policy option in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_GTM/ModernBillingMenuBlade/BillingAccounts). To change settings, navigate to the **Policies** menu.
 
-Microsoft Customer Agreement (MCA), Billing Profile Owners can restrict the reservation purchase by disabling the **Reserved Instances** policy option in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_GTM/ModernBillingMenuBlade/BillingAccounts). Beginning in June 2025, Microsoft Customer Agreement (MCA), Billing Profile, and Billing Account Owners will have the ability to purchase Reservations even if the Reserved Instances policy option is disabled in the Azure portal. To change settings, navigate to the **Policies** menu under **Billing Profile**.
+Microsoft Customer Agreement (MCA), Billing Profile Owners can restrict the reservation purchase by disabling the **Reserved Instances** policy option in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_GTM/ModernBillingMenuBlade/BillingAccounts). Billing Profile, and Billing Account Owners will have the ability to purchase Reservations even if the Reserved Instances policy option is disabled in the Azure portal. You can change the settings in **Policies** menu under **Billing Profile** to control ability to purchase for RBAC users.
 
 EA admins or Billing Profile Owners must have owner or reservation purchaser access on at least one EA or MCA subscription to purchase a reservation. The option is useful for enterprises that want a centralized team to purchase reservations.
 

articles/data-factory/media/connector-azure-cosmos-db/configure-azure-cosmos-db-linked-service.png

@@ -0,0 +1,52 @@
+---
+title: DNS Record Types and IPv6 Support in Azure Traffic Manager
+description: Configure DNS record types in Azure Traffic Manager. Learn how AAAA, A, and CNAME records enable IPv6 and IPv4 support for dual-stack environments. Start routing traffic today.
+author: asudbring
+ms.topic: concept-article
+ms.date: 06/19/2025
+ms.author: allensu
+#customer intent: As a network administrator, I want to understand which DNS record types Azure Traffic Manager supports, so that I can choose the right configuration for my environment.
+---
+
+# DNS record types and IPv6 support in Azure Traffic Manager
+
+Azure Traffic Manager is a DNS-based traffic load balancer that distributes traffic across global Azure regions. To effectively route traffic to your applications, Traffic Manager supports multiple DNS record types that work with both IPv4 and IPv6 protocols.
+
+This article explains the DNS record types that Traffic Manager supports and how they enable dual-stack networking environments. You learn about AAAA records for IPv6 addresses, A records for IPv4 addresses, and CNAME records for domain aliasing. Understanding these record types helps you choose the right configuration for your network infrastructure and ensures optimal traffic routing for your applications.
+
+## AAAA records for IPv6 support
+
+AAAA records map domain names to IPv6 addresses. Azure Traffic Manager supports IPv6 records, enabling traffic routing to services accessible over IPv6 addresses. As the internet transitions towards IPv6, Azure Traffic Manager is equipped to handle this newer protocol, ensuring seamless reachability for services.
+
+Azure Traffic Manager now includes these IPv6 capabilities:
+
+- **IPv6 Maps in DNS Nameservers**: Enables efficient IPv6 address management and resolution by including IPv6 address space in internal DNS maps, providing low-latency resolution for global IPv6 clients.
+
+- **IPv6 Client Subnet (ECS) Support**: Enables geographically accurate traffic routing by using part of the client's IPv6 address through EDNS Client Subnet extension, reducing latency for end users. ECS is used in Performance, Subnet, and Geographic Routing methods.
+
+- **IPv6 Subnet Overrides**: Lets you control traffic routing based on the source IP address of DNS queries, supporting both IPv4 and IPv6 addresses.
+
+These enhancements give full support for IPv6 AAAA record types and provide robust traffic management in IPv6 environments.
+
+## A records for IPv4 addresses
+
+A records map domain names to IPv4 addresses. IPv4 is the backbone of the internet and is still widely used, even as IPv6 adoption grows. Azure Traffic Manager supports IPv4 records, so your existing services and infrastructure stay compatible.
+
+## CNAME records for domain aliasing
+
+CNAME (canonical name) records map an alias name to a `trafficmanager.net` domain name. Azure Traffic Manager supports CNAME records as endpoints, so you can route traffic to a domain name instead of a specific IP address.
+
+CNAME records simplify DNS configuration management. You can handle changes to IP addresses at the authoritative DNS level without changing settings in Azure Traffic Manager, so DNS management is more efficient and scalable.
+
+For example, a domain like `www.contoso.com` can point to `contoso.trafficmanager.net`. You can manage changes to backend service IP addresses centrally without updating the user-facing domain.
+
+## Dual-stack support in Traffic Manager
+
+Azure Traffic Manager is dual stack at the DNS level, so it responds to both A (IPv4) and AAAA (IPv6) DNS queries. This dual stack capability is available only when you use CNAME-based endpoints, because A and AAAA records respond only to their respective query types. Clients connect over the protocol their network or device prefers, based on standard DNS resolution behavior.
+
+For most production scenarios, use DNS-based (CNAME) endpoints. This approach gives you flexibility, simplifies management, and ensures compatibility with both IPv4 and IPv6 clients.
+
+> [!NOTE]
+> Traffic Manager doesn't support setting up separate endpoints within the same profile that use different DNS record types (like one A and one AAAA). This setup ensures that DNS responses from Traffic Manager match the record type the client requests.
+
+