You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/api-management/api-management-howto-api-inspector.md
+76-9Lines changed: 76 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -74,7 +74,7 @@ Follow these steps to trace an API request in the test console in the portal. Th
74
74
75
75
The following high level steps are required to enable tracing for a request to API Management when using `curl`, a REST client such as Visual Studio Code with the REST Client extension, or a client app. Currently these steps must be followed using the [API Management REST API](/rest/api/apimanagement):
76
76
77
-
1. Obtain a token credential for tracing.
77
+
1. Obtain a debug token for tracing.
78
78
1. Add the token value in an `Apim-Debug-Authorization` request header to the API Management gateway.
79
79
1. Obtain a trace ID in the `Apim-Trace-Id` response header.
80
80
1. Retrieve the trace corresponding to the trace ID.
@@ -85,7 +85,7 @@ Detailed steps follow.
85
85
> * These steps require API Management REST API version 2023-05-01-preview or later. You must be assigned the Contributor or higher role on the API Management instance to call the REST API.
86
86
> * For information about authenticating to the REST API, see [Azure REST API reference](/rest/api/azure).
87
87
88
-
1.**Obtain a token credential** - Call the API Management gateway's [List debug credentials](/rest/api/apimanagement/gateway/list-debug-credentials) API. In the URI, enter "managed" for the instance's managed gateway in the cloud, or the gateway ID for a self-hosted gateway. For example, to obtain trace credentials for the instance's managed gateway, use a request similar to the following:
88
+
1.**Obtain a debug token** - Call the API Management gateway's [List debug credentials](/rest/api/apimanagement/gateway/list-debug-credentials) API. In the URI, enter "managed" for the instance's managed gateway in the cloud, or the gateway ID for a self-hosted gateway. For example, to obtain trace credentials for the instance's managed gateway, use a request similar to the following:
89
89
90
90
```http
91
91
POST https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.ApiManagement/service/{serviceName}/gateways/managed/listDebugCredentials?api-version=2023-05-01-preview
> The `apiId` can only be pulled from the full resource ID, not the name displayed in the portal.
106
+
107
+
Get apiId:
108
+
109
+
110
+
```azurecli
111
+
az apim api list --resource-group <resource-group> --service-name <service-name> -o table
112
+
```
103
113
104
-
The token credential is returned in the response, similar to the following:
114
+
The debug credential is returned in the response, similar to the following:
105
115
106
116
```json
107
117
{
@@ -112,18 +122,20 @@ Detailed steps follow.
112
122
1. **Add the token value in a request header** - To enable tracing for a request to the API Management gateway, send the token value in an `Apim-Debug-Authorization` header. For example, to trace a call to the Petstore API that you imported in a previous tutorial, you might use a request similar to the following:
1. Depending on the token, the response contains one of the following headers:
119
-
* If the token is valid, the response includes an `Apim-Trace-Id` header whose value is the trace ID, similar to the following:
130
+
1. **Evaluate the response** - The response can contain one of the following headers depending on the state of the debug token:
131
+
* If the debug token is valid, the response includes an `Apim-Trace-Id` header whose value is the trace ID, similar to the following:
120
132
121
133
```http
122
134
Apim-Trace-Id: 0123456789abcdef....
123
135
```
124
136
125
-
* If the token is expired, the response includes an `Apim-Debug-Authorization-Expired` header with information about expiration date.
126
-
* If the token was obtained for a different API, the response includes an `Apim-Debug-Authorization-WrongAPI` header with an error message.
137
+
* If the debug token is expired, the response includes an `Apim-Debug-Authorization-Expired` header with information about expiration date.
138
+
* If the debug token was obtained for a different API, the response includes an `Apim-Debug-Authorization-WrongAPI` header with an error message.
127
139
128
140
1. **Retrieve the trace** - Pass the trace ID obtained in the previous step to the gateway's [List trace](/rest/api/apimanagement/gateway/list-trace) API. For example, to retrieve the trace for the managed gateway, use a request similar to the following:
129
141
@@ -142,6 +154,61 @@ Detailed steps follow.
142
154
The response body contains the trace data for the previous API request to the gateway. The trace is similar to the trace you can see by tracing a call in the portal's test console.
143
155
144
156
157
+
### Example `.http` file for VS Code REST Client extension
158
+
159
+
To help automate these steps with the [Visual Studio Code REST Client](https://marketplace.visualstudio.com/items?itemName=humao.rest-client) extension, you can use the following example `.http` file:
160
+
161
+
```http
162
+
@subscriptionId = // Your subscription ID
163
+
@resourceGroup = // Your resource group
164
+
@apimName = // Your API Management service name
165
+
@clientId = // Client ID from an app registration for authentication
166
+
@clientSecret = // Client secret from app registration
167
+
@externalHost = // The host name of the App Gateway or the fully qualified gateway URL
168
+
@subscriptionKey = // API Management subscription key
169
+
@apiEndPoint = // API URL
170
+
@requestBody = // Data to send
171
+
@tenantId = // Tenant ID
172
+
173
+
POST https://login.microsoftonline.com/{{tenandId}}/oauth2/token
POST https://management.azure.com/subscriptions/{{subscriptionId}}/resourceGroups/{{resourceGroup}}/providers/Microsoft.ApiManagement/service/{{apimName}}/gateways/managed/listDebugCredentials?api-version=2023-05-01-preview
POST https://management.azure.com/subscriptions/{{subscriptionId}}/resourceGroups/{{resourceGroup}}/providers/Microsoft.ApiManagement/service/{{apimName}}/gateways/managed/listTrace?api-version=2024-06-01-preview
204
+
Authorization: Bearer {{authToken}}
205
+
Content-Type: application/json
206
+
207
+
{
208
+
"traceId": "{{traceId}}"
209
+
}
210
+
```
211
+
145
212
For information about customizing trace information, see the [trace](trace-policy.md) policy.
Copy file name to clipboardExpand all lines: articles/app-service/configure-language-python.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,8 @@ adobe-target: true
13
13
14
14
# Configure a Linux Python app for Azure App Service
15
15
16
+
[](https://go.microsoft.com/fwlink/?linkid=2303112)
17
+
16
18
This article describes how [Azure App Service](overview.md) runs Python apps, how you can migrate existing apps to Azure, and how you can customize the behavior of App Service when you need to. Python apps must be deployed with all the required [pip](https://pypi.org/project/pip/) modules.
17
19
18
20
The App Service deployment engine automatically activates a virtual environment and runs `pip install -r requirements.txt` for you when you deploy a [Git repository](deploy-local-git.md), or when you deploy a [zip package](deploy-zip.md)[with build automation enabled](deploy-zip.md#enable-build-automation-for-zip-deploy).
Copy file name to clipboardExpand all lines: articles/communication-services/how-tos/calling-sdk/includes/closed-captions/closed-captions-teams-interop-android.md
-[Access tokens](../../../../quickstarts/identity/access-tokens.md) for External identity users.
19
19
- For Translated captions, you need to have a [Teams premium](/MicrosoftTeams/teams-add-on-licensing/licensing-enhance-teams#meetings) license.
20
20
21
-
>[!NOTE]
22
-
>Please note that you will need to have a voice calling app using Azure Communication Services calling SDKs to access the closed captions feature that is described in this guide.
21
+
>[!NOTE]
22
+
>Please note that you will need to have a voice calling app using Azure Communication Services calling SDKs to access the closed captions feature that is described in this guide.
Copy file name to clipboardExpand all lines: articles/communication-services/how-tos/calling-sdk/includes/closed-captions/closed-captions-teams-interop-ios.md
-[Access tokens](../../../../quickstarts/identity/access-tokens.md) for External identity users.
19
19
- For Translated captions, you need to have a [Teams premium](/MicrosoftTeams/teams-add-on-licensing/licensing-enhance-teams#meetings) license.
20
20
21
-
>[!NOTE]
22
-
>Please note that you will need to have a voice calling app using Azure Communication Services calling SDKs to access the closed captions feature that is described in this guide.
21
+
>[!NOTE]
22
+
>Please note that you will need to have a voice calling app using Azure Communication Services calling SDKs to access the closed captions feature that is described in this guide.
Copy file name to clipboardExpand all lines: articles/communication-services/how-tos/calling-sdk/includes/closed-captions/closed-captions-teams-interop-web.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,8 +17,8 @@ ms.author: kpunjabi
17
17
-[Access tokens](../../../../quickstarts/identity/access-tokens.md) for External identity users.
18
18
- For Translated captions, you need to have a [Teams premium](/MicrosoftTeams/teams-add-on-licensing/licensing-enhance-teams#meetings) license.
19
19
20
-
>[!NOTE]
21
-
>Please note that you will need to have a voice calling app using Azure Communication Services calling SDKs to access the closed captions feature that is described in this guide.
20
+
>[!NOTE]
21
+
>Please note that you will need to have a voice calling app using Azure Communication Services calling SDKs to access the closed captions feature that is described in this guide.
Copy file name to clipboardExpand all lines: articles/communication-services/how-tos/calling-sdk/includes/closed-captions/closed-captions-teams-interop-windows.md
-[Access tokens](../../../../quickstarts/identity/access-tokens.md) for External identity users.
19
19
- For Translated captions, you need to have a [Teams premium](/MicrosoftTeams/teams-add-on-licensing/licensing-enhance-teams#meetings) license.
20
20
21
-
>[!NOTE]
22
-
>Please note that you will need to have a voice calling app using Azure Communication Services calling SDKs to access the closed captions feature that is described in this guide.
21
+
>[!NOTE]
22
+
>Please note that you will need to have a voice calling app using Azure Communication Services calling SDKs to access the closed captions feature that is described in this guide.
# Quickstart: Deploy an AKS cluster with confidential computing Intel SGX agent nodes by using the Azure CLI
14
14
15
+
[](https://go.microsoft.com/fwlink/?linkid=2303213)
16
+
15
17
In this quickstart, you'll use the Azure CLI to deploy an Azure Kubernetes Service (AKS) cluster with enclave-aware (DCsv2/DCSv3) VM nodes. You'll then run a simple Hello World application in an enclave. You can also provision a cluster and add confidential computing nodes from the Azure portal, but this quickstart focuses on the Azure CLI.
16
18
17
19
AKS is a managed Kubernetes service that enables developers or cluster operators to quickly deploy and manage clusters. To learn more, read the [AKS introduction](/azure/aks/intro-kubernetes) and the [overview of AKS confidential nodes](confidential-nodes-aks-overview.md).
0 commit comments