> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/pd-ag/parallels-desktop-enterprise-quick-start-guide/scenario-based-quick-start-blueprints.md).

# Scenario-Based Quick Start Blueprints

Each scenario is presented as a self-contained, step-by-step blueprint complete with architecture diagrams, prerequisites, and execution steps.

{% tabs %}
{% tab title="A: Engineers" %}
**Software Developers & Engineers**

Your developers manage their own toolchains and just need a stock Windows environment to build and test against. This scenario uses **Declarative** deployment — the Portal sources Windows directly, and developers customize the VM themselves after first launch.
{% endtab %}

{% tab title="B: Enterprise" %}
**Knowledge Workers & Enterprise Fleet**

Your fleet needs a standard, managed Windows experience with line-of-business apps delivered centrally. This scenario uses **Declarative** deployment, with Intune handling app delivery after provisioning.
{% endtab %}

{% tab title="C: BYOD" %}
**Contractors & BYOD Users**

Contractors and BYOD users often aren't enrolled in your MDM. This scenario uses **Declarative** deployment and an invitation email, so it doesn't require Mac management.
{% endtab %}

{% tab title="D: App Delivery" %}
**App Delivery / App-Centric (Hidden Windows)**

You want to deliver a single Windows application without exposing the desktop. Single Application Mode requires **VM image** deployment — a `.pvmp` file in an Autodeploy Package, with exactly one VM.
{% endtab %}

{% tab title="E: DevOps" %}
**DevOps & Automated Pipelines**

Build agents need a pinned, reproducible virtual machines (Windows or Linux), and not just whatever gets freshly provisioned at first launch. This scenario uses **VM image** deployment: Declarative always runs first-launch setup and is Windows-only regardless of source, so it doesn't fit Linux fleets or a frozen, versioned baseline.
{% endtab %}
{% endtabs %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.parallels.com/landing/pd-ag/parallels-desktop-enterprise-quick-start-guide/scenario-based-quick-start-blueprints.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.