Skip to content

Commit 7ece9fc

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into ratelimitingprovider
2 parents 117d695 + d836c01 commit 7ece9fc

22 files changed

+286
-168
lines changed

articles/aks/open-ai-quickstart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -229,7 +229,7 @@ Now that the application is deployed, you can deploy the Python-based microservi
229229
memory: 50Mi
230230
limits:
231231
cpu: 30m
232-
memory: 65Mi
232+
memory: 85Mi
233233
---
234234
apiVersion: v1
235235
kind: Service

articles/aks/open-ai-secure-access-quickstart.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -227,7 +227,7 @@ To use Microsoft Entra Workload ID on AKS, you need to make a few changes to the
227227
memory: 50Mi
228228
limits:
229229
cpu: 30m
230-
memory: 65Mi
230+
memory: 85Mi
231231
EOF
232232
```
233233

articles/api-management/api-management-api-import-restrictions.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -254,6 +254,9 @@ Namespaces other than the target aren't preserved on export. While you can impor
254254
### Multiple endpoints
255255
WSDL files can define multiple services and endpoints (ports) by one or more `wsdl:service` and `wsdl:port` elements. However, the API Management gateway is able to import and proxy requests to only a single service and endpoint. If multiple services or endpoints are defined in the WSDL file, identify the target service name and endpoint when importing the API by using the [wsdlSelector](/rest/api/apimanagement/apis/create-or-update#wsdlselector) property.
256256

257+
> [!TIP]
258+
> If you want to load-balance requests across multiple services and endpoints, consider configuring a [load-balanced backend pool](backends.md#load-balanced-pool-preview).
259+
257260
### Arrays
258261
SOAP-to-REST transformation supports only wrapped arrays shown in the example below:
259262

articles/api-management/backends.md

Lines changed: 125 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
---
22
title: Azure API Management backends | Microsoft Docs
3-
description: Learn about custom backends in API Management
3+
description: Learn about custom backends in Azure API Management
44
services: api-management
55
documentationcenter: ''
66
author: dlepow
77
editor: ''
88

99
ms.service: api-management
1010
ms.topic: article
11-
ms.date: 08/16/2023
11+
ms.date: 01/09/2024
1212
ms.author: danlep
1313
ms.custom:
1414
---
@@ -26,9 +26,13 @@ API Management also supports using other Azure resources as an API backend, such
2626
* A [Service Fabric cluster](how-to-configure-service-fabric-backend.md).
2727
* A custom service.
2828

29-
API Management supports custom backends so you can manage the backend services of your API. Use custom backends, for example, to authorize the credentials of requests to the backend service. Configure and manage custom backends in the Azure portal, or using Azure APIs or tools.
29+
API Management supports custom backends so you can manage the backend services of your API. Use custom backends for one or more of the following:
3030

31-
After creating a backend, you can reference the backend in your APIs. Use the [`set-backend-service`](set-backend-service-policy.md) policy to direct an incoming API request to the custom backend. If you already configured a backend web service for an API, you can use the `set-backend-service` policy to redirect the request to a custom backend instead of the default backend web service configured for that API.
31+
* Authorize the credentials of requests to the backend service
32+
* Protect your backend from too many requests
33+
* Route or load-balance requests to multiple backends
34+
35+
Configure and manage custom backends in the Azure portal, or using Azure APIs or tools.
3236

3337
## Benefits of backends
3438

@@ -38,6 +42,43 @@ A custom backend has several benefits, including:
3842
* Easily used by configuring a transformation policy on an existing API.
3943
* Takes advantage of API Management functionality to maintain secrets in Azure Key Vault if [named values](api-management-howto-properties.md) are configured for header or query parameter authentication.
4044

45+
## Reference backend using set-backend-service policy
46+
47+
After creating a backend, you can reference the backend in your APIs. Use the [`set-backend-service`](set-backend-service-policy.md) policy to direct an incoming API request to the custom backend. If you already configured a backend web service for an API, you can use the `set-backend-service` policy to redirect the request to a custom backend instead of the default backend web service configured for that API. For example:
48+
49+
```xml
50+
<policies>
51+
<inbound>
52+
<base />
53+
<set-backend-service backend-id="myBackend" />
54+
</inbound>
55+
[...]
56+
<policies/>
57+
```
58+
59+
You can use conditional logic with the `set-backend-service` policy to change the effective backend based on location, gateway that was called, or other expressions.
60+
61+
For example, here is a policy to route traffic to another backend based on the gateway that was called:
62+
63+
```xml
64+
<policies>
65+
<inbound>
66+
<base />
67+
<choose>
68+
<when condition="@(context.Deployment.Gateway.Id == "factory-gateway")">
69+
<set-backend-service backend-id="backend-on-prem" />
70+
</when>
71+
<when condition="@(context.Deployment.Gateway.IsManaged == false)">
72+
<set-backend-service backend-id="self-hosted-backend" />
73+
</when>
74+
<otherwise />
75+
</choose>
76+
</inbound>
77+
[...]
78+
<policies/>
79+
```
80+
81+
4182
## Circuit breaker (preview)
4283

4384
Starting in API version 2023-03-01 preview, API Management exposes a [circuit breaker](/rest/api/apimanagement/current-preview/backend/create-or-update?tabs=HTTP#backendcircuitbreaker) property in the backend resource to protect a backend service from being overwhelmed by too many requests.
@@ -50,16 +91,15 @@ The backend circuit breaker is an implementation of the [circuit breaker pattern
5091

5192
### Example
5293

53-
Use the API Management REST API or a Bicep or ARM template to configure a circuit breaker in a backend. In the following example, the circuit breaker trips when there are three or more `5xx` status codes indicating server errors in a day. The circuit breaker resets after one hour.
94+
Use the API Management [REST API](/rest/api/apimanagement/backend) or a Bicep or ARM template to configure a circuit breaker in a backend. In the following example, the circuit breaker in *myBackend* in the API Management instance *myAPIM* trips when there are three or more `5xx` status codes indicating server errors in a day. The circuit breaker resets after one hour.
5495

5596
#### [Bicep](#tab/bicep)
5697

57-
Include a snippet similar to the following in your Bicep template:
98+
Include a snippet similar to the following in your Bicep template for a backend resource with a circuit breaker:
5899

59100
```bicep
60101
resource symbolicname 'Microsoft.ApiManagement/service/backends@2023-03-01-preview' = {
61-
name: 'myBackend'
62-
parent: resourceSymbolicName
102+
name: 'myAPIM/myBackend'
63103
properties: {
64104
url: 'https://mybackend.com'
65105
protocol: 'http'
@@ -72,7 +112,6 @@ resource symbolicname 'Microsoft.ApiManagement/service/backends@2023-03-01-previ
72112
'Server errors'
73113
]
74114
interval: 'P1D'
75-
percentage: int
76115
statusCodeRanges: [
77116
{
78117
min: 500
@@ -85,20 +124,19 @@ resource symbolicname 'Microsoft.ApiManagement/service/backends@2023-03-01-previ
85124
}
86125
]
87126
}
88-
}
89-
[...]
90-
}
127+
}
128+
}
91129
```
92130

93131
#### [ARM](#tab/arm)
94132

95-
Include a JSON snippet similar to the following in your ARM template:
133+
Include a JSON snippet similar to the following in your ARM template for a backend resource with a circuit breaker:
96134

97135
```JSON
98136
{
99137
"type": "Microsoft.ApiManagement/service/backends",
100138
"apiVersion": "2023-03-01-preview",
101-
"name": "myBackend",
139+
"name": "myAPIM/myBackend",
102140
"properties": {
103141
"url": "https://mybackend.com",
104142
"protocol": "http",
@@ -122,18 +160,88 @@ Include a JSON snippet similar to the following in your ARM template:
122160
]
123161
}
124162
}
125-
[...]
126163
}
127164
```
128165

129166
---
130167

168+
## Load-balanced pool (preview)
169+
170+
Starting in API version 2023-05-01 preview, API Management supports backend *pools*, when you want to implement multiple backends for an API and load-balance requests across those backends. Currently, the backend pool supports round-robin load balancing.
171+
172+
Use a backend pool for scenarios such as the following:
173+
174+
* Spread the load to multiple backends, which may have individual backend circuit breakers.
175+
* Shift the load from one set of backends to another for upgrade (blue-green deployment).
131176

177+
To create a backend pool, set the `type` property of the backend to `pool` and specify a list of backends that make up the pool.
178+
179+
> [!NOTE]
180+
> Currently, you can only include single backends in a backend pool. You can't add a backend of type `pool` to another backend pool.
181+
182+
### Example
183+
184+
Use the API Management [REST API](/rest/api/apimanagement/backend) or a Bicep or ARM template to configure a backend pool. In the following example, the backend *myBackendPool* in the API Management instance *myAPIM* is configured with a backend pool. Example backends in the pool are named *backend-1* and *backend-2*.
185+
186+
#### [Bicep](#tab/bicep)
187+
188+
Include a snippet similar to the following in your Bicep template for a backend resource with a load-balanced pool:
189+
190+
```bicep
191+
resource symbolicname 'Microsoft.ApiManagement/service/backends@2023-05-01-preview' = {
192+
name: 'myAPIM/myBackendPool'
193+
properties: {
194+
description: 'Load balancer for multiple backends'
195+
type: 'Pool'
196+
protocol: 'http'
197+
url: 'http://unused'
198+
pool: {
199+
services: [
200+
{
201+
id: '/backends/backend-1'
202+
}
203+
{
204+
id: '/backends/backend-2'
205+
}
206+
]
207+
}
208+
}
209+
}
210+
```
211+
#### [ARM](#tab/arm)
212+
213+
Include a JSON snippet similar to the following in your ARM template for a backend resource with a load-balanced pool:
214+
215+
```json
216+
{
217+
"type": "Microsoft.ApiManagement/service/backends",
218+
"apiVersion": "2023-05-01-preview",
219+
"name": "myAPIM/myBackendPool",
220+
"properties": {
221+
"description": "Load balancer for multiple backends",
222+
"type": "Pool",
223+
"protocol": "http",
224+
"url": "http://unused",
225+
"pool": {
226+
"services": [
227+
{
228+
"id": "/backends/backend-1"
229+
},
230+
{
231+
"id": "/backends/backend-2"
232+
}
233+
]
234+
}
235+
}
236+
}
237+
```
238+
239+
---
132240
## Limitation
133241

134242
For **Developer** and **Premium** tiers, an API Management instance deployed in an [internal virtual network](api-management-using-with-internal-vnet.md) can throw HTTP 500 `BackendConnectionFailure` errors when the gateway endpoint URL and backend URL are the same. If you encounter this limitation, follow the instructions in the [Self-Chained API Management request limitation in internal virtual network mode](https://techcommunity.microsoft.com/t5/azure-paas-blog/self-chained-apim-request-limitation-in-internal-virtual-network/ba-p/1940417) article in the Tech Community blog.
135243

136-
## Next steps
244+
## Related content
137245

138246
* Set up a [Service Fabric backend](how-to-configure-service-fabric-backend.md) using the Azure portal.
139-
* Backends can also be configured using the API Management [REST API](/rest/api/apimanagement), [Azure PowerShell](/powershell/module/az.apimanagement/new-azapimanagementbackend), or [Azure Resource Manager templates](../service-fabric/service-fabric-tutorial-deploy-api-management.md).
247+

articles/azure-monitor/visualize/workbooks-jsonpath.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ In this example, the JSON object represents a store's inventory. We're going to
7373

7474
:::image type="content" source="media/workbooks-jsonpath/query-jsonpath.png" alt-text="Screenshot that shows editing a query item with JSON data source and JSON path result format.":::
7575

76-
## Use regular expressions to covert values
76+
## Use regular expressions to convert values
7777

7878
You may have some data that isn't in a standard format. To use that data effectively, you would want to convert that data into a standard format.
7979

articles/communication-services/concepts/voice-video-calling/includes/user-facing-diagnostics-android.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ The following user-facing diagnostics are available:
3232
| Name | Description | Possible values | Use cases | Mitigation steps |
3333
| -------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
3434
| noSpeakerDevicesAvailable | there's no audio output device (speaker) on the user's system. | - Set to `True` when there are no speaker devices on the system, and speaker selection is supported. <br/> - Set to `False` when there's a least one speaker device on the system, and speaker selection is supported. | All speakers are unplugged | When value set to `True`, consider giving visual notification to end user that their current call session doesn't have any speakers available. |
35-
| speakingWhileMicrophoneIsMuted | Speaking while being on mute. | - Set to `True` when local microphone is muted and the local user is speaking. <br/> - Set to `False` when local user either stops speaking, or unmutes the microphone. <br/> \* Note: Currently, this option isn't supported on Safari because the audio level samples are taken from WebRTC stats. | During a call, mute your microphone and speak into it. | When value set to `True` consider giving visual notification to end user that they might be talking and not realizing that their audio is muted. |
35+
| speakingWhileMicrophoneIsMuted | Speaking while being on mute. | - Set to `True` when local microphone is muted and the local user is speaking. <br/> - Set to `False` when local user either stops speaking, or unmutes the microphone. <br/> - This diagnostic event can be automatically disabled if it is triggered for a certain amount of times without any user action to avoid noise and provide a better user experience. It will be re-enabled again when a new mute action occurs. | During a call, mute your microphone and speak into it. | When value set to `True` consider giving visual notification to end user that they might be talking and not realizing that their audio is muted. |
3636
| noMicrophoneDevicesAvailable | No audio capture devices (microphone) on the user's system | - Set to `True` when there are no microphone devices on the system. <br/> - Set to `False` when there's at least one microphone device on the system. | All microphones are unplugged during the call. | When value set to `True` consider giving visual notification to end user that their current call session doesn't have a microphone. For more information, see [enable microphone from device manger](../../best-practices.md#plug-in-microphone-or-enable-microphone-from-device-manager-when-azure-communication-services-call-in-progress) section. |
3737
| microphoneNotFunctioning | Microphone isn't functioning. | - Set to `True` when we fail to start sending local audio stream because the microphone device may have been disabled in the system or it's being used by another process. This UFD takes about 10 seconds to get raised. <br/> - Set to `False` when microphone starts to successfully send audio stream again. | No microphones available, microphone access disabled in a system | When value set to `True` give visual notification to end user that there's a problem with their microphone. |
3838
| microphoneMuteUnexpectedly | Microphone is muted | - Set to `True` when microphone enters muted state unexpectedly. <br/> - Set to `False` when microphone starts to successfully send audio stream | Microphone is muted from the system. Most cases happen when user is on an Azure Communication Services call on a mobile device and a phone call comes in. In most cases, the operating system mutes the Azure Communication Services call so a user can answer the phone call. | When value is set to `True`, give visual notification to end user that their call was muted because a phone call came in. For more information, see how to best handle [OS muting an Azure Communication Services call](../../best-practices.md#handle-os-muting-call-when-phone-call-comes-in) section for more details. |

0 commit comments

Comments
 (0)