Skip to content

Commit c096daa

Browse files
committed
Merge branch 'main' into eur/voices-locales
2 parents 66aff75 + 860006a commit c096daa

File tree

303 files changed

+3794
-1944
lines changed

Some content is hidden

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

303 files changed

+3794
-1944
lines changed

.openpublishing.redirection.json

Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24142,10 +24142,29 @@
2414224142
"source_path": "articles/azure-cache-for-redis/cache-how-to-functions.md",
2414324143
"redirect_url": "/azure/azure-functions/functions-bindings-cache",
2414424144
"redirect_document_id": false
24145+
},
24146+
{
24147+
"source_path_from_root": "/articles/active-directory/external-identities/customers/how-to-single-page-app-vanillajs-configure-authentication.md",
24148+
"redirect_url": "/azure/active-directory/external-identities/customers/tutorial-single-page-app-vanillajs-configure-authentication",
24149+
"redirect_document_id": false
24150+
},
24151+
{
24152+
"source_path_from_root": "/articles/active-directory/external-identities/customers/how-to-single-page-app-vanillajs-prepare-app.md",
24153+
"redirect_url": "/azure/active-directory/external-identities/customers/tutorial-single-page-app-vanillajs-prepare-app",
24154+
"redirect_document_id": false
24155+
},
24156+
{
24157+
"source_path_from_root": "/articles/active-directory/external-identities/customers/how-to-single-page-app-vanillajs-prepare-tenant.md",
24158+
"redirect_url": "/azure/active-directory/external-identities/customers/tutorial-single-page-app-vanillajs-prepare-tenant",
24159+
"redirect_document_id": false
24160+
},
24161+
{
24162+
"source_path_from_root": "/articles/active-directory/external-identities/customers/how-to-single-page-app-vanillajs-sign-in-sign-out.md",
24163+
"redirect_url": "/azure/active-directory/external-identities/customers/tutorial-single-page-app-vanillajs-sign-in-sign-out",
24164+
"redirect_document_id": false
2414524165
}
2414624166

2414724167

24148-
2414924168

2415024169
]
2415124170
}
Lines changed: 56 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,56 @@
1+
---
2+
title: Microsoft Entra architecture icons
3+
description: Learn about the official collection of Microsoft Entra icons that you can use in architectural diagrams, training materials, or documentation.
4+
author: CelesteDG
5+
manager: CelesteDG
6+
ms.service: active-directory
7+
ms.subservice: fundamentals
8+
ms.topic: conceptual
9+
ms.date: 08/15/2023
10+
ms.author: celested
11+
ms.reviewer: nicholepet
12+
13+
# Customer intent: As a new or existing customer, I want to learn how I can use the official Microsoft Entra icons in architectural diagrams, training materials, or documentation.
14+
---
15+
16+
# Microsoft Entra architecture icons
17+
18+
Helping our customers design and architect new solutions is core to the Microsoft Entra mission. Architecture diagrams can help communicate design decisions and the relationships between components of a given workload. This article provides information about the official collection of Microsoft Entra icons that you can use in architectural diagrams, training materials, or documentation.
19+
20+
## General guidelines
21+
22+
### Do's
23+
24+
- Use the icon to illustrate how products can work together.
25+
- In diagrams, we recommend including the product name somewhere close to the icon.
26+
27+
### Don'ts
28+
29+
- Don't crop, flip, or rotate icons.
30+
- Don't distort or change the icon shape in any way.
31+
- Don't use Microsoft product icons to represent your product or service.
32+
- Don't use Microsoft product icons in marketing communications.
33+
34+
## Icon updates
35+
36+
| Month | Change description |
37+
|-------|--------------------|
38+
| August 2023 | Added a downloadable package that contains the Microsoft Entra architecture icons, branding playbook (which contains guidelines about the Microsoft Security visual identity), and terms of use. |
39+
40+
## Icon terms
41+
42+
Microsoft permits the use of these icons in architectural diagrams, training materials, or documentation. You may copy, distribute, and display the icons only for the permitted use unless granted explicit permission by Microsoft. Microsoft reserves all other rights.
43+
44+
<div id="consent-checkbox">
45+
I agree to the above terms.
46+
</div>
47+
48+
> [!div class="button"]
49+
> [Download icons](https://download.microsoft.com/download/a/4/2/a4289cad-4eaf-4580-87fd-ce999a601516/Microsoft-Entra-architecture-icons.zip?wt.mc_id=microsoftentraicons_downloadmicrosoftentraicons_content_cnl_csasci)
50+
51+
## More icon sets from Microsoft
52+
53+
- [Azure architecture icons](/azure/architecture/icons)
54+
- [Microsoft 365 architecture icons and templates](/microsoft-365/solutions/architecture-icons-templates)
55+
- [Dynamics 365 icons](/dynamics365/get-started/icons)
56+
- [Microsoft Power Platform icons](/power-platform/guidance/icons)

articles/active-directory/architecture/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,8 @@ items:
77
items:
88
- name: Azure AD architecture
99
href: architecture.md
10+
- name: Microsoft Entra architecture icons
11+
href: architecture-icons.md
1012
- name: Road to the cloud
1113
items:
1214
- name: Introduction

articles/active-directory/authentication/concept-authentication-default-enablement.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ services: active-directory
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: conceptual
9-
ms.date: 06/22/2023
9+
ms.date: 08/16/2023
1010

1111
ms.author: justinha
1212
author: mjsantani
@@ -58,6 +58,7 @@ The following table lists each setting that can be set to Microsoft managed and
5858
| [Application name in Microsoft Authenticator notifications](how-to-mfa-additional-context.md) | Disabled |
5959
| [System-preferred MFA](concept-system-preferred-multifactor-authentication.md) | Enabled |
6060
| [Authenticator Lite](how-to-mfa-authenticator-lite.md) | Enabled |
61+
| [Report suspicious activity](howto-mfa-mfasettings.md#report-suspicious-activity) | Disabled |
6162

6263
As threat vectors change, Azure AD may announce default protection for a **Microsoft managed** setting in [release notes](../fundamentals/whats-new.md) and on commonly read forums like [Tech Community](https://techcommunity.microsoft.com/). For example, see our blog post [It's Time to Hang Up on Phone Transports for Authentication](https://techcommunity.microsoft.com/t5/microsoft-entra-azure-ad-blog/it-s-time-to-hang-up-on-phone-transports-for-authentication/ba-p/1751752) for more information about the need to move away from using SMS and voice calls, which led to default enablement for the registration campaign to help users to set up Authenticator for modern authentication.
6364

articles/active-directory/authentication/howto-mfa-mfasettings.md

Lines changed: 9 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,12 @@ services: multi-factor-authentication
66
ms.service: active-directory
77
ms.subservice: authentication
88
ms.topic: how-to
9-
ms.date: 07/17/2023
9+
ms.date: 08/16/2023
1010

1111
ms.author: justinha
1212
author: justinha
1313
manager: amycolannino
14-
ms.reviewer: michmcla
14+
ms.reviewer: jupetter
1515

1616
ms.collection: M365-identity-device-management
1717
ms.custom: contperf-fy20q4
@@ -87,11 +87,16 @@ To unblock a user, complete the following steps:
8787

8888
Users who report an MFA prompt as suspicious are set to **High User Risk**. Administrators can use risk-based policies to limit access for these users, or enable self-service password reset (SSPR) for users to remediate problems on their own. If you previously used the **Fraud Alert** automatic blocking feature and don't have an Azure AD P2 license for risk-based policies, you can use risk detection events to identify and disable impacted users and automatically prevent their sign-in. For more information about using risk-based policies, see [Risk-based access policies](../identity-protection/concept-identity-protection-policies.md).
8989

90-
To enable **Report suspicious activity** from the Authentication Methods Settings:
90+
To enable **Report suspicious activity** from the Authentication methods **Settings**:
9191

9292
1. In the Azure portal, click **Azure Active Directory** > **Security** > **Authentication Methods** > **Settings**.
93-
1. Set **Report suspicious activity** to **Enabled**.
93+
1. Set **Report suspicious activity** to **Enabled**. The feature remains disabled if you choose **Microsoft managed**. For more information about Microsoft managed values, see [Protecting authentication methods in Azure Active Directory](concept-authentication-default-enablement.md).
9494
1. Select **All users** or a specific group.
95+
1. Select a **Reporting code**.
96+
1. Click **Save**.
97+
98+
>[!NOTE]
99+
>If you enable **Report suspicious activity** and specify a custom voice reporting value while the tenant still has **Fraud Alert** enabled in parallel with a custom voice reporting number configured, the **Report suspicious activity** value will be used instead of **Fraud Alert**.
95100
96101
### View suspicious activity events
97102

articles/active-directory/develop/howto-create-self-signed-certificate.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ To customize the start and expiry date and other properties of the certificate,
4646

4747
Use the certificate you create using this method to authenticate from an application running from your machine. For example, authenticate from Windows PowerShell.
4848

49-
In an elevated PowerShell prompt, run the following command and leave the PowerShell console session open. Replace `{certificateName}` with the name that you wish to give to your certificate.
49+
In a PowerShell prompt, run the following command and leave the PowerShell console session open. Replace `{certificateName}` with the name that you wish to give to your certificate.
5050

5151
```powershell
5252
$certname = "{certificateName}" ## Replace {certificateName}

articles/active-directory/develop/identity-videos.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -175,12 +175,12 @@ ___
175175

176176

177177
<!-- IMAGES -->
178-
[auth-fund-01-img]: ./media/identity-videos/aad-auth-fund-01.jpg
179-
[auth-fund-02-img]: ./media/identity-videos/aad-auth-fund-02.jpg
180-
[auth-fund-03-img]: ./media/identity-videos/aad-auth-fund-03.jpg
181-
[auth-fund-04-img]: ./media/identity-videos/aad-auth-fund-04.jpg
182-
[auth-fund-05-img]: ./media/identity-videos/aad-auth-fund-05.jpg
183-
[auth-fund-06-img]: ./media/identity-videos/aad-auth-fund-06.jpg
178+
[auth-fund-01-img]: ./media/identity-videos/auth-fund-01.jpg
179+
[auth-fund-02-img]: ./media/identity-videos/auth-fund-02.jpg
180+
[auth-fund-03-img]: ./media/identity-videos/auth-fund-03.jpg
181+
[auth-fund-04-img]: ./media/identity-videos/auth-fund-04.jpg
182+
[auth-fund-05-img]: ./media/identity-videos/auth-fund-05.jpg
183+
[auth-fund-06-img]: ./media/identity-videos/auth-fund-06.jpg
184184

185185
<!-- VIDEOS -->
186186
[auth-fund-01-vid]: https://www.youtube.com/watch?v=fbSVgC8nGz4&list=PLLasX02E8BPD5vC2XHS_oHaMVmaeHHPLy&index=1

articles/active-directory/develop/mark-app-as-publisher-verified.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,58 +1,58 @@
11
---
22
title: Mark an app as publisher verified
3-
description: Describes how to mark an app as publisher verified. When an application is marked as publisher verified, it means that the publisher (application developer) has verified the authenticity of their organization using a Microsoft Partner Network (MPN) account that has completed the verification process and has associated this MPN account with that application registration.
3+
description: Describes how to mark an app as publisher verified. When an application is marked as publisher verified, it means that the publisher (application developer) has verified the authenticity of their organization using a Cloud Partner Program (CPP) account that has completed the verification process and has associated this CPP account with that application registration.
44
services: active-directory
55
author: rwike77
66
manager: CelesteDG
77
ms.service: active-directory
88
ms.subservice: develop
99
ms.topic: how-to
1010
ms.workload: identity
11-
ms.date: 03/16/2023
11+
ms.date: 08/17/2023
1212
ms.author: ryanwi
1313
ms.custom: aaddev
1414
ms.reviewer: xurobert
1515
---
1616

1717
# Mark your app as publisher verified
1818

19-
When an app registration has a verified publisher, it means that the publisher of the app has [verified](/partner-center/verification-responses) their identity using their Microsoft Partner Network (MPN) account and has associated this MPN account with their app registration. This article describes how to complete the [publisher verification](publisher-verification-overview.md) process.
19+
When an app registration has a verified publisher, it means that the publisher of the app has [verified](/partner-center/verification-responses) their identity using their Cloud Partner Program (CPP) account and has associated this CPP account with their app registration. This article describes how to complete the [publisher verification](publisher-verification-overview.md) process.
2020

2121
## Quickstart
22-
If you are already enrolled in the Microsoft Partner Network (MPN) and have met the [pre-requisites](publisher-verification-overview.md#requirements), you can get started right away:
22+
If you are already enrolled in the [Cloud Partner Program (CPP)](/partner-center/intro-to-cloud-partner-program-membership) and have met the [pre-requisites](publisher-verification-overview.md#requirements), you can get started right away:
2323

2424
1. Sign into the [App Registration portal](https://aka.ms/PublisherVerificationPreview) using [multi-factor authentication](../fundamentals/concept-fundamentals-mfa-get-started.md)
2525

2626
1. Choose an app and click **Branding & properties**.
2727

28-
1. Click **Add MPN ID to verify publisher** and review the listed requirements.
28+
1. Click **Add Partner One ID to verify publisher** and review the listed requirements.
2929

30-
1. Enter your MPN ID and click **Verify and save**.
30+
1. Enter your Partner One ID and click **Verify and save**.
3131

3232
For more details on specific benefits, requirements, and frequently asked questions see the [overview](publisher-verification-overview.md).
3333

3434
## Mark your app as publisher verified
3535
Make sure you meet the [pre-requisites](publisher-verification-overview.md#requirements), then follow these steps to mark your app(s) as Publisher Verified.
3636

37-
1. Sign in using [multi-factor authentication](../fundamentals/concept-fundamentals-mfa-get-started.md) to an organizational (Azure AD) account authorized to make changes to the app you want to mark as Publisher Verified and on the MPN Account in Partner Center.
37+
1. Sign in using [multi-factor authentication](../fundamentals/concept-fundamentals-mfa-get-started.md) to an organizational (Azure AD) account authorized to make changes to the app you want to mark as Publisher Verified and on the CPP Account in Partner Center.
3838

3939
- The Azure AD user must have one of the following [roles](../roles/permissions-reference.md): Application Admin, Cloud Application Admin, or Global Administrator.
4040

41-
- The user in Partner Center must have the following [roles](/partner-center/permissions-overview): MPN Admin, Accounts Admin, or a Global Administrator (a shared role mastered in Azure AD).
41+
- The user in Partner Center must have the following [roles](/partner-center/permissions-overview): CPP Admin, Accounts Admin, or a Global Administrator (a shared role mastered in Azure AD).
4242

4343
1. Navigate to the **App registrations** blade:
4444

4545
1. Click on an app you would like to mark as Publisher Verified and open the **Branding & properties** blade.
4646

4747
1. Ensure the app’s [publisher domain](howto-configure-publisher-domain.md) is set.
4848

49-
1. Ensure that either the publisher domain or a DNS-verified [custom domain](../fundamentals/add-custom-domain.md) on the tenant matches the domain of the email address used during the verification process for your MPN account.
49+
1. Ensure that either the publisher domain or a DNS-verified [custom domain](../fundamentals/add-custom-domain.md) on the tenant matches the domain of the email address used during the verification process for your CPP account.
5050

51-
1. Click **Add MPN ID to verify publisher** near the bottom of the page.
51+
1. Click **Add Partner One ID to verify publisher** near the bottom of the page.
5252

53-
1. Enter the **MPN ID** for:
53+
1. Enter the **Partner One ID** for:
5454

55-
- A valid Microsoft Partner Network account that has completed the verification process.
55+
- A valid Cloud Partner Program account that has completed the verification process.
5656

5757
- The Partner global account (PGA) for your organization.
5858

0 commit comments

Comments
 (0)