Skip to content

Commit 4d50656

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into sovUp
2 parents d772571 + 709d1d9 commit 4d50656

29 files changed

+230
-227
lines changed

articles/active-directory/develop/workload-identity-federation.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -57,12 +57,12 @@ The workflow for exchanging an external token for an access token is the same, h
5757
1. When the checks are satisfied, Microsoft identity platform issues an access token to the external workload.
5858
1. The external workload accesses Azure AD protected resources using the access token from Microsoft identity platform. A GitHub Actions workflow, for example, uses the access token to publish a web app to Azure App Service.
5959

60-
The Microsoft identity platform stores only the first 25 signing keys when they're downloaded from the external IdP's OIDC endpoint. If the external IdP exposes more than 25 signing keys, you may experience errors when using Workload Identity Federation.
60+
The Microsoft identity platform stores only the first 100 signing keys when they're downloaded from the external IdP's OIDC endpoint. If the external IdP exposes more than 100 signing keys, you may experience errors when using Workload Identity Federation.
6161

6262
## Next steps
6363
Learn more about how workload identity federation works:
6464
- How Azure AD uses the [OAuth 2.0 client credentials grant](v2-oauth2-client-creds-grant-flow.md#third-case-access-token-request-with-a-federated-credential) and a client assertion issued by another IdP to get a token.
6565
- How to create, delete, get, or update [federated identity credentials](workload-identity-federation-create-trust.md) on an app registration.
6666
- How to create, delete, get, or update [federated identity credentials](workload-identity-federation-create-trust-user-assigned-managed-identity.md) on a user-assigned managed identity.
6767
- Read the [GitHub Actions documentation](https://docs.github.com/actions/deployment/security-hardening-your-deployments/configuring-openid-connect-in-azure) to learn more about configuring your GitHub Actions workflow to get an access token from Microsoft identity provider and access Azure resources.
68-
- For information about the required format of JWTs created by external identity providers, read about the [assertion format](active-directory-certificate-credentials.md#assertion-format).
68+
- For information about the required format of JWTs created by external identity providers, read about the [assertion format](active-directory-certificate-credentials.md#assertion-format).

articles/active-directory/fundamentals/5-secure-access-b2b.md

Lines changed: 127 additions & 147 deletions
Large diffs are not rendered by default.

articles/active-directory/hybrid/how-to-connect-staged-rollout.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -171,6 +171,7 @@ You can roll out these options:
171171
- **Pass-through authentication** + **Seamless SSO**
172172
- **Not supported** - **Password hash sync** + **Pass-through authentication** + **Seamless SSO**
173173
- **Certificate-based authentication settings**
174+
- **Azure multifactor authentication**
174175

175176
To configure Staged Rollout, follow these steps:
176177

articles/aks/azure-csi-blob-storage-static.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@ The following example demonstrates how to mount a Blob storage container as a pe
114114
kubectl create -f pv-blob-nfs.yaml
115115
```
116116

117-
3. Create a `pvc-blob-nfs.yaml` file with a *PersistentVolume*. For example:
117+
3. Create a `pvc-blob-nfs.yaml` file with a *PersistentVolumeClaim*. For example:
118118

119119
```yml
120120
kind: PersistentVolumeClaim

articles/azure-functions/functions-bindings-error-pages.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Azure Functions error handling and retry guidance
33
description: Learn to handle errors and retry events in Azure Functions with links to specific binding errors, including information on retry policies.
44

55
ms.topic: conceptual
6-
ms.date: 08/03/2022
6+
ms.date: 01/03/2023
77
zone_pivot_groups: programming-languages-set-functions-lang-workers
88
---
99

@@ -49,7 +49,7 @@ There are two kinds of retries available for your functions: built-in retry beha
4949

5050
| Trigger/binding | Retry source | Configuration |
5151
| ---- | ---- | ----- |
52-
| Azure Cosmos DB | n/a | Not configurable |
52+
| Azure Cosmos DB | [Retry policies](#retry-policies) | Function-level |
5353
| Blob Storage | [Binding extension](functions-bindings-storage-blob-trigger.md#poison-blobs) | [host.json](functions-bindings-storage-queue.md#host-json) |
5454
| Event Grid | [Binding extension](../event-grid/delivery-and-retry.md) | Event subscription |
5555
| Event Hubs | [Retry policies](#retry-policies) | Function-level |

articles/cosmos-db/nosql/troubleshoot-changefeed-functions.md

Lines changed: 26 additions & 29 deletions
Large diffs are not rendered by default.
63 KB
Loading

0 commit comments

Comments
 (0)