Your Brand. Your Platform. How MSPs White-Label Atlas AVD

By David, 2026-09-07

For MSPs, the technology behind a service matters. But to your customers, your brand matters too.

When an MSP delivers Azure Virtual Desktop, endpoint management, automation, documentation and other IT services, the customer experience shouldn't switch to another vendor's branding every time a user opens a portal. When your customers sign in to their virtual desktops, they should see your name, not your software vendor's.

Atlas AVD is built for that. The MSP Capabilities upgrade includes white-label branding, and you configure all of it yourself from a single Branding tab in Atlas Command. There is no ticket to open with us, no custom build, and nothing to redeploy. Changes apply as soon as you save.

This article covers two things: what white-labeling gives you and why it matters, and then a step-by-step setup guide, with real screenshots of each step.

Make Atlas AVD look like your platform

Upload your company logo and configure the visual identity of the platform, so customers see a familiar experience when they sign in. Branding includes:

• Your company name in place of "Atlas AVD", in the sidebar, page titles, emails and reports
• Your logo, with separate versions for light and dark mode
• Your brand colors, applied to buttons, navigation and highlights across the app
• A custom favicon in the browser tab
• A branded sign-in page on your own domain, in your own words
• Your support details: help desk email, phone, hours, website, terms and privacy links
• Email from your domain, and PDF reports with your logo, colors and footer
• Your own sidebar labels, so the console uses the vocabulary in your contracts
• No Atlas AVD badge, if you prefer to hide the "Powered by Atlas AVD" mark

It also reaches the places that are easy to forget: the User Portal your customers' end users open to find their desktops uses your logo and primary color, and the Atlas Reach agent on customer devices uses your company name in its consent prompt, session banner, tray icon and restart messages, so the person whose screen is being shared sees who is helping them: you.

The goal is simple: your customers should feel like they're using your platform.

Present Atlas capabilities as your services

White-labeling goes beyond changing a logo.

Atlas AVD contains a growing collection of integrated IT operations capabilities, and MSPs may not want every customer touchpoint to lead with an Atlas product name. Your company name replaces "Atlas" in the product names customers read: if you are Contoso, a Vault share arrives from "Contoso Vault", and a remote-support notice comes from "Contoso Reach". And you can rename the main sidebar sections to match your runbooks.

What you sell is up to you. The capabilities underneath stay the same, but in your service catalog, your quotes and your contracts, you name them around your brand. For example, an MSP called Contoso could offer:

That lets you package Atlas capabilities into branded service tiers, instead of reselling individual third-party products:

• Managed Workspace: Azure Virtual Desktop management, autoscaling, image management, monitoring and user access, with a branded User Portal for your customers' staff.
• Managed Endpoint: remote support, endpoint management, scripting, patching and automation, powered by Atlas Reach, plus IT documentation with Atlas Vault.
• Managed Security: DNS filtering with Atlas Resolve, security hardening baselines, vulnerability visibility, auditing and compliance reporting.
• Managed Microsoft 365: email signature management with Atlas Ink and Microsoft 365 administration: users, licenses, mail, Teams and more, in the same console as your desktops.

You control how these services are named, packaged, presented and ultimately sold to your customers.

Stop advertising your vendors

Traditional MSP technology stacks can expose customers to dozens of vendor names. One portal handles remote management. Another handles documentation. Another manages email signatures. Another manages Azure Virtual Desktop. Another handles DNS filtering. Each login becomes another opportunity for the customer to see the underlying vendor, rather than the MSP delivering and supporting the service.

Atlas AVD takes a different approach. By bringing these capabilities together in one platform and letting you white-label the experience, you can build your technology platform around your own brand. Your customer hired you to manage their environment. Your platform should reinforce that relationship.

Set it once, for every customer

For MSPs managing many organizations, branding shouldn't require rebuilding the configuration for every tenant.

You set your branding once, at the MSP account level, and every customer tenant you manage inherits it. That includes administrators you scope to a single customer's tenant, and the scheduled reports that go out to each customer. Onboarding a new customer doesn't mean another round of logo uploads and color picking: they see your brand from their first sign-in.

Where customers genuinely need to differ, it's in how their environments are run, not in whose name is on the door. Policies, schedules and settings can be set per tenant (see Per-Tenant Policy Enforcement), while the brand stays consistently yours.

Setting it up: before you start

The rest of this article walks through the whole setup in the order most MSPs do it. To keep it concrete we brand a fictional MSP, Summit Ridge IT, from start to finish.

About the screenshots: every image in this article is the real Atlas AVD application running in demo mode, branded as Summit Ridge IT. The company, its domain and its phone number are made up. Everything else is exactly what you will see in your own instance.

You need three things:

• MSP Capabilities. White-label branding comes with MSP Capabilities, the optional upgrade to Atlas AVD at $50 per licensed tenant a month, and the 30-day trial includes it. Atlas AVD on its own does not include it. (See MSP pricing.)
• An administrator account on your MSP account. The Branding tab is admin-only.
• Your brand assets: a logo for light backgrounds, a logo for dark backgrounds, a square favicon, and optionally a background image for the sign-in page. You will also need access to your DNS provider for the custom-domain and email steps.

Then open Atlas Command → Branding.

The page has three parts:

• Branding Settings on the left: a six-step checklist. Each step shows whether it is Configured, Pending (waiting on DNS) or Not configured, so you always know what your customers still see as an Atlas default.
• Preview on the right, with tabs for the App Shell, Sign-In, Emails and Reports. It updates as you type, before you save.
• Advanced Settings further down, for the sign-in page, sidebar labels, custom CSS and the Atlas AVD badge. These are optional.

Nothing on this page changes how desktops, host pools or sessions behave. It only changes what your customers see. Each step is optional on its own, and a bar at the bottom of the page counts your unsaved changes until you choose Save Settings.

Step 1: Company name

Company Display Name (up to 80 characters) replaces "Atlas AVD" in the sidebar, page titles, outbound emails and report headers. It also reaches your customers' devices: the Atlas Reach agent uses it in its consent prompt, session banner, tray icon and restart messages (the first 64 characters).

Slug is a short, unique ID for your MSP that appears in links and report file names. Use lowercase letters, numbers and hyphens, 2 to 64 characters.

Step 2: Logos and favicon

Upload four images:

Logos larger than 2000 × 2000 px and backgrounds larger than 4000 × 4000 px are resized automatically.

Tips that save a second round:

• Crop your logo tightly. Transparent padding around a wordmark makes it render small in the sidebar.
• Give the dark-mode logo light text. The sidebar is dark, so this is the logo it uses.
• Pick a light, low-detail background image. The sign-in page lays a tint over the image so the text stays readable. A soft image works in both light and dark mode; a busy or very dark one goes muddy in light mode.

Step 3: Brand colors

Three colors drive the whole interface:

• Primary is the main action color: buttons and the active navigation item.
• Secondary is the supporting color.
• Accent highlights things, such as the active-item badge in the preview.

Type a hex value or use the color picker. The navigation-bar preview updates as you type, and the field warns you if a color falls below the WCAG AA contrast ratio of 4.5:1, so you can catch an unreadable button before a customer does.

Step 4: Custom domain

This is the step that makes the platform feel like yours. Customers reach Atlas at your own hostname, such as desktop.summitridgeit.com, instead of your Atlas address.

1. Enter the hostname only, with no https://, and choose Save Domain. The domain saves on its own, separately from the rest of the page.
2. Atlas shows two DNS records to add at your DNS provider:
   • a CNAME that points your hostname at your Atlas instance, and
   • a TXT record that proves the domain belongs to your account, so no other account can claim it.
3. Wait for DNS to propagate. That usually takes a few minutes and occasionally up to an hour.
4. Come back and choose Revalidate. When the check passes, the status changes from Pending Verification to Verified.

Two things to know:

• TLS is provisioned at the infrastructure level, for example Azure Front Door, Cloudflare or your load balancer, so plan your certificate alongside the DNS change.
• A custom domain is unique across all Atlas AVD instances. Only hostnames registered and verified here are trusted.

Your branded sign-in page (covered below) only appears on the verified custom domain, so it is worth doing this step early.

Step 5: Support and legal links

These fields tell customers where to go for help. They are printed in outbound emails, on PDF reports and on the sign-in page:

• Support Email, Support Phone and Support URL
• Support Hours, printed alongside your support details in email footers and reports
• Terms of Service URL and Privacy Policy URL
• Documentation URL, which replaces the Atlas AVD documentation links inside the app (setup guides, device enrollment help) with your own site. It must be HTTPS.

Step 6: Email sender and report footer

Set a From Name and From Address for every email Atlas sends to your customers, such as alerts and scheduled reports. Save the page, and Atlas issues a TXT record that proves you own the sender's domain. Add it at your DNS provider and choose Verify now.

Until the record is found, mail keeps going out from the Atlas AVD default address. That way a typo in a DNS record never means lost alerts. For good deliverability, also publish SPF, DKIM and DMARC records for the domain with the mail provider configured under Settings → Email.

The Report Footer (up to 300 characters) is printed at the bottom of every PDF report. Preview Email Template and Preview Report Branding show exactly how both will look with your saved settings.

Check your logo in the previews. Email and PDF report headers draw your logo on a band of your primary color. Open both previews to make sure your logo reads well against it before you go live.

Your branded sign-in page

With a verified custom domain, you can rewrite the page your customers see before they sign in. Open Advanced Settings → Sign-in page.

You control:

• Text: a small uppercase tagline, the headline (press Enter for a line break) and the body copy.
• Feature cards: add, remove and reorder cards, each with a title, a short description and an icon.
• Benefit chips: short one-line promises such as "24/7 service desk".
• Layout: drag the three sections into any order, or hide any of them.

A live preview, in light or dark mode, sits next to the editor. Reset to Atlas defaults starts over. Here is the finished result, on Summit Ridge IT's own domain:

The logo, background image and colors come from steps 2 and 3, and the footer links come from step 5. Customers who arrive at any other address keep seeing the default sign-in page.

Optional fine-tuning

The rest of Advanced Settings is safe to leave alone, but MSPs often use these:

Sidebar labels

Rename the main sidebar sections (Dashboard, Host Pools, Imaging, Reports, Resources and Settings) to match the vocabulary in your contracts and runbooks. Summit Ridge calls host pools "Desktop Pools" and the imaging area "Golden Images". Leave a field blank to keep the default name. A rename applies in every language the app is shown in.

Custom CSS

For small adjustments that the color and logo settings can't make, you can inject your own CSS into the app shell. It is sanitized on the server: patterns such as javascript:, expression() and event handlers are rejected. Keep it small. Everything above covers what most MSPs need.

Vault share notification

If you use Atlas Vault to share credentials or documents with customers, you can rewrite the email the recipient gets, so it comes from your service desk in your words.

Atlas AVD attribution

By default a small "Powered by Atlas AVD" badge appears to your customers. Turn on Hide Atlas AVD branding to remove it from the sidebar, outbound emails and PDF reports.

The result

Save, and the branding applies right away for everyone on your account, including admins scoped to your customers' tenants. The Summit Ridge IT dashboard at the top of this article is the finished result: the MSP's logo, its teal colors and its own sidebar vocabulary, on the same Atlas AVD underneath.

Your brand also shows up in places that are easy to forget:

• The End User Self-Service Portal uses your logo and primary color.
• Customer devices running Atlas Reach show your company name in the agent's prompts and banners.
• Emails and PDF reports carry your name, logo, colors, support details and footer.

Good to know

• One brand per MSP account. Every customer tenant you manage inherits your branding. There is no per-customer override.
• The master switch. Under Instance controls, turning off Atlas Command makes the app, emails and reports fall back to Atlas AVD defaults and stops your custom domain resolving to your instance. Nothing is deleted, and turning it back on restores everything exactly as it was.
• An audit trail. The Audit Trail section at the bottom of the page records who changed the branding, what they changed, and when.
• If your MSP license lapses. Your branding stays in place through a grace period, then the app falls back to Atlas AVD defaults. Your settings are kept, so renewing brings the brand straight back.

Quick checklist

For a field-by-field reference, see White-Label Branding in the support docs. To see what MSP Capabilities adds, see MSP pricing and pricing.

Atlas provides the technology. Your customers see your brand.