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
@@ -113,7 +140,7 @@ When your MCP server requires a bearer token, configure token retrieval in your
113
140
```
114
141
115
142
> [!TIP]
116
-
> For development, get a token by using `az account get-access-token --resource $APP_ID --query accessToken -o tsv` and paste it when prompted. For automated workflows, integrate with your organization's token management system.
143
+
> For development, get a token by using `az account get-access-token --resource api://$APP_ID --query accessToken -o tsv` and paste it when prompted. For automated workflows, integrate with your organization's token management system.
117
144
118
145
### Configure CORS
119
146
@@ -206,6 +233,7 @@ A common mistake is using the API key header (`x-ms-apikey`) with a standalone c
206
233
|----------|--------|
207
234
|`x-ms-apikey` header sent to standalone app | Header is ignored; request hits built-in authentication and returns `401` if auth is enabled |
208
235
|`Authorization: Bearer` sent to sessions MCP | Key validation fails and returns `401`|
236
+
| Bearer token requested without an exposed API scope | Token acquisition fails or the token has no valid audience, resulting in `401`|
209
237
210
238
Make sure your MCP client configuration matches the hosting model you deployed.
0 commit comments