How are people handling local file and print servers with Entra-only devices?

The file server is probably the trickier part. A traditional on-premises file server often expects Active Directory for authentication, so Entra-joined devices don't automatically make the existing setup work without a domain.

If the files can move, look at SharePoint and OneDrive for ordinary document collaboration. Azure Files is another option, but it's cloud storage and the cost model is different from running a local server. Check the authentication requirements for your chosen configuration rather than assuming every existing file share will transfer unchanged.

For printing, look at Universal Print, PaperCut, or PrinterLogic. They offer alternatives to keeping a conventional print server, though you'll need to compare features and costs against your printer fleet and deployment requirements.

If there are only a few printers and budget is tight, you could package the drivers for deployment through Intune and use PowerShell to set up the printers on devices. It's more hands-on than a dedicated print service, but it may be enough for a small setup.

If the storage really has to stay on site, check what authentication the server or NAS actually supports. An LDAP bridge that queries Entra ID is one possible workaround for a system that expects LDAP, although it adds another component to maintain and may not provide seamless sign-in.

Entra Domain Services is another route to investigate when directory services are needed. Either way, test the specific client and server combination before retiring the existing domain.

Before replacing every printer, check how much printing is still needed. Some paper workflows may be removable altogether, which could shrink the fleet and make whatever print solution you choose simpler.