Powered by Intentional Design
Microsoft 365 Branding Roadmap
Beyond Contoso
Because your organization is not a demo tenant.
What This Is
Every Microsoft 365 tenant starts the same way. Default purple. Generic logo placeholder. A SharePoint intranet that looks like it came from a 2019 tutorial. Teams channels named after org chart boxes. A login page that could belong to anyone.
Sound familiar? That's Contoso energy. And your organization deserves better.
This is a living roadmap for Microsoft 365 administrators, IT leaders, and anyone who cares about the experience of the humans using these tools every day. Every item here is achievable through configuration — no custom development, no PowerShell wizardry required unless noted, no Azure DevOps pipelines.
Fork it. Adapt it. Build on it. Share it.
Before You Start: Brand Alignment
Configuration decisions should follow brand decisions — not the other way around. Before you change a single setting, get answers to these questions with your communications or brand team.
The fastest path to a 'branded' M365 tenant that still feels off is applying colors without intent. Contoso has colors too. The difference is purpose.
ADA & Accessibility
Every branding decision is also an accessibility decision. Microsoft 365 serves everyone in your organization — accessibility is not optional.
Color Contrast Requirements (WCAG 2.1 AA)
| Element | Minimum Ratio | Recommended |
|---|---|---|
| Normal text on background | 4.5:1 | 7:1 |
| Large text (18pt+ or 14pt bold) | 3:1 | 4.5:1 |
| UI components (buttons, icons, focus indicators) | 3:1 | 4.5:1 |
| Decorative elements only | No requirement | — |
Free Contrast Checking Tools
Image & Content Rules
- Always add alt text to images used in SharePoint pages and Viva Connections cards
- Do not use color alone to convey meaning in dashboards or org charts
- Avoid text embedded in images — use real text with proper contrast instead
- Test your SharePoint home site with Accessibility Insights before launch
Logo & Image Dimensions
Microsoft 365 has specific size requirements that vary by surface. Use these before exporting from your design tool.
| Surface | Size | Format | Notes |
|---|---|---|---|
| M365 Admin Center — Square Logo (light bg) | 200 × 200px max | PNG (transparent bg) | Sign-in page and throughout suite on light backgrounds |
| M365 Admin Center — Square Logo (dark bg) | 200 × 200px max | PNG (transparent bg) | Dark/high contrast backgrounds — submit both versions |
| M365 Admin Center — Banner Logo | 280 × 60px max | PNG (transparent bg) | Appears above the sign-in form |
| SharePoint Site Logo | 64 × 64px (min) | PNG (transparent bg) | Suite bar and site header |
| SharePoint Header background | 1920 × 300px | JPG or PNG | Design for center-crop on smaller screens |
| SharePoint Page banner | 1920 × 500px | JPG or PNG | Page headers — keep key content centered |
| Teams custom background | 1920 × 1080px | JPG or PNG | Branded virtual meeting backgrounds |
| Viva Connections — Dashboard logo | 220 × 220px | PNG (transparent bg) | Top of Viva Connections dashboard |
| Viva Engage — Cover image | 1200 × 200px | JPG or PNG | Community and network cover images |
| Teams app icon (custom app) | 192 × 192px + 32 × 32px outline | PNG | Only if publishing a custom Teams app |
| Email signature logo | 200 × 80px | PNG | Keep file size under 50KB for deliverability |
| Favicon (SharePoint sites) | 16 × 16px or 32 × 32px | ICO or PNG | Set per site via Site Settings |
Always export at 2× your target dimensions and let Microsoft scale down. Scaling up creates blurry logos — especially painful on high-DPI screens and mobile.
Microsoft has file size limits. Keep logos under 10KB where possible, and background images under 2MB.
Tier 1 — Highest Impact
Do These FirstOrganized by impact level. Start here for the fastest visible wins across every surface in your tenant.
Item 1
M365 Admin Center — Organizational Branding
Your single most powerful move. Changes here propagate automatically across Teams, SharePoint, Outlook on the web, and the M365 portal.
What you can configure
- Organization name (displayed in the suite bar)
- Logo image — light and dark background versions
- Custom color for navigation bar and accent elements
- Sign-in page background image or color
- Banner logo (appears above the sign-in form)
- Link color
Steps
- 1Go to admin.microsoft.com
- 2Navigate to Settings → Org Settings → Organization Profile
- 3Click "Custom Themes" (or "Add Theme" for group-specific variants)
- 4Upload your logos using the dimensions above
- 5Set your primary brand color via hex code
- 6Upload a sign-in background or set a color
- 7Preview across the suite before saving
- 8Save — changes propagate within minutes
Microsoft 365 allows multiple themes assigned to different user groups. Power users or departments can have a distinct visual experience while maintaining org-wide consistency.
Accessibility: The navigation bar color must meet 4.5:1 contrast ratio against white for the text and icons rendered on it. Check with WebAIM before finalizing.
Item 2
Sign-In Page Customization
Note: If your org uses SSO via a third-party identity provider (Okta, Ping, etc.), users may never see this page. Check with your identity team first.
The sign-in page is your first impression. Most organizations leave it completely generic. A few intentional choices here signal care before anyone has even logged in.
What you can configure
- Background image (1920 × 1080px recommended)
- Banner logo above the username field (280 × 60px max)
- Sign-in page text — a short tagline or welcome message
- Username hint text (custom placeholder)
- Self-service password reset link text
- Footer links (privacy policy, help desk, acceptable use)
- Favicon (browser tab icon)
Steps
- 1Go to entra.microsoft.com
- 2Navigate to User Experiences → Company Branding
- 3Click "Configure" or edit the default branding
- 4Upload banner logo and background image
- 5Add sign-in page text (one line works best)
- 6Set favicon
- 7Save — test in a private browser window at your org sign-in URL
The sign-in page text field is small but powerful. "Welcome back. Let's do some good today." or your org's tagline sets the tone before anyone clicks anything.
Accessibility: If using a background image, ensure sufficient contrast between the sign-in form text and the visible background. Microsoft adds a frosted overlay automatically, but test it visually.
Item 3
SharePoint Home Site — Your Digital Front Door
Your SharePoint home site is the intranet landing page for your entire organization. It is the single highest-value canvas in M365 for communicating culture, mission, and belonging.
What you can configure
- Site logo and title
- Navigation structure and labeling
- Header layout and background (image, color, or gradient)
- Hero web part (large featured image/content area)
- Quick links, news feed, events calendar, people directory
- Footer with org links
Steps
- 1Go to your SharePoint Admin Center
- 2Settings → Home Site → designate your hub site as home
- 3Edit the site via gear icon → Edit
- 4Customize header: Site Settings → Change the Look → Header
- 5Set site logo, header layout, and background
- 6Add and configure web parts via the page canvas
- 7Publish
Lead with mission, not org chart. Name navigation items the way your team talks, not the way IT categorizes. Keep the homepage to 4–5 sections maximum. Use your brand photography — stock photos signal "generic" faster than a default template.
Accessibility: Ensure text overlaid on hero images meets 4.5:1 contrast. Use a dark overlay on light photography or vice versa. Never put white text directly on a light image without a background scrim.
Item 4
Microsoft Teams — Org Branding & Structure
Teams is where most of your people spend most of their day. Structure, naming, and visual organization send constant signals about organizational culture.
What you can configure
- Custom meeting backgrounds (upload branded backgrounds org-wide)
- Together Mode scenes (custom virtual environments)
- Meeting policies (control what backgrounds users can set)
- Team names, descriptions, and pictures
- Channel names, descriptions, order, and pinning
- Tab names and pinned apps per channel
Emoji in channel names: supported in Teams and adds visual personality without any configuration. Use them intentionally — one emoji per channel, aligned to function.
Tier 2 — High Impact
Do These NextOnce the foundation is solid, these layers add depth and consistency across the employee experience.
Item 5
Viva Connections — Branded Dashboard
Viva Connections is the branded employee experience layer that surfaces inside Teams. It is the closest M365 equivalent to a Salesforce custom homepage — and it is enormously underutilized.
What you can configure
- Dashboard name (appears as the app name in Teams)
- Dashboard logo and icon
- Dashboard cards (quick actions, news, announcements, resources)
- Viva Connections feed (sourced from SharePoint news)
- Resources tab (curated links, tools, and documents)
Steps
- 1Go to your SharePoint home site
- 2Settings → Manage Viva Connections
- 3Enable Viva Connections and configure the dashboard
- 4Add cards via the dashboard editor
- 5Deploy to Teams via Teams Admin Center as a pinned app
Pin it. Go to Teams Admin Center → Teams Apps → Setup Policies → pin Viva Connections for all users. If it's buried in the app drawer, nobody will use it.
Item 6
Viva Engage — Community Branding
Viva Engage is your org's social network layer. If you use it, branding it transforms a generic feed into a recognizable community space.
What you can configure
- Network name and logo
- Cover image for the Engage home feed (1200 × 200px)
- Community cover images (one per community)
- Leadership Corner setup and branding
- Story highlights and featured content
- Home feed curation
Leadership Corner is one of the most underused features in Viva Engage. Configure it with your leaders' profiles and encourage regular posts. When leadership is visibly present in the digital community, belonging increases.
Item 7
SharePoint Sites — Department & Team Sites
Every SharePoint site in your tenant can be independently branded. Department sites, team sites, project sites — all can carry your org's visual identity while maintaining their own personality.
What you can configure
- Theme (Microsoft themes or custom theme)
- Header layout and background image
- Navigation labels and structure
- Site logo and title
- Footer content and links
- Page layouts and web part configuration
Steps
- 1Use the SharePoint Theme Generator to create your theme JSON from your hex codes
- 2Upload via SharePoint Admin Center → Theme Gallery (PowerShell for tenant-wide)
- 3Or apply per-site: Settings → Change the Look → Theme → select your custom theme
The SharePoint Theme Generator (fluentuipr.z22.web.core.windows.net) builds a full theme palette from your primary hex code — you don't need to define every color manually.
Item 8
Email Signatures — Branded Outbound Communications
Every email your team sends is a brand touchpoint. Inconsistent signatures are one of the most common and most visible brand failures in M365 organizations.
What you can configure
- Exchange transport rules — text-based disclaimer appended to all outbound mail (low effort)
- Outlook signature templates — rich HTML, users apply manually (medium effort)
- Third-party tools (Exclaimer, CodeTwo, Crossware) — fully branded, centrally managed (higher cost)
- Name, title, pronouns (optional)
- Logo at 200 × 80px, under 50KB
- Mission tagline (optional but powerful)
Accessibility: HTML email signatures should use real text for name and title, not text embedded in an image. Screen readers cannot read image-based text.
Tier 3 — Refinement Layer
Polish & ExtendThe finishing touches that elevate a good tenant into a truly intentional digital workplace.
Item 9
Branded Microsoft Office Templates
When your team opens Word, PowerPoint, or Excel — what do they see? Org-level templates ensure every new document starts on-brand.
What you can configure
- Word: letterhead template with logo, colors, and font defaults
- PowerPoint: branded slide deck with master slides matching your identity
- Excel: branded workbook with logo header and color palette pre-loaded
Steps
- 1Create your templates using your brand guidelines
- 2Save to a SharePoint document library designated as your org template library
- 3Go to M365 Admin Center → Settings → Org Settings → Office on the web → Organization templates
- 4Point to your SharePoint library
- 5Templates now appear under "New" in Word, Excel, and PowerPoint
Item 10
Teams Meeting Backgrounds
Branded meeting backgrounds are visible to everyone in every video call. A simple branded background is one of the easiest high-visibility wins on this list.
What you can configure
- Gradient or solid color field with a small logo (keep it simple)
- Tagline or mission statement in small text at the bottom
- Light version and dark version
- Export at 1920 × 1080px
Steps
- 1Teams Admin Center → Meeting Policies → select your policy
- 2Under "Content Sharing" → "Organizational background images"
- 3Upload your branded backgrounds
- 4They will appear as options for all users in that policy
Keep backgrounds simple — a gradient or solid color with a small logo beats a busy design every time.
Item 11
Power Apps & Power Pages — Branded Internal Tools
If your organization uses Power Apps for internal tools or Power Pages for portals, each one is a brand touchpoint. A generic canvas app signals the tool was built quickly, not thoughtfully.
What you can configure
- App name and icon (192 × 192px PNG)
- App splash screen and loading image
- Theme colors applied to all controls
- Navigation structure and labeling
- Power Pages: full CSS and HTML control over visual design
Item 12
Microsoft Search — Branded Search Experience
Microsoft Search surfaces in Teams, SharePoint, Outlook, and the M365 portal. Most orgs don't know it's configurable.
What you can configure
- Acronyms — define org-specific terms so staff don't have to guess
- Bookmarks — pin your most important internal resources to the top of results
- Q&A — curated answers for common questions
- Floor plans (for multi-site orgs)
- Locations (office addresses and maps)
Bookmarks are powerful. If "submit a help desk ticket" always surfaces first when someone searches "IT help," you've made the experience dramatically more intentional. Start with your 10 most-searched internal topics.
Item 13
Copilot Studio — Branded AI Assistants
If your org is deploying AI assistants via Copilot Studio, the name, personality, and visual identity of those bots are brand decisions — not just technical ones.
What you can configure
- Give your bot a name that fits your culture (not "Bot" or "Assistant")
- Write a personality and tone guide for responses
- Set a custom icon (192 × 192px PNG)
- Deploy with a welcome message that sounds like your organization
- Surface in Teams with a branded app icon
This is where the flywheel closes. If your team is already living in a branded, mission-aligned M365 environment — and they trust the platform because it feels like theirs — AI adoption follows naturally.
The Beyond Contoso Pledge
Open your M365 tenant right now. Does it look like your organization — or does it look like Contoso?
Pick one thing from Tier 1 and do it this week. Just one. The org branding in Admin Center takes less than 30 minutes and touches every surface in your tenant. Start there.
Your people didn't sign up to work in a demo environment. Give them a digital home that looks like the place they actually chose to work.
Quick Reference Checklist
Click to check off items as you go.
Tier 1 — Do First
Tier 2 — Do Next
Tier 3 — Refinement
Additional Resources
About This Series
Powered by Intentional Design explores how intentional platform design drives mission alignment, user adoption, and belonging at work.
Beyond Contoso is the M365 companion session — a talk about what happens when a Technology Leader decides to stop treating M365 as a utility and start treating it as a canvas.
Pete Schweiss — Director of Technology Services
Licensed CC BY 4.0 · Last updated 2026 · Contributions welcome