Skip to content

Commit 3d15886

Browse files
author
gitName
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into apicteams
2 parents e0c96d4 + fc6da31 commit 3d15886

File tree

1,381 files changed

+9336
-6017
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

1,381 files changed

+9336
-6017
lines changed

.openpublishing.redirection.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3100,6 +3100,16 @@
31003100
"redirect_url": "https://docs.sendgrid.com/for-developers/partners/microsoft-azure-2021#create-a-twilio-sendgrid-account",
31013101
"redirect_document_id": false
31023102
},
3103+
{
3104+
"source_path_from_root": "/articles/synapse-analytics/whats-new.md",
3105+
"redirect_url": "/fabric/get-started/whats-new",
3106+
"redirect_document_id": false
3107+
},
3108+
{
3109+
"source_path_from_root": "/articles/synapse-analytics/whats-new-archive.md",
3110+
"redirect_url": "/fabric/get-started/whats-new",
3111+
"redirect_document_id": false
3112+
},
31033113
{
31043114
"source_path_from_root": "/articles/terraform/terrafom-quickstart.md",
31053115
"redirect_url": "/azure/terraform/terraform-create-configuration",

articles/active-directory-b2c/faq.yml

Lines changed: 3 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -22,15 +22,11 @@ sections:
2222
- question: |
2323
What is Microsoft Entra External ID?
2424
answer: |
25-
We announced an early preview of our next-generation Microsoft Entra External ID solution. This early preview represents an evolutionary step in unifying secure and engaging experiences across all external identities including partners, customers, citizens, patients, and others within a single, integrated platform. For more information about the preview, see [What is Microsoft Entra External ID for customers?](../active-directory/external-identities/customers/overview-customers-ciam.md).
25+
We have released our next generation Microsoft Entra External ID product which combines powerful solutions for working with people outside of your organization. With External ID capabilities, you can allow external identities to securely access your apps and resources. Whether you’re working with external partners, consumers, or business customers, users can bring their own identities. These identities can range from corporate or government-issued accounts to social identity providers like Google or Facebook. For more information, see [Introduction to Microsoft Entra External ID](/entra/external-id/external-identities-overview)
2626
- question: |
2727
How does this preview affect me?
2828
answer: |
29-
No action is required on your part at this time. The next-generation platform is currently in early preview only. We remain fully committed to supporting your current Azure AD B2C solution. There are no requirements for Azure AD B2C customers to migrate at this time and no plans to discontinue the current Azure AD B2C service. As the next generation platform approaches GA, details will be made available to all our valued B2C customers on available options including migration to the new platform.
30-
- question: |
31-
How do I participate in the preview?
32-
answer: |
33-
As the next-generation platform represents our future for customer identity and access management (CIAM), we welcome and encourage your participation and feedback during early preview. If you're interested in joining the early preview, contact your sales team for details.
29+
No action is required on your part at this time. We remain fully committed to supporting your current Azure AD B2C solution. There are no requirements for Azure AD B2C customers to migrate at this time and no plans to discontinue the current Azure AD B2C service.
3430
- name: General
3531
questions:
3632
- question: |
@@ -119,7 +115,7 @@ sections:
119115
Currently, you can’t change the "From:" field on the email.
120116
121117
> [!TIP]
122-
> With Azure AD B2C [custom policy](custom-policy-overview.md), you can customize the email Azure AD B2C sends to users, including the "From:" field on the email. The custom email verification requires the use of a third-party email provider like [Mailjet](custom-email-mailjet.md), [SendGrid](custom-email-sendgrid.md), or [SparkPost](https://messagebird.com/email/cloud-sending?sp=true).
118+
> With Azure AD B2C [custom policy](custom-policy-overview.md), you can customize the email Azure AD B2C sends to users, including the "From:" field on the email. The custom email verification requires the use of a third-party email provider like [Mailjet](custom-email-mailjet.md) or [SendGrid](custom-email-sendgrid.md).
123119
124120
- question: |
125121
How can I migrate my existing user names, passwords, and profiles from my database to Azure AD B2C?
132 KB
Loading

articles/active-directory-b2c/policy-keys-overview.md

Lines changed: 15 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -50,8 +50,8 @@ The top-level resource for policy keys in Azure AD B2C is the **Keyset** contain
5050
| Attribute | Required | Remarks |
5151
| --- | --- |--- |
5252
| `use` | Yes | Usage: Identifies the intended use of the public key. Encrypting data `enc`, or verifying the signature on data `sig`.|
53-
| `nbf`| No | Activation date and time. |
54-
| `exp`| No | Expiration date and time. |
53+
| `nbf`| No | Activation date and time. An override value can be set manually by admins.|
54+
| `exp`| No | Expiration date and time. An override value can be set manually by admins.|
5555

5656
We recommend setting the key activation and expiration values according to your PKI standards. You might need to rotate these certificates periodically for security or policy reasons. For example, you might have a policy to rotate all your certificates every year.
5757

@@ -72,10 +72,22 @@ If an Azure AD B2C keyset has multiple keys, only one of the keys is active at a
7272
- The key activation is based on the **activation date**.
7373
- The keys are sorted by activation date in ascending order. Keys with activation dates further into the future appear lower in the list. Keys without an activation date are located at the bottom of the list.
7474
- When the current date and time is greater than a key's activation date, Azure AD B2C will activate the key and stop using the prior active key.
75-
- When the current key's expiration time has elapsed and the key container contains a new key with valid *not before* and *expiration* times, the new key will become active automatically.
75+
- When the current key's expiration time has elapsed and the key container contains a new key with valid *nbf (not before)* and *exp (expiration)* times, the new key will become active automatically. New tokens will be signed with the newly active key. It is possible to keep an expired key published for token validation until disabled by an admin, but this must be requested by [filing a support request](/azure/active-directory-b2c/find-help-open-support-ticket).
76+
7677
- When the current key's expiration time has elapsed and the key container *does not* contain a new key with valid *not before* and *expiration* times, Azure AD B2C won't be able to use the expired key. Azure AD B2C will raise an error message within a dependant component of your custom policy. To avoid this issue, you can create a default key without activation and expiration dates as a safety net.
7778
- The key's endpoint (JWKS URI) of the OpenId Connect well-known configuration endpoint reflects the keys configured in the Key Container, when the Key is referenced in the [JwtIssuer Technical Profile](./jwt-issuer-technical-profile.md). An application using an OIDC library will automatically fetch this metadata to ensure it uses the correct keys to validate tokens. For more information, learn how to use [Microsoft Authentication Library](../active-directory/develop/msal-b2c-overview.md), which always fetches the latest token signing keys automatically.
7879

80+
:::image type="content" source="media/policy-keys-overview/key-rollover.png" alt-text="A diagram describing the process for key rollover in Azure AD B2C." lightbox="media/policy-keys-overview/key-rollover.png":::
81+
82+
83+
## Key caching
84+
85+
When a key is uploaded, the activation flag on the key is set to false by default. You can then set the state of this key to **Enabled**. If a key enabled and valid (current time is between NBF and EXP), then the key will be used.
86+
87+
### Key state
88+
89+
The activation flag property is modifiable within the Azure portal UX allowing admins to disable a key and take it out of rotation.
90+
7991
## Policy key management
8092

8193
To get the current active key within a key container, use the Microsoft Graph API [getActiveKey](/graph/api/trustframeworkkeyset-getactivekey) endpoint.

articles/api-center/TOC.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,8 @@
4646
items:
4747
- name: Use metadata for governance
4848
href: metadata.md
49+
- name: Govern APIs - VS Code extension
50+
href: govern-apis-vscode-extension.md
4951
- name: API analysis - Microsoft managed
5052
href: enable-managed-api-analysis-linting.md
5153
- name: API analysis - self-managed
@@ -58,6 +60,8 @@
5860
href: set-up-notification-workflow.md
5961
- name: API discovery and consumption
6062
items:
63+
- name: Discover and consume APIs - VS Code extension
64+
href: discover-apis-vscode-extension.md
6165
- name: Enable platform API catalog - VS Code extension
6266
href: enable-platform-api-catalog-vscode-extension.md
6367
- name: Self-host Azure API Center portal

0 commit comments

Comments
 (0)