Skip to content

Commit 81fbb8a

Browse files
committed
Merge branch 'release-umc-rebranding' of https://github.com/MicrosoftDocs/azure-docs-pr into release-umc-rebranding
2 parents b6d8850 + ebbfdb2 commit 81fbb8a

File tree

392 files changed

+4296
-2230
lines changed

Some content is hidden

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

392 files changed

+4296
-2230
lines changed

.openpublishing.redirection.json

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24132,11 +24132,15 @@
2413224132
"source_path_from_root": "/articles/reliability/migrate-app-service-environment.md",
2413324133
"redirect_url": "/azure/reliability/reliability-app-service",
2413424134
"redirect_document_id": false
24135+
},
24136+
{
24137+
"source_path_from_root": "/articles/flexible-server/concepts-high-availability.md",
24138+
"redirect_url": "/azure/reliability/reliability-postgre-flexible",
24139+
"redirect_document_id": false
2413524140
}
2413624141

2413724142

2413824143

24139-
24140-
24144+
2414124145
]
2414224146
}

articles/active-directory-b2c/partner-nok-nok.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ To get started, you need:
2828
* If you don't have one, get a [Azure free account](https://azure.microsoft.com/free/)
2929
* An Azure AD B2C tenant linked to the Azure subscription
3030
* [Tutorial: Create an Azure Active Directory B2C tenant](tutorial-create-tenant.md)
31-
* Go to [noknok.com](https://noknok.com/products/strong-authentication-service/). On the top menu, select **Demo**.
31+
* Go to [noknok.com](https://noknok.com/). On the top menu, select **Demo**.
3232

3333
## Scenario description
3434

articles/active-directory/authentication/concept-fido2-hardware-vendor.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,6 @@ The following table lists partners who are Microsoft-compatible FIDO2 security k
5252
| [IDmelon Technologies Inc.](https://www.idmelon.com/#idmelon) | ![y] | ![y]| ![y]| ![y]| ![n] |
5353
| [Kensington](https://www.kensington.com/solutions/product-category/why-biometrics/) | ![y] | ![y]| ![n]| ![n]| ![n] |
5454
| [KONA I](https://konai.com/business/security/fido) | ![y] | ![n]| ![y]| ![y]| ![n] |
55-
| [Movenda](https://www.movenda.com/en/authentication/fido2/overview) | ![y] | ![n]| ![y]| ![y]| ![n] |
5655
| [NeoWave](https://neowave.fr/en/products/fido-range/) | ![n] | ![y]| ![y]| ![n]| ![n] |
5756
| [Nymi](https://www.nymi.com/nymi-band) | ![y] | ![n]| ![y]| ![n]| ![n] |
5857
| [Octatco](https://octatco.com/) | ![y] | ![y]| ![n]| ![n]| ![n] |

articles/active-directory/conditional-access/howto-conditional-access-policy-registration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ After administrators confirm the settings using [report-only mode](howto-conditi
6262

6363
Administrators will now have to issue Temporary Access Pass credentials to new users so they can satisfy the requirements for multifactor authentication to register. Steps to accomplish this task, are found in the section [Create a Temporary Access Pass in the Azure AD Portal](../authentication/howto-authentication-temporary-access-pass.md#create-a-temporary-access-pass).
6464

65-
Organizations may choose to require other grant controls with or in place of **Require multifactor authentication** at step 7a. When selecting multiple controls, be sure to select the appropriate radio button toggle to require **all** or **one** of the selected controls when making this change.
65+
Organizations may choose to require other grant controls with or in place of **Require multifactor authentication** at step 8a. When selecting multiple controls, be sure to select the appropriate radio button toggle to require **all** or **one** of the selected controls when making this change.
6666

6767
### Guest user registration
6868

articles/active-directory/develop/quickstart-create-new-tenant.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ ms.service: active-directory
88
ms.subservice: develop
99
ms.workload: identity
1010
ms.topic: quickstart
11-
ms.date: 04/19/2023
11+
ms.date: 07/11/2023
1212
ms.author: ryanwi
1313
ms.reviewer: jmprieur
1414
ms.custom: aaddev, identityplatformtop40, fasttrack-edit, mode-other
@@ -61,7 +61,7 @@ If you don't have a tenant associated with your account, you'll see a GUID under
6161

6262
### Create a new Azure AD tenant
6363

64-
If you don't already have an Azure AD tenant or if you want to create a new one for development, see [Create a new tenant in Azure AD](../fundamentals/active-directory-access-create-new-tenant.md). Or use the [directory creation experience](https://portal.azure.com/#create/Microsoft.AzureActiveDirectory) in the Azure portal.
64+
If you don't already have an Azure AD tenant or if you want to create a new one for development, see [Create a new tenant in Azure AD](../fundamentals/active-directory-access-create-new-tenant.md) or use the [directory creation experience](https://portal.azure.com/#create/Microsoft.AzureActiveDirectory) in the Azure portal. If you want to create a tenant for app testing, see [build a test environment](test-setup-environment.md).
6565

6666
You'll provide the following information to create your new tenant:
6767

articles/active-directory/saas-apps/slack-tutorial.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.service: active-directory
99
ms.subservice: saas-app-tutorial
1010
ms.workload: identity
1111
ms.topic: tutorial
12-
ms.date: 01/25/2023
12+
ms.date: 08/11/2023
1313
ms.author: jeedes
1414
---
1515

@@ -113,9 +113,6 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
113113
| emailaddress | user.userprincipalname |
114114
| email | user.userprincipalname |
115115

116-
> [!NOTE]
117-
> In order to set up the service provider (SP) configuration, you must click on **Expand** next to **Advanced Options** in the SAML configuration page. In the **Service Provider Issuer** box, enter the workspace URL. The default is slack.com.
118-
119116
1. On the **Set up single sign-on with SAML** page, in the **SAML Signing Certificate** section, find **Certificate (Base64)** and select **Download** to download the certificate and save it on your computer.
120117

121118
![The Certificate download link](common/certificatebase64.png)
@@ -187,6 +184,9 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
187184

188185
c. Choose how the SAML response from your IDP is signed from the two options.
189186

187+
> [!NOTE]
188+
> In order to set up the service provider (SP) configuration, you must click on **Expand** next to **Advanced Options** in the SAML configuration page. In the **Service Provider Issuer** box, enter the workspace URL. The default is slack.com.
189+
190190
1. Under **Settings**, decide if members can edit their profile information (like their email or display name) after SSO is enabled. You can also choose whether SSO is required, partially required or optional.
191191

192192
![Screenshot of Configure Save configuration single sign-on On App Side.](./media/slack-tutorial/save-configuration-button.png)

articles/active-directory/saas-apps/successfactors-tutorial.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ Follow these steps to enable Azure AD SSO in the Azure portal.
107107
- `https://<companyname>.sapsf.cn/<companyname>`
108108

109109
> [!NOTE]
110-
> These values are not real. Update these values with the actual Sign-on URL, Identifier and Reply URL. Contact [SuccessFactors Client support team](https://www.sap.com/support.html) to get these values.
110+
> These values are not real. Update these values with the actual Sign-on URL, Identifier and Reply URL. Contact [SuccessFactors Client support team](https://www.sap.com/services-support.html) to get these values.
111111

112112
4. On the **Set up Single Sign-On with SAML** page, in the **SAML Signing Certificate** section, find **Certificate (Base64)** and select **Download** to download the certificate and save it on your computer.
113113

@@ -212,7 +212,7 @@ In this section, you'll enable B.Simon to use Azure single sign-on by granting a
212212

213213
To enable Azure AD users to sign in to SuccessFactors, they must be provisioned into SuccessFactors. In the case of SuccessFactors, provisioning is a manual task.
214214

215-
To get users created in SuccessFactors, you need to contact the [SuccessFactors support team](https://www.sap.com/support.html).
215+
To get users created in SuccessFactors, you need to contact the [SuccessFactors support team](https://www.sap.com/services-support.html).
216216

217217
## Test SSO
218218

articles/active-directory/standards/configure-cmmc-level-2-additional-controls.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.collection: M365-identity-device-management
1616

1717
# Configure Azure Active Directory to meet CMMC Level 2
1818

19-
Azure Active Directory helps meet identity-related practice requirements in each Cybersecurity Maturity Model Certification (CMMC) level. To be compliant with requirements in [CMMC V2.0 level 2](https://cmmc-coe.org/maturity-level-two/), it's the responsibility of companies performing work with, and on behalf of, the US Dept. of Defense (DoD) to complete other configurations or processes.
19+
Azure Active Directory helps meet identity-related practice requirements in each Cybersecurity Maturity Model Certification (CMMC) level. To be compliant with requirements in CMMC V2.0 level 2, it's the responsibility of companies performing work with, and on behalf of, the US Dept. of Defense (DoD) to complete other configurations or processes.
2020

2121
In CMMC Level 2, there are 13 domains that have one or more practices related to identity:
2222

articles/active-directory/standards/configure-cmmc-level-2-identification-and-authentication.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.collection: M365-identity-device-management
1616

1717
# Configure CMMC Level 2 Identification and Authentication (IA) controls
1818

19-
Azure Active Directory helps you meet identity-related practice requirements in each Cybersecurity Maturity Model Certification (CMMC) level. To complete other configurations or processes to be compliant with [CMMC V2.0 level 2](https://cmmc-coe.org/maturity-level-two/)requirements, is the responsibility of companies performing work with, and on behalf of, the US Dept. of Defense (DoD).
19+
Azure Active Directory helps you meet identity-related practice requirements in each Cybersecurity Maturity Model Certification (CMMC) level. To complete other configurations or processes to be compliant with CMMC V2.0 level 2 requirements, is the responsibility of companies performing work with, and on behalf of, the US Dept. of Defense (DoD).
2020

2121
CMMC Level 2 has 13 domains that have one or more practices related to identity. The domains are:
2222

@@ -56,4 +56,4 @@ The following table provides a list of practice statement and objectives, and Az
5656
* [Configure Azure Active Directory for CMMC compliance](configure-for-cmmc-compliance.md)
5757
* [Configure CMMC Level 1 controls](configure-cmmc-level-1-controls.md)
5858
* [Configure CMMC Level 2 Access Control (AC) controls](configure-cmmc-level-2-access-control.md)
59-
* [Configure CMMC Level 2 additional controls](configure-cmmc-level-2-additional-controls.md)
59+
* [Configure CMMC Level 2 additional controls](configure-cmmc-level-2-additional-controls.md)

articles/active-directory/standards/configure-for-fedramp-high-impact.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ There are multiple paths towards FedRAMP authorization. You can reuse the existi
3232

3333
## Scope of guidance
3434

35-
The FedRAMP high baseline is made up of 421 controls and control enhancements from [NIST 800-53 Security Controls Catalog Revision 4](https://csrc.nist.gov/publications/detail/sp/800-53/rev-4/final). Where applicable, we included clarifying information from the [800-53 Revision 5](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final). This article set covers a subset of these controls that are related to identity, and which you must configure.
35+
The FedRAMP high baseline is made up of 421 controls and control enhancements from [NIST 800-53 Security Controls Catalog Revision 4](https://csrc.nist.gov/pubs/itlb/2015/01/release-of-nist-special-publication-80053a-revisio/final). Where applicable, we included clarifying information from the [800-53 Revision 5](https://csrc.nist.gov/publications/detail/sp/800-53/rev-5/final). This article set covers a subset of these controls that are related to identity, and which you must configure.
3636

3737
We provide prescriptive guidance to help you achieve compliance with controls you're responsible for configuring in Azure Active Directory (Azure AD). To fully address some identity control requirements, you might need to use other systems. Other systems might include a security information and event management tool, such as Microsoft Sentinel. If you're using Azure services outside of Azure Active Directory, there will be other controls you need to consider, and you can use the capabilities Azure already has in place to meet the controls.
3838

0 commit comments

Comments
 (0)