Merge pull request #260666 from MicrosoftDocs/main

12/7/2023 PM Publish

Author: Taojunshen

articles/ai-services/content-safety/quickstart-protected-material.md

@@ -34,7 +34,7 @@ The following section walks through a sample request with cURL. Paste the comman
     > [!TIP]
     > Text size and granularity
     >
-    > The default maximum length for text submissions is **1K** characters. The minimum length is **110** characters. Protected material detection is meant to be run on LLM completions, not user prompts.
+    > The default maximum length for text submissions is **1K** characters. The minimum length is **111** characters. Protected material detection is meant to be run on LLM completions, not user prompts.
 
 ```shell
 curl --location --request POST '<endpoint>/contentsafety/text:detectProtectedMaterial?api-version=2023-10-15-preview' \

articles/aks/media/quotas-skus-regions/yes-icon.svg

@@ -3,9 +3,9 @@ title: Limits for resources, SKUs, and regions in Azure Kubernetes Service (AKS)
 titleSuffix: Azure Kubernetes Service
 description: Learn about the default quotas, restricted node VM SKU sizes, and region availability of the Azure Kubernetes Service (AKS).
 ms.topic: conceptual
-ms.date: 03/07/2023
-
+ms.date: 12/05/2023
 ---
+
 # Quotas, virtual machine size restrictions, and region availability in Azure Kubernetes Service (AKS)
 
 All Azure services set default limits and quotas for resources and features, including usage restrictions for certain virtual machine (VM) SKUs.
@@ -31,7 +31,7 @@ The list of supported VM sizes in AKS is evolving with the release of new VM SKU
 
 ## Restricted VM sizes
 
-VM sizes with less than two CPUs may not be used with AKS.
+VM sizes with fewer than two CPUs may not be used with AKS.
 
 Each node in an AKS cluster contains a fixed amount of compute resources such as vCPU and memory. If an AKS node contains insufficient compute resources, pods might fail to run correctly. To ensure the required *kube-system* pods and your applications can be reliably scheduled, AKS requires nodes use VM sizes with at least two CPUs.
 
@@ -51,13 +51,28 @@ For the latest list of where you can deploy and run clusters, see [AKS region av
 
 When you create a cluster using the Azure portal, you can choose a preset configuration to quickly customize based on your scenario. You can modify any of the preset values at any time.
 
-| Preset           | Description                                                            |
-|------------------|------------------------------------------------------------------------|
-| Standard         | Best if you're not sure what to choose. Works well with most applications. |
-| Dev/Test         | Best for experimenting with AKS or deploying a test application. |
-| Cost-optimized   | Best for reducing costs on production workloads that can tolerate interruptions. |
-| Batch processing | Best for machine learning, compute-intensive, and graphics-intensive workloads. Suited for applications requiring fast scale-up and scale-out of the cluster. |
-| Hardened access  | Best for large enterprises that need full control of security and stability. |
+| Preset                      | Description                                                            |
+|-----------------------------|------------------------------------------------------------------------|
+| Production Standard         | Best for most applications serving production traffic with AKS recommended best practices. |
+| Dev/Test                    | Best for developing new workloads or testing existing workloads. |
+| Production Economy          | Best for serving production traffic in a cost conscious way if your workloads can tolerate interruptions. |
+| Production Enterprise       | Best for serving production traffic with rigorous permissions and hardened security. |
+
+|                              | Production Standard |Dev/Test|Production Economy|Production Enterprise|
+|------------------------------|---------|--------|--------|--------|
+|**System node pool node size**|Standard_D8ds_v5 |Standard_DS2_v2|Standard_D8ds_v5|Standard_D16ds_v5|
+|**System node pool autoscaling range**|2-5 nodes|2-100 nodes|2-5 nodes|2-5 nodes|
+|**User node pool node size**|Standard_D8ds_v5|-|Standard_D8as_v4|Standard_D8ds_v5|
+|**User node pool autoscaling range**|2-100 nodes|-|-|2-100 nodes|
+|**Private cluster**|-|-|-|:::image type="icon" source="./media/quotas-skus-regions/yes-icon.svg":::|
+|**Availability zones**|:::image type="icon" source="./media/quotas-skus-regions/yes-icon.svg":::|-|-|:::image type="icon" source="./media/quotas-skus-regions/yes-icon.svg":::|
+|**Azure Policy**|:::image type="icon" source="./media/quotas-skus-regions/yes-icon.svg":::|-|-|:::image type="icon" source="./media/quotas-skus-regions/yes-icon.svg":::|
+|**Azure Monitor**|:::image type="icon" source="./media/quotas-skus-regions/yes-icon.svg":::|-|-|:::image type="icon" source="./media/quotas-skus-regions/yes-icon.svg":::|
+|**Secrets store CSI driver**|:::image type="icon" source="./media/quotas-skus-regions/yes-icon.svg":::|-|-|:::image type="icon" source="./media/quotas-skus-regions/yes-icon.svg":::|
+|**Network configuration**|Azure CNI|Kubenet|Azure CNI|Azure CNI|
+|**Network configuration**|Calico|Calico|Calico|Calico|
+|**Authentication and Authorization**|Local accounts with Kubernetes RBAC|Local accounts with Kubernetes RBAC|Azure AD Authentication with Azure RBAC|Azure AD authentication with Azure RBAC|
+
 
 ## Next steps
 

articles/aks/quotas-skus-regions.md

@@ -27,10 +27,6 @@ Currently, API Management supports resolvers that can access the following data
 * Resolver-scoped policies are evaluated *after* any `inbound` and `backend` policies in the policy execution pipeline. They don't inherit policies from other scopes. For more information, see [Policies in API Management](api-management-howto-policies.md).
 * You can configure API-scoped policies for a GraphQL API, independent of the resolver-scoped policies. For example, add a [validate-graphql-request](validate-graphql-request-policy.md) policy to the `inbound` scope to validate the request before the resolver is invoked. Configure API-scoped policies on the **API policies** tab for the API.
 
-> [!IMPORTANT]
-> * If you use the preview `set-graphql-resolver` policy in policy definitions, you should migrate to the managed resolvers described in this article.
-> * After you configure a managed resolver for a GraphQL field, the gateway will skip the `set-graphql-resolver` policy in any policy definitions. You can't combine use of managed resolvers and the `set-graphql-resolver` policy in your API Management instance.
-
 ## Prerequisites
 
 - An existing API Management instance. [Create one if you haven't already](get-started-create-service-instance.md).

articles/api-management/configure-graphql-resolver.md

@@ -7,17 +7,16 @@ ms.custom:
 ms.topic: include
 ms.date: 11/1/2023
 ---
-
-At this time, a test or preview build is not available for the next release.
-
 <!--
+At this time, a test or preview build is not available for the next release.
+ -->
 
-Nov 2023 test release is now available.
+Dec 2023 preview release is now available.
 
 |Component|Value|
 |-----------|-----------|
-|Container images registry/repository |`mcr.microsoft.com/arcdata/test`|
-|Container images tag |`v1.25.0_2023-11-14`|
+|Container images registry/repository |`mcr.microsoft.com/arcdata/preview`|
+|Container images tag |`v1.26.0_2023-12-12`|
 |**CRD names and version:**| |
 |`activedirectoryconnectors.arcdata.microsoft.com`| v1beta1, v1beta2, v1, v2|
 |`datacontrollers.arcdata.microsoft.com`| v1beta1, v1 through v5|
@@ -34,29 +33,14 @@ Nov 2023 test release is now available.
 |`telemetrycollectors.arcdata.microsoft.com`| v1beta1 through v1beta5|
 |`telemetryrouters.arcdata.microsoft.com`| v1beta1 through v1beta5|
 |Azure Resource Manager (ARM) API version|2023-11-01-preview|
-|`arcdata` Azure CLI extension version|1.5.7 ([Download](https://aka.ms/az-cli-arcdata-ext))|
-|Arc-enabled Kubernetes helm chart extension version|1.25.0|
+|`arcdata` Azure CLI extension version|1.5.8 ([Download](https://aka.ms/az-cli-arcdata-ext))|
+|Arc-enabled Kubernetes helm chart extension version|1.26.0|
 |Azure Arc Extension for Azure Data Studio<br/>`arc`<br/>`azcli`|<br/>1.8.0 ([Download](https://aka.ms/ads-arcdata-ext))</br>1.8.0 ([Download](https://aka.ms/ads-azcli-ext))|
 |SQL Database version | 957 |
 
 ### Release notes
 
 #### Arc-enabled SQL Server
+Arc SQL Server | Show the Data Processing Service (DPS) connectivity status in the Azure portal | GA
 
-- Configure backups at instance level using custom schedule for SQL Server enabled by Azure Arc instances for both portal and CLI - public preview.
-  - Configure Automated Backups with a custom schedule and custom retention period, on an Arc enabled SQL Server.
-- Point-in-time-restore using Azure CLI and Azure portal - public preview.
-  - Restore a database to a point-in-time restore of their databases, if automatic backups are enabled. Restore can be done either from Azure portal or via az CLI.
-
-- Monitoring | Performance dashboards of an individual SQL Server enabled by Azure Arc in the Azure portal - public preview.
-
-- Track the provision state and (extension service) status of Azure extension for SQL Server - general availability.
-  - Beginning with this release, you can track the provisioning status of Azure Arc extension for SQL Server and Azure Arc guest agent in the properties tab for Arc enabled SQL Server. 
-
-- High Availability | Manage Always On availability group - manual failover - public preview.
-  - Perform a planned, manual failover on an availability group replica, using Azure portal.
-- Availability group status - Track the availability upload status | public preview.
-  - Beginning with this release, track the status and see the last time that the availability group inventory data is updated.  The portal shows two new properties, **Upload status** and **Last collected time**" in the **Availability Groups** tab of the Arc-enabled SQL Server. 
-- Support for separate proxy bypass value for Arc SQL Server only - general availability.
-
--->
+Arc SQL Server | Monitoring | Add IOPS, Queue Latency Storage IO charts in Performance Dashboard in Azure portal

articles/azure-arc/data/includes/azure-arc-data-preview-release.md

@@ -9,14 +9,13 @@ ms.author: franlanglois
 ms.custom: devx-track-azurepowershell
 
 ---
+
 # Manage Azure Cache for Redis with Azure PowerShell
 
 > [!div class="op_single_selector"]
 
 > * [PowerShell](cache-how-to-manage-redis-cache-powershell.md)
 > * [Azure CLI](cache-manage-cli.md)
->
->
 
 [!INCLUDE [updated-for-az](../../includes/updated-for-az.md)]
 
@@ -146,7 +145,7 @@ The following table contains Azure PowerShell properties and descriptions for co
 | Name |Name of the cache | |
 | Location |Location of the cache | |
 | ResourceGroupName |Resource group name in which to create the cache | |
-| Size |The size of the cache. Valid values are: P1, P2, P3, P4, C0, C1, C2, C3, C4, C5, C6, 250MB, 1GB, 2.5GB, 6GB, 13GB, 26GB, 53GB |1GB |
+| Size |The size of the cache. Valid values are: P1, P2, P3, P4, P5, C0, C1, C2, C3, C4, C5, C6, 250MB, 1GB, 2.5GB, 6GB, 13GB, 26GB, 53GB |1GB |
 | ShardCount |The number of shards to create when creating a premium cache with clustering enabled. Valid values are: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 | |
 | SKU |Specifies the SKU of the cache. Valid values are: Basic, Standard, Premium |Standard |
 | RedisConfiguration |Specifies Redis configuration settings. For details on each setting, see the following [RedisConfiguration properties](#redisconfiguration-properties) table. | |

articles/azure-cache-for-redis/cache-how-to-manage-redis-cache-powershell.md

@@ -998,7 +998,15 @@
           - name: AZFD0005
             href: errors-diagnostics/diagnostic-events/azfd0005.md
           - name: AZFD0006
-            href: errors-diagnostics/diagnostic-events/azfd0006.md            
+            href: errors-diagnostics/diagnostic-events/azfd0006.md        
+          - name: AZFD0007
+            href: errors-diagnostics/diagnostic-events/azfd0007.md 
+          - name: AZFD0008
+            href: errors-diagnostics/diagnostic-events/azfd0008.md  
+          - name: AZFD0009
+            href: errors-diagnostics/diagnostic-events/azfd0009.md     
+          - name: AZFD0010
+            href: errors-diagnostics/diagnostic-events/azfd0010.md            
     - name: host.json 2.x reference
       href: functions-host-json.md
     - name: host.json 1.x reference

articles/azure-functions/TOC.yml

@@ -1,10 +1,8 @@
 ---
 title: "AZFD0001: AzureWebJobsStorage app setting is not present."
 titleSuffix: "Azure Functions"
-description: "AZFD0001: AzureWebJobsStorage app setting is not present"
-author: soninaren
-ms.author: nasoni
-ms.topic: troubleshooting
+description: "Learn how to troubleshoot the event 'AZFD0001: AzureWebJobsStorage app setting is not present' in Azure Functions"
+ms.topic: reference
 ms.date: 09/03/2022
 ---
 
@@ -15,7 +13,6 @@ This event occurs when the function app doesn't have the `AzureWebJobsStorage` a
 | | Value |
 |-|-|
 | **Event ID** |AZFD0001|
-| **Category** |[Usage]|
 | **Severity** |Error|
 
 ## Event description

articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0001.md

@@ -1,7 +1,7 @@
 ---
 title: "AZFD0002: Value of AzureWebJobsStorage app setting is invalid."
 titleSuffix: "Azure Functions"
-description: "AZFD0002: Value of AzureWebJobsStorage app setting is invalid."
+description: "Learn how to troubleshoot the event 'AZFD0002: Value of AzureWebJobsStorage app setting is invalid' in Azure Functions"
 author: soninaren
 ms.author: nasoni
 ms.topic: reference
@@ -15,7 +15,6 @@ This event occurs when the value of the `AzureWebJobsStorage` app setting is set
 | | Value |
 |-|-|
 | **Event ID** |AZFD0002|
-| **Category** |[Usage]|
 | **Severity** |Error|
 
 ## Event description

articles/azure-functions/errors-diagnostics/diagnostic-events/azfd0002.md

@@ -1,10 +1,8 @@
 ---
 title: "AZFD0003: Encountered a StorageException while trying to fetch the diagnostic events."
 titleSuffix: "Azure Functions"
-description: "AZFD0003: Encountered a StorageException while trying to fetch the diagnostic events."
-author: soninaren
-ms.author: nasoni
-ms.topic: troubleshooting
+description: "Learn how to troubleshoot the event 'AZFD0003: Encountered a StorageException while trying to fetch the diagnostic events' in Azure Functions."
+ms.topic: reference
 ms.date: 09/03/2022
 ---
 
@@ -15,7 +13,6 @@ This event occurs when the Azure Storage account connection string value in the
 | | Value |
 |-|-|
 | **Event ID** |AZFD0003|
-| **Category** |[Usage]|
 | **Severity** |Error|
 
 ## Event description