Skip to content

Commit ab595d2

Browse files
Merge pull request #231133 from rwike77/branding
fixed link
2 parents 3db36d6 + 6876f27 commit ab595d2

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

articles/active-directory/develop/howto-add-branding-in-azure-ad-apps.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,15 +9,15 @@ ms.service: active-directory
99
ms.subservice: develop
1010
ms.topic: conceptual
1111
ms.workload: identity
12-
ms.date: 08/31/2020
12+
ms.date: 03/16/2023
1313
ms.author: ryanwi
1414
ms.reviewer: arielgo, jiml
1515
ms.custom: aaddev, signin_art
1616
---
1717

1818
# Sign in with Microsoft: Branding guidelines for applications
1919

20-
When developing applications with the Microsoft identity platform, you'll need to direct your customers when they want to use their work or school account (managed in Azure AD), or their personal account for sign-up and sign-in to your application.
20+
When developing applications with the Microsoft identity platform, you need to direct your customers when they want to use their work or school account (managed in Azure AD), or their personal account for sign-up and sign-in to your application.
2121

2222
In this article, you will:
2323

@@ -44,21 +44,21 @@ Microsoft doesn’t expose end users to the Azure or the Active Directory brand
4444

4545
## User account pictogram
4646

47-
In an earlier version of these guidelines, we recommended using a “blue badge” pictogram. Based on user and developer feedback, we now recommend the use of the Microsoft logo instead. The Microsoft logo will help users understand that they can reuse the account they use with Microsoft 365 or other Microsoft business services to sign into your app.
47+
In an earlier version of these guidelines, we recommended using a “blue badge” pictogram. Based on user and developer feedback, we now recommend the use of the Microsoft logo instead. The Microsoft logo helps users understand that they can reuse the account they use with Microsoft 365 or other Microsoft business services to sign into your app.
4848

4949
## Signing up and signing in with Azure AD
5050

5151
Your app may present separate paths for sign-up and sign-in and the following sections provide visual guidance for both scenarios.
5252

53-
**If your app supports end-user sign-up (for example, free to trial or freemium model)**: You can show a **sign-in** button that allows users to access your app with their work account or their personal account. Azure AD will show a consent prompt the first time they access your app.
53+
**If your app supports end-user sign-up (for example, free to trial or freemium model)**: You can show a **sign-in** button that allows users to access your app with their work account or their personal account. Azure AD shows a consent prompt the first time they access your app.
5454

5555
**If your app requires permissions that only admins can consent to, or if your app requires organizational licensing**: Separate admin acquisition from user sign-in. The **“get this app” button** will redirect admins to sign in then ask them to grant consent on behalf of users in their organization, which has the added benefit of suppressing end-user consent prompts to your app.
5656

5757
## Visual guidance for app acquisition
5858

5959
Your “get the app” link must redirect the user to the Azure AD grant access (authorize) page, to allow an organization’s administrator to authorize your app to have access to their organization’s data, which is hosted by Microsoft. Details on how to request access are discussed in the [Integrating Applications with Azure Active Directory](./quickstart-register-app.md) article.
6060

61-
After admins consent to your app, they can choose to add it to their users’ Microsoft 365 app launcher experience (accessible from the waffle and from [https://portal.office.com/myapps](https://portal.office.com/myapps)). If you want to advertise this capability, you can use terms like “Add this app to your organization” and show a button like the following example:
61+
After admins consent to your app, they can choose to add it to their users’ Microsoft 365 app launcher experience (accessible from the waffle and from [https://www.office.com/](https://www.office.com/)). If you want to advertise this capability, you can use terms like “Add this app to your organization” and show a button like the following example:
6262

6363
![Button showing the Microsoft logo and "Add to my organization" text](./media/howto-add-branding-in-azure-ad-apps/add-to-my-org.png)
6464

0 commit comments

Comments
 (0)