Merge branch 'main' into release-defender-flip

Author: v-alje

articles/application-gateway/monitor-application-gateway-reference.md

@@ -46,7 +46,7 @@ For Application Gateway v2 SKU, the following metrics are available. What follow
 - **Client TLS protocol**. Count of TLS and non-TLS requests.
 - **Current capacity units**. There are three determinants to capacity unit: compute unit, persistent connections, and throughput. Each capacity unit is composed of at most one compute unit, or 2500 persistent connections, or 2.22-Mbps throughput.
 - **Current compute units**. Factors affecting compute unit are TLS connections/sec, URL Rewrite computations, and WAF rule processing.
-- **Current connections**. The total number of concurrent connections active from clients to the Application Gateway.
+- **Current connections**. The total number of concurrent connections active from clients to the Application Gateway, including probes for the health of the application gateway's instances.
 - **Estimated Billed Capacity units**. With the v2 SKU, consumption drives the pricing model. Capacity units measure consumption-based cost that is charged in addition to the fixed cost. *Estimated Billed Capacity units indicate the number of capacity units using which the billing is estimated. This amount is calculated as the greater value between *Current capacity units* (capacity units required to load balance the traffic) and *Fixed billable capacity units* (minimum capacity units kept provisioned).
 - **Failed Requests**. This value includes the 5xx codes that are generated from the Application Gateway and the 5xx codes that are generated from the backend. The request count can be further filtered to show count per each/specific backend pool-http setting combination.
 - **Fixed Billable Capacity Units**. The minimum number of capacity units kept provisioned as per the *Minimum scale units* setting in the Application Gateway configuration. One instance translates to 10 capacity units.

articles/azure-app-configuration/concept-private-endpoint.md

@@ -59,7 +59,7 @@ If you are using a custom DNS server on your network, you need to configure it t
 
 ## Pricing
 
-Enabling private endpoints requires a [Standard or Premium tier](https://azure.microsoft.com/pricing/details/app-configuration/) App Configuration store. To learn about private link pricing details, see [Azure Private Link pricing](https://azure.microsoft.com/pricing/details/private-link).
+Enabling private endpoints requires a [Developer, Standard or Premium tier](https://azure.microsoft.com/pricing/details/app-configuration/) App Configuration store. To learn about private link pricing details, see [Azure Private Link pricing](https://azure.microsoft.com/pricing/details/private-link).
 
 ## Troubleshooting private endpoint errors
 

articles/azure-app-configuration/concept-snapshots.md

@@ -45,7 +45,7 @@ As snapshots are immutable entities, snapshots can only be created and archived.
 * **Recover snapshot**: Recovering a snapshot puts it back in an active state. At this point, the snapshot is no longer subject to expiration based on its configured retention period. Recovery is only possible in the retention period after archival.
 
 > [!NOTE]
-> The retention period can only be set during the creation of a snapshot. The default value for retention period is 30 days for Standard stores and 7 days for Free stores.
+> The retention period can only be set during the creation of a snapshot. The default value for retention period is 30 days for Standard and Premium tier stores and 7 days for Free and Developer tier stores.
 
 ## Requirements for snapshot operations
 

articles/azure-app-configuration/faq.yml

@@ -68,42 +68,59 @@ sections:
           
       - question: How much does App Configuration cost?
         answer: |
-          There are three pricing tiers: Free, Standard, and Premium. For detailed pricing information, refer to the [App Configuration pricing](https://azure.microsoft.com/en-us/pricing/details/app-configuration/) page.
+          There are four pricing tiers: Free, Developer, Standard, and Premium. For detailed pricing information, refer to the [App Configuration pricing](https://azure.microsoft.com/en-us/pricing/details/app-configuration/) page.
 
       - question: Which App Configuration tier should I use?
         answer: |
           All App Configuration tiers offer core functionality, including config settings, feature flags, Key Vault references, configuration snapshots, basic management operations, metrics, and logs.
           
           The following are considerations for choosing a tier.
 
-          - **Purpose**: The Free tier is perfect for evaluating the service in non-production environments, allowing you to explore its features without any cost. The Standard tier is tailored for medium-volume production use cases, providing a balance of performance and cost-efficiency. For high-volume or enterprise-level production needs, the Premium tier offers the highest level of performance and scalability, ensuring your applications run smoothly even under heavy load.
-          - **Resources per subscription**: A resource consists of a single configuration store. Each subscription is limited to one configuration store per region in the Free tier. Subscriptions can have an unlimited number of configuration stores in the Standard and Premium tiers.
-          - **Storage per resource**: In the Free tier, each configuration store is limited to 10 MB of regular storage and 10 MB of snapshot storage. In the Standard tier, each configuration store can use up to 1 GB of regular storage and an additional 1 GB of snapshot storage. In the Premium tier, each configuration store can use up to 4 GB of regular storage and an additional 4 GB of snapshot storage.
-          - **Revision history**: App Configuration stores a history of all changes made to keys. In the Free tier, this history is stored for seven days. In the Standard and Premium tiers, this history is stored for 30 days.
+          - **Purpose**: The Free tier is perfect for evaluating the service in non-production environments, allowing you to explore its features without any cost.
+
+              The Developer tier is cost-efficient for low-volume, non-production use cases and comes equipped with features and capabilities specifically tailored for development and testing needs.
+
+              The Standard tier is designed for medium-volume production and non-production use cases, providing a balance of performance and cost-efficiency.
+
+              For high-volume or enterprise-level production needs, the Premium tier offers the highest level of performance and scalability, ensuring your applications run smoothly even under heavy loads.
+
+          - **Resources per subscription**: A resource consists of a single configuration store. Each subscription is limited to one configuration store per region in the Free tier. Subscriptions can have an unlimited number of configuration stores in the Developer, Standard and Premium tiers.
+          - **Storage per resource**: In the Free tier, each configuration store is limited to 10 MB of regular storage and 10 MB of snapshot storage. In the Developer tier, each configuration store can use up to 500 MB of regular storage and an additional 500 MB of snapshot storage. In the Standard tier, each configuration store can use up to 1 GB of regular storage and an additional 1 GB of snapshot storage. In the Premium tier, each configuration store can use up to 4 GB of regular storage and an additional 4 GB of snapshot storage.
+          - **Revision history**: App Configuration stores a history of all changes made to keys. In the Free and Developer tiers, this history is stored for seven days. In the Standard and Premium tiers, this history is stored for 30 days.
           - **Requests quota**: Free tier stores are limited to 1,000 requests per day. When a store reaches 1,000 requests, it returns HTTP status code 429 for all requests until midnight UTC.
+
+              Developer tier stores are limited to 6,000 requests per hour. Once the hourly quota is exhausted, additional requests return an HTTP status code 429, indicating too many requests, until the end of the hour.
           
               Standard tier stores are limited to 30,000 requests per hour. Once the hourly quota is exhausted, additional requests may return an HTTP status code 429, indicating too many requests, until the end of the hour. As more requests are sent which are above quota, a higher percentage of them may return status code 429. 
 
               Premium tier stores have no quota limit on requests, ensuring that access to the store is never blocked.
           - **Throughput**: App Configuration stores in all tiers have a throughput allowance. Requests exceeding this allowance receive an HTTP status code 429 response.
-              Stores in the Free tier have no guaranteed throughput.
+
+              Stores in the Free tier and Developer tier have no guaranteed throughput.
 
               Stores in the Standard tier allow run rate† up to 300 requests per second (RPS) for read requests and up to 60 RPS for write requests.
 
               Stores in the Premium tier allow run rate† up to 450 RPS for read requests and up to 100 RPS for write requests.
 
               †The run rate is typically measured as the average number of requests handled by an App Configuration store without throttling over a specified period.
-          - **Service level agreement**: The Free tier doesn't have an SLA. The Standard tier has an SLA of 99.9% availability and 99.95% availability with geo-replication enabled. The Premium tier has an SLA of 99.9% availability and 99.99% availability with geo-replication enabled.
-          - **Features**: All tiers include functionalities, including encryption with Microsoft-managed keys, authentication via access key or Microsoft Entra ID, Azure role-based access control (RBAC), managed identity, service tags, and availability zone redundancy. The Standard and Premium tiers offer more functionalities, including Private Link support, encryption with customer-managed keys, soft delete protection, and geo-replication capability.
+          - **Service level agreement**: The Free tier and Developer tier don't have an SLA. The Standard tier has an SLA of 99.9% availability and 99.95% availability with geo-replication enabled. The Premium tier has an SLA of 99.9% availability and 99.99% availability with geo-replication enabled.
+          - **Features**: All tiers include functionalities, including encryption with Microsoft-managed keys, authentication via access key or Microsoft Entra ID, Azure role-based access control (RBAC), managed identity, service tags, and availability zone redundancy.
+
+              The Developer tier also includes support for Private Link.
+
+              The Standard and Premium tiers offer more functionalities, including Private Link support, encryption with customer-managed keys, soft delete protection, and geo-replication capability.
+
           - **Cost**: There's no cost to use a Free tier store.
 
+              Developer tier stores have a daily usage charge, which includes the first 3,000 requests each day. Requests beyond this daily allocation incur an overage charge.
+
               Standard tier stores have a daily usage charge, which includes the first 200,000 requests each day. Requests beyond this daily allocation incur an overage charge.
 
               Premium tier stores also have a daily usage charge and include a replica. The first 800,000 requests for the origin and the first 800,000 requests for the replica each day are included in the daily charge. Requests exceeding this daily allocation incur an overage charge.
           
       - question: Can I upgrade or downgrade an App Configuration store?
         answer: |
-          You can upgrade an App Configuration store at any time, for example, from the Free tier to the Standard or Premium tier, or from the Standard tier to the Premium tier.
+          You can upgrade an App Configuration store at any time, for example, from the Free tier to the Developer, Standard or Premium tier, or from the Developer, Standard tier to the Premium tier.
           
           You can downgrade an App Configuration store from the Premium tier to the Standard tier, as both tiers are designed for production usage. However, downgrading to a non-production tier, such as the Free tier, is not supported. To achieve this, you can create a new store in the desired tier and then [import configuration data into that store](howto-import-export-data.md).
           
@@ -123,9 +140,9 @@ sections:
 
       - question: Are there any limits on the number of requests made to App Configuration?
         answer: |        
-          App Configuration stores have different request quotas based on their tier. Free tier stores are limited to 1,000 requests per day, Standard tier stores to 30,000 requests per hour, and Premium tier stores have no request limits, ensuring uninterrupted access.
+          App Configuration stores have different request quotas based on their tier. Free tier stores are limited to 1,000 requests per day, Developer tier stores to 6,000 requests per hour, Standard tier stores to 30,000 requests per hour, and Premium tier stores have no request limits, ensuring uninterrupted access.
 
-          App Configuration stores have throughput allowances based on their tier. Free tier stores don't have guaranteed throughput. Standard tier stores support run rate up to 300 requests per second (RPS) for read operations and up to 60 RPS for write operations. Premium tier stores support run rate up to 450 RPS for read operations and up to 100 RPS for write operations.
+          App Configuration stores have throughput allowances based on their tier. Free tier and Developer tier stores don't have guaranteed throughput. Standard tier stores support run rate up to 300 requests per second (RPS) for read operations and up to 60 RPS for write operations. Premium tier stores support run rate up to 450 RPS for read operations and up to 100 RPS for write operations.
 
       - question: How do I estimate the number of requests my application may send to App Configuration?
         answer: |
@@ -146,6 +163,7 @@ sections:
           Your application may receive an HTTP status code 429 response under the following circumstances:
 
           - Exceeding the daily request quota for a store in the Free tier.
+          - Exceeding the hourly request quota for a store in the Developer tier.
           - Exceeding the hourly request quota for a store in the Standard tier.
           - Exceeding the throughput allowance for a store in any tier.
           - Exceeding the bandwidth allowance for a store in any tier.

articles/azure-app-configuration/howto-recover-deleted-stores-in-azure-app-configuration.md

@@ -53,7 +53,7 @@ To create a new App Configuration store in the  Azure portal, follow these steps
 ## Enable Purge Protection in an existing store
 
 1. Log in to the Azure portal.
-1. Select your standard tier App Configuration store.
+1. Select your Standard or Premium tier App Configuration store.
 1. Refer to the screenshot below on where to check for the soft delete status of an existing store.
 
     :::image type="content" source="./media/how-to-soft-delete-app-config-1.png" alt-text="In Overview, Soft-delete is highlighted.":::

articles/azure-app-configuration/monitor-app-configuration.md

@@ -179,7 +179,7 @@ The following table lists common and recommended alert rules for App C
 
 | Alert type | Condition | Description  |
 |:---|:---|:---|
-|Request quota usage exceeded | RequestQuotaUsage >= 100 | The configuration store has exceeded the [request quota usage](./faq.yml#are-there-any-limits-on-the-number-of-requests-made-to-app-configuration). Upgrade to a standard tier store or follow the [best practices](./howto-best-practices.md#reduce-requests-made-to-app-configuration) to optimize your usage. |
+|Request quota usage exceeded | RequestQuotaUsage >= 100 | The configuration store has exceeded the [request quota usage](./faq.yml#are-there-any-limits-on-the-number-of-requests-made-to-app-configuration). Upgrade your store or follow the [best practices](./howto-best-practices.md#reduce-requests-made-to-app-configuration) to optimize your usage. |
 
 
 

articles/azure-netapp-files/configure-unix-permissions-change-ownership-mode.md

@@ -1,11 +1,11 @@
 ---
-title: Configure Unix permissions and change ownership mode for Azure NetApp Files NFS and dual-protocol volumes | Microsoft Docs
-description: Describes how to set the Unix permissions and the change ownership mode options for Azure NetApp Files NFS and dual-protocol volumes.
+title: Configure Unix permissions and change ownership mode for Azure NetApp Files NFS and dual-protocol volumes
+description: Learn how to set the Unix permissions and the change ownership mode options for Azure NetApp Files NFS and dual-protocol volumes.
 services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 02/28/2023
+ms.date: 04/25/2025
 ms.author: anfdocs
 ---
 # Configure Unix permissions and change ownership mode for NFS and dual-protocol volumes
@@ -22,31 +22,35 @@ The Unix permissions setting is set to `0770` by default. This default setting g
 
 ## Change ownership mode   
 
-The change ownership mode (**`Chown Mode`**) functionality enables you to set the ownership management capabilities of files and directories.  You can specify or modify the setting under a volume's export policy. Two options for **`Chown Mode`** are available:   
+The change ownership mode (**`Chown Mode`**) functionality enables you to set the ownership management capabilities of files and directories. You can specify or modify the setting under a volume's export policy. Two options for **`Chown Mode`** are available:   
 
 * `Restricted` (default) - Only the root user can change the ownership of files and directories.
 * `Unrestricted` - Non-root users can change the ownership for files and directories that they own.
 
 ## Considerations  
 
 * The Unix permissions you specify apply only for the volume mount point (root directory).  
-* You can modify the Unix permissions on the source volume *but not on the destination volume* that is in a cross-region replication configuration.
+* You can modify the Unix permissions on the source volume *but not the destination volume* that is in a replication configuration.
 
-## Steps
+## Set Unix permissions for new volumes
 
 1. You can specify the **Unix permissions** and change ownership mode (**`Chown Mode`**) settings under the **Protocol** tab when you [create an NFS volume](azure-netapp-files-create-volumes.md) or [create a dual-protocol volume](create-volumes-dual-protocol.md). 
 
-    The following example shows the Create a Volume screen for an NFS volume. 
+    The following example shows the Create a volume screen for an NFS volume. 
 
-    ![Screenshots that shows the Create a Volume screen for NFS.](./media/configure-unix-permissions-change-ownership-mode/unix-permissions-create-nfs-volume.png)
+    ![Screenshot that shows the Create a Volume screen for NFS.](./media/configure-unix-permissions-change-ownership-mode/unix-permissions-create-nfs-volume.png)
 
-2. For existing NFS or dual-protocol volumes, you can set or modify **Unix permissions** and **change ownership mode** as follows:  
+## Set Unix permissions for existing volumes
 
-    1. To modify Unix permissions, right-click the **volume**, and select **Edit**. In the Edit window that appears, specify a value for **Unix Permissions**.  
-        ![Screenshots that shows the Edit screen for Unix permissions.](./media/configure-unix-permissions-change-ownership-mode/unix-permissions-edit.png)
+For existing NFS or dual-protocol volumes, you can set or modify **Unix permissions** and **change ownership mode** as follows:  
 
-    2. To modify the change ownership mode, click the **volume**, click **Export policy**, then modify the **`Chown Mode`** setting.  
-        ![Screenshots that shows the Export Policy screen.](./media/configure-unix-permissions-change-ownership-mode/chown-mode-edit.png)
+1. To modify Unix permissions, right-click the **volume**, and select **Edit**. In the Edit window that appears, specify a value for **Unix Permissions**.
+
+    ![Screenshot that shows the Edit screen for Unix permissions.](./media/configure-unix-permissions-change-ownership-mode/unix-permissions-edit.png)
+
+2. To modify the change ownership mode, select the **volume**, click **Export policy** then modify the **`Chown Mode`** setting.  
+
+    ![Screenshot that shows the Export Policy screen.](./media/configure-unix-permissions-change-ownership-mode/chown-mode-edit.png)
 
 ## Next steps