How to mark a print job as completed in universal print with virtual printer

If you are developing a virtual printer, we recommend you to use IPP APIs as per the IPP INFRA specification. You can find more information on OEM Universal Print Device Development Overview - Universal Print | Microsoft Learn.

IPP APIs are required for multiple reasons. Some key ones are:

1. Ensuring you have support for all print options and attributes. IPP APIs are typically more up-to-date compared to Graph APIs when it comes to printer functions. This is because Microsoft is committed to IPP standards from Mopria and PWG.
2. Ability to acknowledge the print job - this locks the print job to be printed by the printer which acknowledged the print job.
3. Ability to update print job status - this is very important as some client behavior depends on the correct print job state
4. Ability to easily integrate with Secure release and Universal Print anywhere (pull print feature coming soon)

Graph APIs are a great fit for:

1. Cloud workflows that can be applied on top of a print job queued in cloud (like implementing user quotas, print policies etc.). Check - https://learn.microsoft.com/en-us/graph/universal-print-webhook-notifications?view=graph-rest-beta#create-subscription-printtask-triggered-jobstarted-event 
2. If your printer is hosted in cloud, then you can use Graph change notifications. These help in notifying about new jobs (ready to be released at printer) instead of IPP notifications. Check https://learn.microsoft.com/en-us/graph/universal-print-webhook-notifications?view=graph-rest-beta#create-subscription-jobfetchable-event 
3. Building custom Print Management