Skip to content

Commit 1ee4818

Browse files
committed
Line edits5
1 parent ba3a2a5 commit 1ee4818

3 files changed

Lines changed: 11 additions & 11 deletions

File tree

articles/api-management/how-to-configure-local-metrics-logs.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -315,7 +315,7 @@ May 15 05:54:21 aks-agentpool-43853532-vmss000000 apimuser[8]: Timestamp=2023-05
315315
```
316316

317317
> [!NOTE]
318-
> If you change the root with `chroot`, for example `chroot /host`, then the above path needs to reflect that change.
318+
> If you change the root with `chroot`, for example `chroot /host`, then the preceding path needs to reflect that change.
319319

320320
## Related content
321321

articles/api-management/how-to-configure-service-fabric-backend.yml

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
### YamlMime:HowTo
22

33
metadata:
4-
title: Set up Service Fabric backend in Azure API Management
4+
title: Set up Service Fabric Backend in Azure API Management
55
description: How to create a Service Fabric service backend in Azure API Management using the Azure portal
66
author: dlepow
77
ms.custom:
@@ -10,7 +10,7 @@ metadata:
1010

1111
ms.service: azure-api-management
1212
ms.topic: how-to
13-
ms.date: 01/29/2021
13+
ms.date: 10/09/2025
1414
ms.author: danlep
1515
title: |
1616
Set up a Service Fabric backend in API Management using the Azure portal
@@ -23,19 +23,19 @@ prerequisites:
2323
summary: |
2424
Prerequisites to configure a sample service in a Service Fabric cluster running Windows as a custom backend:
2525
26-
* **Windows development environment** - Install [Visual Studio 2019](https://www.visualstudio.com) and the **Azure development**, **ASP.NET and web development**, and **.NET Core cross-platform development** workloads. Then set up a [.NET development environment](/azure/service-fabric/service-fabric-get-started).
26+
* **Windows development environment**: Install [Visual Studio](https://www.visualstudio.com) and the **Azure development**, **ASP.NET and web development**, and **.NET Core cross-platform development** workloads. Then set up a [.NET development environment](/azure/service-fabric/service-fabric-get-started).
2727
28-
* **Service Fabric cluster** - See [Tutorial: Deploy a Service Fabric cluster running Windows into an Azure virtual network](/azure/service-fabric/service-fabric-tutorial-create-vnet-and-windows-cluster). You can create a cluster with an existing X.509 certificate or for test purposes create a new, self-signed certificate. The cluster is created in a virtual network.
28+
* **Service Fabric cluster**: See [Tutorial: Deploy a Service Fabric cluster running Windows into an Azure virtual network](/azure/service-fabric/service-fabric-tutorial-create-vnet-and-windows-cluster). You can create a cluster with an existing X.509 certificate, or for test purposes create a new, self-signed certificate. The cluster is created in a virtual network.
2929
30-
* **Sample Service Fabric app** - Create a Web API app and deploy to the Service Fabric cluster as described in [Integrate API Management with Service Fabric in Azure](/azure/service-fabric/service-fabric-tutorial-deploy-api-management).
30+
* **Sample Service Fabric app**: Create a Web API app and deploy to the Service Fabric cluster as described in [Integrate API Management with Service Fabric in Azure](/azure/service-fabric/service-fabric-tutorial-deploy-api-management).
3131
3232
These steps create a basic stateless ASP.NET Core Reliable Service using the default Web API project template. Later, you expose the HTTP endpoint for this service through Azure API Management.
3333
3434
Take note of the application name, for example `fabric:/myApplication/myService`.
3535
36-
* **API Management instance** - An existing or new API Management instance in the **Premium** or **Developer** tier and in the same region as the Service Fabric cluster. If you need one, [create an API Management instance](get-started-create-service-instance.md).
36+
* **API Management instance**: An existing or new API Management instance in the **Premium** or **Developer** tier and in the same region as the Service Fabric cluster. If you need one, [create an API Management instance](get-started-create-service-instance.md).
3737
38-
* **Virtual network** - Add your API Management instance to the virtual network you created for your Service Fabric cluster. API Management requires a dedicated subnet in the virtual network.
38+
* **Virtual network**: Add your API Management instance to the virtual network you created for your Service Fabric cluster. API Management requires a dedicated subnet in the virtual network.
3939
4040
For steps to enable virtual network connectivity for the API Management instance, see [How to use Azure API Management with virtual networks](api-management-using-with-vnet.md).
4141
procedureSection:
@@ -56,9 +56,9 @@ procedureSection:
5656
- |
5757
In the [Azure portal](https://portal.azure.com), navigate to your API Management instance.
5858
- |
59-
Under **APIs**, select **Backends** > **+ Add**.
59+
Under **APIs**, select **Backends** > **+ Create new backend**.
6060
- |
61-
Enter a backend name and an optional description
61+
Enter a backend name and an optional description.
6262
- |
6363
In **Type**, select **Service Fabric**.
6464
- |
@@ -138,7 +138,7 @@ procedureSection:
138138
:::image type="content" source="media/backends/set-backend-service.png" alt-text="Configure set-backend-service policy":::
139139
140140
> [!NOTE]
141-
> If one or more nodes in the Service Fabric cluster goes down or is removed, API Management does not get an automatic notification and continues to send traffic to these nodes. To handle these cases, configure a resolve condition similar to: `sf-resolve-condition="@((int)context.Response.StatusCode != 200 || context.LastError?.Reason == "BackendConnectionFailure" || context.LastError?.Reason == "Timeout")"`
141+
> If one or more nodes in the Service Fabric cluster goes down or is removed, API Management doesn't get an automatic notification and continues to send traffic to these nodes. To handle these cases, configure a resolve condition similar to: `sf-resolve-condition="@((int)context.Response.StatusCode != 200 || context.LastError?.Reason == "BackendConnectionFailure" || context.LastError?.Reason == "Timeout")"`
142142
143143
### Test backend API
144144
steps:
41.3 KB
Loading

0 commit comments

Comments
 (0)