Intune – How to add / deploy printers with Intune

Adding printers to Intune seems like it would be a simple and effortless process. And thankfully, it is. In this blog post i will walk you through how to add / deploy printers to devices through Intune.

In this scenario, we will create a new device configuration profile, of the type “Device Restrictions”

  1. Navigate to and click on Intune.
  2. Click on Device Configuration

  1. Click on Profiles and then click on “Create Profile”
  2. Give the profile a name.
  3. For the platform select – Windows 10 and later
  4. Profile Type – Select “Device Restrictions”
  5. From the menu that opens(if it doesn’t open, click on settings) scroll down and click on “Printer”
  6. Where it says “Printer DNS name” enter the name of the printer that you wish to add in the format of \\Servername\Printername
    • An example of this can be seen in the image below.

Once the above profile has been completed, click ok out of the menus and save your profile.

Now all thats required is for you to assign the profile to your target group.

Once the profile has been assigned and devices have synced with Intune, you will be able to see the printers which have been added through the devices and printers menu in control panel.

Should you set a default printer through Intune?

Due to the way that many offices function, choosing whether to have a printer set as default via Intune is something that should be considered carefully.

If you choose to have a default printer set via intune, its important to consider that, if a user changes their default printer to something of their preference, then this setting will not stick.

And as soon as the Intune policy syncs again, it will be reverted to whatever is set in the policy.

Thank you for reading.

9 Replies to “Intune – How to add / deploy printers with Intune”

  1. This works if a group of users has 1 printer they share otherwise you have to create a bunch of printer policies for each user, correct?

    1. Hi Dbdmora,

      It really comes down to how your organisation uses printers.

      If for example, you have one office, and the printers are all named in a way that users can identify which printer is which, then having all the printers configured within the single profile should be no issue.

      However, if you have multiple offices, then i would opt to create a profile for each office with its relevant printers.

    1. Depends on your scenario, deploy to a user if you want it to follow the user on whatever device they log into. Otherwise if you only want the printers available on certain devices, deploy to a device group.

  2. Does this solution works for On-Prem printer as well?

    I have tried assigning this printer policy to a device, but it does not installs the printer.

    I have created a dummy printer and tested it manually – by simply running path\\ServerDNSName\PrinterName in RUN, I see it is successfully installing the driver and getting connected but if i tried the same with the policy it does not work.

    I see the report says successfully deployed. I also see the GUID in registry created with Printer Path “\\ServerDNSName\PrinterName”. but unfortunately printer does not gets installed.

    Do you know whether this policy is supported for onprem printers which are joined to Onprem AD?

  3. I am unable to get it to work. It says it is applied, however it is not showing up. I tried users and devices as target groups. There are no error show, and no printers.

  4. For anyone having trouble getting this working, you can’t use it with a printer share name but instead point directly to a printer DNS name.
    – create static A record in onsite DNS server (
    – set Printer value on intune to
    – The printer will be deployed using the DNS name from the printer

    1. I have tried this, Still without success. The Config profile says ‘Succeeded’ but no printer. I have tired the format you suggested “” and “\\” I have tried the ‘share’ as well. “\\servernamefqdn\printershare” . If I have intune run a PS-script or connect directly from the machine no issue. but if I do it the way I’m supposed to and the way this is designed… No Luck. What am I missing. Is there a logfile that will let me know the issue or error, and where is it located? (I fear, since it says ‘succeeded’, the answer is ‘no’)

Leave a Reply

Your email address will not be published. Required fields are marked *