Merge pull request #295112 from MicrosoftDocs/main

2/21/2025 AM Publish

Author: Albertyang0

.openpublishing.redirection.json

@@ -30,6 +30,11 @@
       "redirect_url": "/previous-versions/azure/partner-solutions/logzio/troubleshoot",
       "redirect_document_id": false
     },
+    {
+      "source_path": "articles/event-grid/event-schema-storage-actions.md",
+      "redirect_url": "/azure/storage-actions/overview",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/hdinsight-aks/index.yml",
       "redirect_url": "/previous-versions/azure/hdinsight-aks",
@@ -5935,6 +5940,11 @@
       "redirect_url": "/azure/reliability/overview-reliability-guidance",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/reliability/sovereign-cloud-china.md",
+      "redirect_url": "/azure/china/concepts-service-availability",
+      "redirect_document_id": false
+    },
     {
       "source_path_from_root": "/articles/managed-grafana/concept-role-based-access-control.md",
       "redirect_url": "/azure/managed-grafana/how-to-manage-access-permissions-users-identities",

articles/active-directory-b2c/localization-string-ids.md

@@ -496,18 +496,18 @@ The following IDs are used for a [time-based one-time password (TOTP) display co
       </LocalizedResources>
 ```
 
-## Restful service error messages
+## RESTful service error messages
 
-The following IDs are used for [Restful service technical profile](restful-technical-profile.md) error messages:
+The following IDs are used for [RESTful service technical profile](restful-technical-profile.md) error messages:
 
 | ID | Default value |
 | --- | ------------- |
-| `DefaultUserMessageIfRequestFailed` | Failed to establish connection to restful service end point. Restful service URL: {0} |
-| `UserMessageIfCircuitOpen` | {0} Restful Service URL: {1} |
-| `UserMessageIfDnsResolutionFailed` | Failed to resolve the hostname of the restful service endpoint. Restful service URL: {0} |
-| `UserMessageIfRequestTimeout` | Failed to establish connection to restful service end point within timeout limit {0} seconds. Restful service URL: {1} |
+| `DefaultUserMessageIfRequestFailed` | Failed to establish connection to restful service end point. RESTful service URL: {0} |
+| `UserMessageIfCircuitOpen` | {0} RESTful Service URL: {1} |
+| `UserMessageIfDnsResolutionFailed` | Failed to resolve the hostname of the restful service endpoint. RESTful service URL: {0} |
+| `UserMessageIfRequestTimeout` | Failed to establish connection to restful service end point within timeout limit {0} seconds. RESTful service URL: {1} |
 
-### Restful service example
+### RESTful service example
 
 ```xml
 <LocalizedResources Id="api.localaccountsignup.en">

articles/api-management/graphql-apis-overview.md

@@ -21,7 +21,7 @@ API Management helps you import, manage, protect, test, publish, and monitor Gra
 
 |Pass-through GraphQL   |Synthetic GraphQL  |
 |---------|---------|
-| ▪️ Pass-through API to existing GraphQL service endpoint<br><br/>▪️ Support for GraphQL queries, mutations, and subscriptions  |   ▪️ API based on a custom GraphQL schema<br></br>▪️ Support for GraphQL queries, mutations, and subscriptions<br/><br/>▪️  Configure custom resolvers, for example, to HTTP data sources<br/><br/>▪️ Develop GraphQL schemas and GraphQL-based clients while consuming data from legacy APIs     |
+| ▪️ Pass-through API to existing GraphQL service endpoint<br><br/>▪️ Support for GraphQL queries, mutations, and subscriptions  |   ▪️ API based on a custom GraphQL schema<br></br>▪️ Support for GraphQL queries, mutations, and subscriptions<br/><br/>▪️  Configure custom resolvers, for example, to HTTP data sources<br/><br/>▪️ Develop GraphQL schemas and GraphQL-based clients while consuming data from legacy APIs<br/><br/>▪️ Synthetic subscriptions do not require resolvers. See [publish-event](publish-event-policy.md) policy.    |
 
 ## Availability
 

articles/api-management/publish-event-policy.md

@@ -53,6 +53,7 @@ The `publish-event` policy publishes an event to one or more subscriptions speci
 ### Usage notes
 
 * This policy is invoked only when a related GraphQL query or mutation is executed.
+* Resolver *should not* be defined for the corresponding subscription. Defining a `publish-event` policy on a source query or mutation is sufficient to trigger subscription events.
 
 ## Example
 

articles/azure-resource-manager/bicep/bicep-core-diagnostics.md

@@ -138,8 +138,8 @@ If you need more information about a particular diagnostic code, select the **Fe
 | <a id='BCP130' />BCP130 | Error | Decorators aren't allowed here. |
 | <a id='BCP132' />[BCP132](./diagnostics/bcp132.md) | Error | Expected a declaration after the decorator. |
 | <a id='BCP133' />BCP133 | Error | The unicode escape sequence isn't valid. Valid unicode escape sequences range from \\u{0} to \\u{10FFFF}. |
-| <a id='BCP134' />BCP134 | Warning | Scope {ToQuotedString(LanguageConstants.GetResourceScopeDescriptions(suppliedScope))} isn't valid for this module. Permitted scopes: {ToQuotedString(LanguageConstants.GetResourceScopeDescriptions(supportedScopes))}. |
-| <a id='BCP135' />BCP135 | Warning | Scope {ToQuotedString(LanguageConstants.GetResourceScopeDescriptions(suppliedScope))} isn't valid for this resource type. Permitted scopes: {ToQuotedString(LanguageConstants.GetResourceScopeDescriptions(supportedScopes))}. |
+| <a id='BCP134' />BCP134 | Error | Scope \<scope-name> isn't valid for this module. Permitted scopes: \<scope-name>. |
+| <a id='BCP135' />[BCP135](./diagnostics/bcp135.md) | Error | Scope \<scope-name> isn't valid for this resource type. Permitted scopes: \<scope-name>. |
 | <a id='BCP136' />BCP136 | Error | Expected a loop item variable identifier at this location. |
 | <a id='BCP137' />BCP137 | Error | Loop expected an expression of type "{LanguageConstants.Array}" but the provided value is of type "{actualType}". |
 | <a id='BCP138' />BCP138 | Error | For-expressions aren't supported in this context. For-expressions may be used as values of resource, module, variable, and output declarations, or values of resource and module properties. |
@@ -237,7 +237,7 @@ If you need more information about a particular diagnostic code, select the **Fe
 | <a id='BCP235' />BCP235 | Error | Specified JSONPath doesn't exist in the given file or is invalid. |
 | <a id='BCP236' />BCP236 | Error | Expected a new line or comma character at this location. |
 | <a id='BCP237' />BCP237 | Error | Expected a comma character at this location. |
-| <a id='BCP238' />BCP238 | Error | Unexpected new line character after a comma. |
+| <a id='BCP238' />[BCP238](./diagnostics/bcp238.md) | Error | Unexpected new line character after a comma. |
 | <a id='BCP239' />BCP239 | Error | Identifier "{name}" is a reserved Bicep symbol name and can't be used in this context. |
 | <a id='BCP240' />BCP240 | Error | The "parent" property only permits direct references to resources. Expressions aren't supported. |
 | <a id='BCP241' />BCP241 | Warning | The \<function-name> function is deprecated and will be removed in a future release of Bicep. Add a comment to https://github.com/Azure/bicep/issues/2017 if you believe this will impact your workflow. |

articles/azure-resource-manager/bicep/diagnostics/bcp135.md

@@ -0,0 +1,60 @@
+---
+title: BCP135
+description: Scope <scope-name> isn't valid for this resource type. Permitted scopes <scope-name>.
+ms.topic: reference
+ms.custom: devx-track-bicep
+ms.date: 02/20/2025
+---
+
+# Bicep diagnostic code - BCP135
+
+In Bicep, scopes determine the hierarchical level at which resources are deployed within Azure. ARM provides four deployment scopes—resource group, management group, subscription, and tenant. Resources must be deployed within the allowed scopes. For more information, see [Deployment scope](../deploy-to-resource-group.md#deployment-scopes).
+
+## Description
+
+Scope \<scope-name> isn't valid for this resource type. Permitted scopes: \<scope-name>.
+
+## Level
+
+Error
+
+## Solutions
+
+Deploy resources to the permitted scopes.
+
+## Examples
+
+The following example raises the diagnostic because `storageAccounts` can't be deployed at the management group scope.
+
+```bicep
+targetScope = 'managementGroup'
+
+resource storageAccount 'Microsoft.Storage/storageAccounts@2023-05-01' = {
+  name: 'demostorage0220'
+  location: 'eastus'
+  sku: {
+    name:  'Standard_LRS'
+  }
+  kind:  'StorageV2'
+}
+```
+
+You can fix the diagnostic by setting the `targetScope` to `resourceGroup`.  
+
+```bicep
+targetScope = 'resourceGroup'
+
+resource storageAccount 'Microsoft.Storage/storageAccounts@2023-05-01' = {
+  name: 'demostorage0220'
+  location: 'eastus'
+  sku: {
+    name:  'Standard_LRS'
+  }
+  kind:  'StorageV2'
+}
+
+```
+
+## Next steps
+
+For more information about Bicep diagnostics, see [Bicep core diagnostics](../bicep-core-diagnostics.md).

articles/azure-resource-manager/bicep/diagnostics/bcp238.md

@@ -0,0 +1,47 @@
+---
+title: BCP238
+description: Unexpected new line character after a comma.
+ms.topic: reference
+ms.custom: devx-track-bicep
+ms.date: 02/12/2025
+---
+
+# Bicep diagnostic code - BCP238
+
+In Bicep, arrays or objects can be declared on a single line or across multiple lines. In single-line declarations, values are separated by commas (,), while in multi-line declarations, commas aren't used. You can combine single-line and multi-line styles, but each element must be separated by no more than one comma or one set of new lines. This diagnostic occurs when this rule isn't followed. For more information, see [Arrays](../data-types.md#arrays) or [Objects](../data-types.md#objects).
+
+## Description
+
+Unexpected new line character after a comma.
+
+## Level
+
+Error
+
+## Solution
+
+Remove Use a name of a value.
+
+## Examples
+
+The following example raises the diagnostic because a comma and a new line are used in between _'def'_ and _'ghi'_:
+
+```bicep
+var mixedArray = ['abc', 'def',
+    'ghi']
+```
+
+You can fix the diagnostic by removing either the comma or the new line:
+
+```bicep
+var mixedArray = ['abc', 'def'
+    'ghi']
+```
+
+```bicep
+var mixedArray = ['abc', 'def', 'ghi']
+```
+
+## Next steps
+
+For more information about Bicep diagnostics, see [Bicep core diagnostics](../bicep-core-diagnostics.md).

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

@@ -681,6 +681,8 @@
       href: diagnostics/bcp129.md
     - name: BCP132
       href: diagnostics/bcp132.md
+    - name: BCP135
+      href: diagnostics/bcp135.md
     - name: BCP139
       href: diagnostics/bcp139.md
     - name: BCP147
@@ -695,6 +697,8 @@
       href: diagnostics/bcp170.md
     - name: BCP192
       href: diagnostics/bcp192.md
+    - name: BCP238
+      href: diagnostics/bcp238.md
     - name: BCP266
       href: diagnostics/bcp266.md
     - name: BCP288

articles/cost-management-billing/understand/billing-meter-location.md

@@ -7,7 +7,7 @@ ms.reviewer: v-minasyanv
 ms.service: cost-management-billing
 ms.subservice: common
 ms.topic: concept-article
-ms.date: 02/18/2025
+ms.date: 02/21/2025
 ms.author: banders
 #customer intent: As a billing administrator, I want to understand the difference between a billing meter region and a resource location.
 ---
@@ -28,7 +28,7 @@ Consider a situation where you deploy an Azure service in the US West region. Th
 
 The Azure region where you deploy a resource determines its physical location. The billing meter's location doesn't affect the actual resource location. So, the meter region location can differ from the resource location, causing the variation.
 
-To avoid any confusion, keep the distinction between a billing meter region and an Azure region location in mind.
+To avoid any confusion, keep the distinction between a billing meter region and an Azure resource region in mind.
 
 ## Related content