The previous article explained why tenant customization matters and what each surface is designed to do. This one is about implementation – where these settings actually live and what I pay attention to when configuring them.
Tenant customization doesn’t live in one place in the portal. That’s the first thing that catches people off guard. The sign-in experience, the Company Portal, and browser-level settings are all configured separately, in different locations, and through different interfaces. If you go looking for a single “branding” section, you won’t find one.
Entra ID branding is configured in the Entra admin center under Company Branding. This is where you control what users see at the sign-in page – the logo, background image, sign-in page text, and the support information that appears on MFA prompts and error pages. I keep this simple. The sign-in screen isn’t a marketing surface. I want recognition, not creativity. A logo, a background that matches the organization’s visual identity, and clear support contact information. That’s it. The support details matter more than most admins expect – adding tenant name and helpdesk contact to sign-in and error screens measurably reduces retry loops and account lockouts.
Stable visuals build confidence over time. Every time I tested whether changing branding frequently affected user trust, the answer came back yes – consistency matters more than freshness.
One thing worth testing: Entra ID supports language-specific branding, which means you can configure different sign-in experiences for different locales. If your organization operates across multiple regions, this is worth the effort. A sign-in page in the wrong language looks like a phishing attempt even when it isn’t.
Company Portal branding is configured in Intune under Tenant Administration → Customization. This is where you set the organization name, logo, brand color, support website, and contact information that appears inside the portal app. The brand color here affects buttons and interface accents – it doesn’t need to be exact, but it should be recognizable as belonging to the same organization users saw at sign-in.
Platform differences matter and are easy to underestimate. The Company Portal renders differently on Windows, iOS, Android, and macOS. Text that looks clean on a Windows desktop can feel cramped on a mobile screen. I test on at least two platforms before calling this done – usually Windows and iOS, since those cover the majority of enrollment scenarios in most environments. What works on one doesn’t always translate.
The support messaging inside the portal deserves specific attention. When a user hits a compliance prompt or an app installation delay, the portal is often the first place they look for context. Clear language explaining who manages the device and how to get help reduces support tickets and reduces the likelihood of users making uninformed decisions – like ignoring compliance prompts because they don’t understand why they’re appearing.
A default portal feels distant. Requests feel arbitrary. Branding changes the tone – it reminds users that device controls are deliberate and that there’s a real team behind them.
Browser-level branding, if you’re deploying Edge as a managed browser, is configured through device configuration profiles. A managed Edge profile tied to the user’s Entra ID identity carries the organizational context into the browser experience – new tab page, profile avatar, and sync behavior all reflect the managed state. This is the lightest of the three surfaces to configure and often the last one teams get to, but it closes the visual gap between authentication and productivity that the other two surfaces leave open.
Get these three surfaces consistent before enrollment begins. The window to establish what “normal” looks like is narrow – users form expectations quickly, and reconfiguring branding after they’ve already enrolled is significantly less effective than getting it right the first time.
Intune Deployment Guide · Phase 2: Identity and Tenant Foundation
‹ Previous: [2.1.1] Tenant Customization and Branding
Next: [2.1.3] Licensing ›
