> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/extensions/microsoft-cloud-solution-provider/additional-resources/faqs/what-is-offer-attestation.md).

# What is offer attestation?

Offer attestation is a verification process that requires clients purchasing through the Marketplace to acknowledge specific terms and conditions before placing an order.

Currently, the only offer that requires attestation is **Windows 365 Business with Windows Hybrid Benefit**. When ordering it, you must acknowledge that each person using the software has a valid copy of Windows 10/11 Pro installed on their primary work device.&#x20;

This verification helps ensure compliance with Microsoft's licensing requirements and must be completed before the order can be placed.

### Acknowledge an offer attestation

When you order an item that falls under the **Hybrid Use** category, the following message appears on the **Items** page:

"By proceeding with this order, I acknowledge that each person using Windows 365 Business with Windows Hybrid Benefit must have a valid copy of Windows 10/11 Pro installed on their primary work device."&#x20;

The attestation message appears for purchase orders and change orders that include items requiring attestation.

<div data-with-frame="true"><figure><img src="https://1674205915-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ5DNbniz33mXCZoO62Rm%2Fuploads%2FWkl4eMirjk5Y9jDWEyP5%2Foffer_attestation.png?alt=media&amp;token=19072aa1-1c8a-41d2-9591-e97c1dd1c017" alt=""><figcaption><p>Offer attestation message during the ordering process.</p></figcaption></figure></div>

By selecting **Next** on the **Items** page, you confirm that you accept the attestation.&#x20;

After you place the order, a PDF is available on the **Attachments** tab of the agreement details and order details pages. The PDF contains the attestation details, including the name of the person who accepted the attestation and the date and time it was confirmed.&#x20;

The following image shows an example:

<div data-with-frame="true"><figure><img src="https://1674205915-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZ5DNbniz33mXCZoO62Rm%2Fuploads%2FH9ezv3C64B2kH1rcxO8m%2Foffer_attestation_orders_tab.png?alt=media&amp;token=7c9d9c4e-827f-49b1-83cd-34941553c897" alt=""><figcaption><p>Use the <strong>Attachments</strong> tab to view the attestation PDF.</p></figcaption></figure></div>

You can also see the attestation details through the [audit trail](/modules-and-features/settings/audit-trail.md).&#x20;


---

# 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://docs.platform.softwareone.com/extensions/microsoft-cloud-solution-provider/additional-resources/faqs/what-is-offer-attestation.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.
