> For the complete documentation index, see [llms.txt](https://developer.ultimo.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.ultimo.net/connectors/universal-print.md).

# Universal Print

Introduction

<figure><img src="https://4033746893-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZmRVbbu75Ds8MiWx_F%2Fuploads%2FZbjGiav39m1EIlhNo7Da%2Fimage.png?alt=media&amp;token=379e4ee9-6722-4609-ae94-a72d81f1e05e" alt=""><figcaption></figcaption></figure>

Universal Print is a modern print solution that organizations can use to manage their print infrastructure through cloud services from Microsoft. Universal Print runs entirely on Microsoft Azure. When it's deployed with Universal Print–compatible printers, it doesn't require any on-premises infrastructure. Universal Print can be deployed with non-compatible printers by using Universal Print connector software. To learn more about Universal Print, click [here](https://learn.microsoft.com/en-us/universal-print/fundamentals/universal-print-whatis).

Ultimo offers integration with Universal Print as an addition to our 'direct printing' functionality, making it possible to send print jobs from Ultimo directly to a specific printer.

Note: Universal Print was released as a product several years ago, but is still evolving to meet the needs of customers. To read more about current prerequisites and limitations, go to the next page.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.ultimo.net/connectors/universal-print.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
