cloud print setup guide

Cloud Print Setup for Small Teams: Migrate and Test Before Deploying

IT administrator tests cloud printing beside office printer

Pick Universal Print if you run Microsoft 365, AirPrint for Apple-only fleets, and CUPS or a third-party cloud print service for Chromebook and mixed-OS offices. Google Cloud Print was deprecated and is no longer supported, so any leftover setup needs migrating. Jump to the Universal Print steps first if your users sign in with Microsoft accounts.

TL;DR:

Before setup, update printer firmware, confirm eligible licenses and network access, and allow outbound traffic to Microsoft Entra ID and Microsoft Graph.

Register Universal Print ready printers directly; legacy models need an always available Windows connector, then share with users, deploy printers, and print a test page.

AirPrint needs no drivers on a shared network; before replacing an unsupported printer, check whether its manufacturer documents an IPP resource path.

When you host CUPS yourself, expose IPP only through a VPN or tunnel, and plan to manage patches, monitoring, and server uptime.

Pilot one printer from sign in through a printed page, then investigate stalled jobs through portal status, connector logs, and spooler records before expanding.

How do you choose an approach and check prerequisites?
How do you set up Microsoft Universal Print step by step?
How do you set up AirPrint and CUPS?
How do third-party and self-hosted cloud printing work?
What should you check first when cloud printing fails?
How does a print job travel from cloud to paper?
What practical tips do we give small IT teams?
Need a hand with your print setup?
FAQ
Sources

How do you choose an approach and check prerequisites?

Match the approach to the devices your people actually use, then confirm the basics before touching a single setting.

Microsoft 365 tenant: Universal Print is the natural fit and replaces many on-premises Windows print servers.
Apple-only devices: AirPrint needs no drivers when the device and printer share a network.
ChromeOS or mixed fleets: CUPS over IPP, or a third-party cloud print service, covers the gaps.
Tight control over data paths: a self-hosted CUPS server behind a VPN keeps traffic in your hands.

Before any install, update printer firmware, confirm the printer stays powered and reachable, and check DNS and proxy behavior. Verify that the OS versions and endpoint access Microsoft lists in its Universal Print setup guide are in place. Universal Print entitlement comes with several Microsoft subscriptions, and Microsoft's access page lists which ones.

Also separate your printers into two groups: Universal Print ready models that register directly, and legacy models that need a connector on a Windows host. Finally, ask your firewall owner to allow outbound access to the Microsoft Entra ID and Microsoft Graph endpoints. Our printer fleet security guide covers hardening those devices during maintenance. For broader network hygiene, this overview of cloud security best practices for SMBs is a useful companion.

How do you set up Microsoft Universal Print step by step?

Work through these in order, and stop to validate after registration.

Confirm that your users and admins hold eligible licenses, and assign a Printer Administrator role to whoever will register devices.
If the printer is Universal Print ready, update its firmware and register it directly from the Universal Print portal.
If it is not, install the Universal Print connector on a Windows host that stays online and can reach the required endpoints.
Register each printer through the connector, then review its settings.
Create a printer share and limit access to the right users or groups.
Deploy the printer through Intune, or let users add it themselves from Printers & scanners.
Print a test page, then check the printer state and "Is accepting jobs" status in the portal.

If a job never appears, collect connector and spooler logs, as described in Microsoft's print error debugging guidance.

Pro Tip: Run the connector on a dedicated, patched virtual machine rather than someone's desktop, so a reboot or sleep setting never silently takes your printers offline.

If you are rolling out devices alongside printers, our Windows Autopilot runbook shows a pilot approach that pairs well with Intune printer deployment.

How do you set up AirPrint and CUPS?

These two paths cover Apple devices and ChromeOS or Linux endpoints.

AirPrint basics: Connect the printer to Wi-Fi, confirm it supports AirPrint, and keep the device and printer on the same network, as Apple's AirPrint documentation describes.
Managed Apple fleets: Push an AirPrint payload through your MDM (Intune, Jamf, or Apple Configurator) so iPhones, iPads, and Macs get printers preconfigured. This AirPrint guide explains how profiles spare users from discovering printers manually.
CUPS for ChromeOS and Linux: Add the printer to your CUPS server, expose it over IPP, then use the Google Admin console so printers appear for users without extra setup. Google's page on printing from a ChromeOS device explains how to limit printers to organizational units.
Which to prefer: Choose AirPrint when everyone uses Apple hardware. Choose CUPS when ChromeOS or mixed operating systems are in play.

If a printer lacks AirPrint support, adding an IPP resource path often bridges the gap, so check the manufacturer's documentation before replacing hardware.

How do third-party and self-hosted cloud printing work?

Most third-party cloud print services follow one pattern: install the provider's agent or app, register the printer with the service, and confirm the hub or gateway stays online. Google's migration page points administrators toward platform-supported options and print partners for this reason.

Third-party service: Often the easiest route for multi-site offices or mixed operating systems, since the provider handles discovery and routing.
Self-hosted CUPS: Expose IPP only through a VPN or tunnel, never directly to the internet. This remote work server setup guide explains why leaving remote access ports open is risky.
Always-online connector host: A small server that stays powered and patched keeps remote printing reliable.
Trade-offs: Self-hosting gives you tighter control over data, but you own the patching, monitoring, and uptime.

Pro Tip: Whichever route you pick, write down where print data travels and who maintains each hop. That note saves time the first time a remote user cannot print.

What should you check first when cloud printing fails?

Work from the cloud down to the desk, and change one thing at a time.

Open the Universal Print portal and look for the job. Note whether it sits in Pending or Paused.
Confirm the printer is accepting jobs and identify which connector serves it.
On the connector host, verify the connector service is running, review event logs, and confirm internet and proxy access. Check that the Print Spooler service is healthy.
Print a test page directly from the connector host to separate driver or hardware faults from cloud faults.
Confirm the user has an eligible license and access to the printer share.
On the client, check internet access, Microsoft Entra ID sign-in, OS version minimums, and any firewall blocking outbound connections.

Firewall rules that block Microsoft Entra ID and Microsoft Graph endpoints are a common failure point in Universal Print troubleshooting, according to Microsoft's troubleshooting documentation. Check network rules before you suspect the printer.

How does a print job travel from cloud to paper?

Knowing the route tells you which log to open. Per Microsoft's print job journey, the cloud validates and stores the job, notifies the printer or connector, which downloads it. A connector then hands it to the local spooler and driver, and the printer processes the payload.

A job stuck in Pending usually points to the link between cloud and connector rather than a broken printer. That is why the portal and connector come first in any investigation. When you need evidence, collect the Universal Print Jobs page, the connector event log, Windows spooler logs, and a network trace from the connector host. Matching a symptom to a stage narrows a long investigation to one machine.

What practical tips do we give small IT teams?

The best rollout starts small. Pilot one test printer and prove the full flow, from sign-in to paper, before touching the rest. Inventory every printer and mark which are Universal Print ready and which depend on a connector, because the second group carries your real risk. Patch firmware and connector hosts on a schedule, and watch job volumes against your license entitlements so capacity or billing never surprises you. Our take on proactive IT management applies directly: monitor before something breaks, not after.

— Nicholas

Need a hand with your print setup?

Cloud printing touches licensing, networking, and endpoint management at once, and we handle all three for small businesses. Our Oklahoma City metro team can validate your Microsoft 365 licensing and plan the connector, firewall, and deployment steps in plain language, with a prompt response and no long-term contract. If printing is one of several loose ends, our Microsoft 365 Support covers the tenant side, and you can start with a free 10-minute readiness audit to see where your setup stands today.

FAQ

What is cloud print?

Cloud print lets you send documents to a printer over the internet instead of through a local cable or office network. Modern versions are usually cloud-managed or cloud-discovery services such as Universal Print, which Microsoft describes as a cloud-based print management solution for Microsoft 365 customers.

Is Google Cloud Print still available?

No. Google Cloud Print was deprecated in January 2021 and is no longer supported. Administrators should move to CUPS for ChromeOS, AirPrint for Apple, Universal Print, or a third-party print partner.

How do I get my devices to recognize a cloud printer?

Start with registration and sharing. For Universal Print, register the printer, share it, and make sure the user has access, then add it from Printers & scanners. For Apple devices, keep the device and printer on the same network or push the printer through MDM.

How do I set up AirPrint?

Connect the printer to the same Wi-Fi network as the Apple device and confirm the printer supports AirPrint. The device then discovers it without drivers, as Apple's documentation explains. In managed fleets, push an AirPrint payload through your MDM instead.

Sources

Want help putting this into practice?

We'll audit your security, speed, and hardware in under an hour — no commitment, no sales pitch. Just a clear roadmap of what to fix and why.

Schedule Your Free Assessment

Cloud Print Setup for Small Teams: Migrate and Test Before Deploying