You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When users authenticate into your corporate intranet or web-based applications, Azure Active Directory (Azure AD) provides the identity and access management (IAM) service. You can add company branding that applies to all these sign-in experiences to create a consistent experience for your users.
22
22
23
-
The default sign-in experience is the global look and feel that applies across all sign-ins to your tenant. Before you customize any settings, the default Microsoft branding appears in your sign-in pages. You can customize this default experience with a custom background image or color, favicon, layout, header, and footer. You can also upload a custom CSS.
23
+
The default sign-in experience is the global look and feel that applies across all sign-ins to your tenant. Before you customize any settings, the default Microsoft branding appears in your sign-in pages. You can customize this default experience with a custom background image and/or color, favicon, layout, header, and footer. You can also upload a custom CSS.
24
24
25
25
> [!NOTE]
26
26
> Instructions for the legacy company branding customization process can be found in the **[Customize branding](customize-branding.md)** article.<br><br>The updated experience for adding company branding covered in this article is available as an Azure AD preview feature. To opt in and explore the new experience, go to **Azure AD** > **Preview features** and enable the **Enhanced Company Branding** feature. For more information about previews, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
27
27
>
28
28
29
-
## User experience
30
-
31
-
You can customize the sign-in pages when users access your organization's tenant-specific apps. For Microsoft and SaaS applications (multi-tenant apps) such as <https://myapps.microsoft.com>, or <https://outlook.com> the customized sign-in page appears only after the user types their **Email**, or **Phone**, and select **Next**.
32
-
33
-
Some of the Microsoft applications support the home realm discovery `whr` query string parameter, or a domain variable. With the home realm discovery and domain parameter, the customized sign-in page appears immediately in the first step.
34
-
35
-
In the following examples replace the contoso.com with your own tenant name, or verified domain name:
36
-
37
-
- For Microsoft Outlook `https://outlook.com/contoso.com`
38
-
- For SharePoint online `https://contoso.sharepoint.com`
39
-
- For my app portal `https://myapps.microsoft.com/?whr=contoso.com`
Adding custom branding requires one of the following licenses:
45
32
@@ -61,6 +48,42 @@ The **Global Administrator** role is required to customize company branding.
61
48
62
49
**Use Microsoft Graph with Azure AD company branding.** Company branding can be viewed and managed using Microsoft Graph on the `/beta` endpoint and the `organizationalBranding` resource type. For more information, see the [organizational branding API documentation](/graph/api/resources/organizationalbranding?view=graph-rest-beta&preserve-view=true).
63
50
51
+
The branding elements are called out in the following example. Text descriptions are provided following the image.
52
+
53
+
:::image type="content" source="media/how-to-customize-branding/company-branding-map.png" alt-text="Screenshot of the sign-in page, with each of the company branding elements highlighted." lightbox="media/how-to-customize-branding/company-branding-map-large.png":::
54
+
55
+
1.**Favicon**: Small icon that appears on the left side of the browser tab.
56
+
1.**Header logo**: Space across the top of the web page, below the web browser navigation area.
57
+
1.**Background image** and **page background color**: The entire space behind the sign-in box.
58
+
1.**Banner logo**: The logo that appears in the upper-left corner of the sign-in box.
59
+
1.**Username hint and text**: The text that appears before a user enters their information.
60
+
1.**Sign-in page text**: Additional text you can add below the username field.
61
+
1.**Self-service password reset**: A link you can add below the sign-in page text for password resets.
62
+
1.**Template**: The layout of the page and sign-in boxes.
63
+
1.**Footer**: Text in the lower-right corner of the page where you can add Terms of use or privacy information.
64
+
65
+
### User experience
66
+
67
+
When customizing the sign-in pages that users see when accessing your organization's tenant-specific applications, there are some user experience scenarios you may need to consider.
68
+
69
+
For Microsoft, Software as a Service (SaaS), and multi-tenant applications such as <https://myapps.microsoft.com>, or <https://outlook.com>, the customized sign-in page appears only after the user types their **Email** or **Phone number** and selects the **Next** button.
70
+
71
+
Some Microsoft applications support [Home Realm Discovery](../manage-apps/home-realm-discovery-policy.md) for authentication. In these scenarios, when a customer signs in to an Azure AD common sign-in page, Azure AD can use the customer's user name to determine where they should sign in.
72
+
73
+
For customers who access applications from a custom URL, the `whr` query string parameter, or a domain variable, can be used to apply company branding at the initial sign-in screen, not just after adding the email or phone number. For example, `whr=contoso.com` would appear in the custom URL for the app. With the Home Realm Discover and domain parameter included, the company branding appears immediately in the first sign-in step. Other domain hints can be included.
74
+
75
+
In the following examples replace the contoso.com with your own tenant name, or verified domain name:
76
+
77
+
- For Microsoft Outlook `https://outlook.com/contoso.com`
78
+
- For SharePoint online `https://contoso.sharepoint.com`
79
+
- For my app portal `https://myapps.microsoft.com/?whr=contoso.com`
> The settings to manage the 'Stay signed in?' prompt can now be found in the User settings area of Azure AD. Go to **Azure AD** > **Users** > **User settings**.
84
+
<br><br>
85
+
For more information on the 'Stay signed in?' prompt, see [How to manage user profile information](how-to-manage-user-profile-info.md#learn-about-the-stay-signed-in-prompt).
86
+
64
87
## How to navigate the company branding process
65
88
66
89
1. Sign in to the [Azure portal](https://portal.azure.com/) using a Global Administrator account for the directory.
@@ -78,6 +101,8 @@ The sign-in experience process is grouped into sections. At the end of each sect
78
101
79
102
-**Favicon**: Select a PNG or JPG of your logo that appears in the web browser tab.
80
103
104
+

105
+
81
106
-**Background image**: Select a PNG or JPG to display as the main image on your sign-in page. This image scales and crops according to the window size, but may be partially blocked by the sign-in prompt.
82
107
83
108
-**Page background color**: If the background image isn't able to load because of a slower connection, your selected background color appears instead.
@@ -88,13 +113,19 @@ The sign-in experience process is grouped into sections. At the end of each sect
88
113
89
114
- Choose one of two **Templates**: Full-screen or partial-screen background. The full-screen background could obscure your background image, so choose the partial-screen background if your background image is important.
90
115
- The details of the **Header** and **Footer** options are set on the next two sections of the process.
116
+
117
+

91
118
92
-
-**Custom CSS**: Upload custom CSS to replace the Microsoft default style of the page. [Download the CSS template](https://download.microsoft.com/download/7/2/7/727f287a-125d-4368-a673-a785907ac5ab/custom-styles-template-013023.css).
119
+
-**Custom CSS**: Upload custom CSS to replace the Microsoft default style of the page.
120
+
-[Download the CSS template](https://download.microsoft.com/download/7/2/7/727f287a-125d-4368-a673-a785907ac5ab/custom-styles-template-013023.css).
121
+
- View the [CSS template reference guide](reference-company-branding-css-template.md).
93
122
94
123
## Header
95
124
96
125
If you haven't enabled the header, go to the **Layout** section and select **Show header**. Once enabled, select a PNG or JPG to display in the header of the sign-in page.
97
126
127
+

128
+
98
129
## Footer
99
130
100
131
If you haven't enabled the footer, go to the **Layout** section and select **Show footer**. Once enabled, adjust the following settings.
@@ -103,7 +134,7 @@ If you haven't enabled the footer, go to the **Layout** section and select **Sho
103
134
104
135
Uncheck this option to hide the default Microsoft link. Optionally provide your own **Display text** and **URL**. The text and links don't have to be related to privacy and cookies.
105
136
106
-
-**Show 'Terms of Use'**: This option is also elected by default and displays the [Microsoft 'Terms of Use'](https://www.microsoft.com/servicesagreement/) link.
137
+
-**Show 'Terms of Use'**: This option is also selected by default and displays the [Microsoft 'Terms of Use'](https://www.microsoft.com/servicesagreement/) link.
107
138
108
139
Uncheck this option to hide the default Microsoft link. Optionally provide your own **Display text** and **URL**. The text and links don't have to be related to your terms of use.
109
140
@@ -159,8 +190,12 @@ To create an inclusive experience for all of your users, you can customize the s
159
190
160
191
The process for customizing the experience is the same as the [default sign-in experience](#basics) process, except you must select a language from the dropdown list in the **Basics** section. We recommend adding custom text in the same areas as your default sign-in experience.
161
192
193
+
Azure AD supports right-to-left functionality for languages such as Arabic and Hebrew that are read right-to-left. The layout adjusts automatically, based on the user's browser settings.
194
+
195
+

196
+
162
197
## Next steps
163
198
199
+
-[View the CSS template reference guide](reference-company-branding-css-template.md).
164
200
-[Learn more about default user permissions in Azure AD](../fundamentals/users-default-permissions.md)
165
-
166
-
-[Manage the 'stay signed in' prompt](active-directory-users-profile-azure-portal.md#learn-about-the-stay-signed-in-prompt)
201
+
-[Manage the 'stay signed in' prompt](how-to-manage-user-profile-info.md#learn-about-the-stay-signed-in-prompt)
Copy file name to clipboardExpand all lines: articles/active-directory/fundamentals/how-to-manage-user-profile-info.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Add or update user profile information
2
+
title: How to manage user profile information
3
3
description: Instructions about how to manage a user's profile and settings in Azure Active Directory.
4
4
services: active-directory
5
5
author: shlipsey3
@@ -9,7 +9,7 @@ ms.service: active-directory
9
9
ms.workload: identity
10
10
ms.subservice: fundamentals
11
11
ms.topic: how-to
12
-
ms.date: 11/21/2022
12
+
ms.date: 03/23/2023
13
13
ms.author: sarahlipsey
14
14
ms.reviewer: jeffsta
15
15
ms.collection: M365-identity-device-management
@@ -80,11 +80,11 @@ Go to **Azure AD** > **User settings**.
80
80
81
81
### Learn about the 'Stay signed in?' prompt
82
82
83
-
The **Stay signed in?** prompt appears after a user successfully signs in. This process is known as **Keep me signed in** (KMSI). If a user answers **Yes** to this prompt, the KMSI service gives them a persistent [refresh token](../develop/developer-glossary.md#refresh-token). For federated tenants, the prompt will show after the user successfully authenticates with the federated identity service.
83
+
The **Stay signed in?** prompt appears after a user successfully signs in. This process is known as **Keep me signed in** (KMSI). If a user answers **Yes** to this prompt, a persistent authentication cookie is issued. The cookie must be stored in session for KMSI to work. KMSI won't work with locally stored cookies. If KMSI isn't enabled, a non-persistent cookie is issued and lasts for 24 hours or until the browser is closed.
84
84
85
-
The following diagram shows the user sign-in flow for a managed tenant and federated tenant using the KMSI in prompt. This flow contains smart logic so that the **Stay signed in?** option won't be displayed if the machine learning system detects a high-risk sign-in or a sign-in from a shared device.
85
+
The following diagram shows the user sign-in flow for a managed tenant and federated tenant using the KMSI in prompt. This flow contains smart logic so that the **Stay signed in?** option won't be displayed if the machine learning system detects a high-risk sign-in or a sign-in from a shared device. For federated tenants, the prompt will show after the user successfully authenticates with the federated identity service.
86
86
87
-
KMSI setting is available in User settings. Some features of SharePoint Online and Office 2010 depend on users being able to choose to remain signed in. If you uncheck the **Show option to remain signed in** option, your users may see other unexpected prompts during the sign-in process.
87
+
The KMSI setting is available in **User settings**. Some features of SharePoint Online and Office 2010 depend on users being able to choose to remain signed in. If you uncheck the **Show option to remain signed in** option, your users may see other unexpected prompts during the sign-in process.
88
88
89
89

90
90
@@ -101,7 +101,7 @@ If a user doesn't act on the **Stay signed in?** prompt but abandons the sign-in
101
101
102
102

103
103
104
-
Details about the sign-in error are found in the **Sign-in logs** in Azure AD. Select the impacted user from the list and locate the details below in the **Basic info** section.
104
+
Details about the sign-in error are found in the **Sign-in logs** in Azure AD. Select the impacted user from the list and locate the following error code details in the **Basic info** section.
105
105
106
106
***Sign in error code**: 50140
107
107
***Failure reason**: This error occurred due to "Keep me signed in" interrupt when the user was signing in.
0 commit comments