> For the complete documentation index, see [llms.txt](https://docs.realmjoin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.realmjoin.com/automation/runbooks/runbook-references/org/general/export-cloudpc-usage_scheduled.md).

# Export Cloudpc Usage Scheduled

Write daily Windows 365 usage data to an Azure table

{% hint style="info" %}
This is a scheduled runbook. It is designed to run on a recurring schedule rather than being triggered for a single object. See [Scheduling](/automation/runbooks/scheduling.md) for details on how to configure runbook schedules.
{% endhint %}

### Description

Collects how the Windows 365 Cloud PCs were used, based on the remote connection reports of the chosen number of past days. The figures are written to an Azure Table so they can be tracked over time. The table is created when missing, and records for the same day are updated rather than duplicated.

### Location

Organization → General → Export Cloudpc Usage (Scheduled)

**Full Runbook name**

rjgit-org\_general\_export-cloudpc-usage\_scheduled

### Details

| Property         | Value                                                               |
| ---------------- | ------------------------------------------------------------------- |
| Version          | 1.0.1                                                               |
| Required modules | <p>RealmJoin.RunbookHelper (>= 0.8.10)<br>Az.Storage (>= 9.7.2)</p> |
| Schedulable      | yes                                                                 |

### Permissions

#### Application permissions

* **Type**: Microsoft Graph
  * CloudPC.Read.All
    * *Lists all Cloud PCs and pulls their remote connection historical reports*
  * Organization.Read.All
    * *Reads /organization to use the tenant id as storage table partition key*

#### Permission notes

Azure IaaS: `Contributor` role on the Azure Storage Account used for storing CloudPC usage data

### Parameters

#### Table

Table in the storage account the usage data is written to. Created when it does not exist yet.

| Property            | Value          |
| ------------------- | -------------- |
| Required            | false          |
| Default Value       | CloudPCUsageV2 |
| Type                | String         |
| Portal display name | Table name     |

#### ResourceGroupName

Resource group that holds the storage account.

| Property            | Value          |
| ------------------- | -------------- |
| Required            | true           |
| Default Value       |                |
| Type                | String         |
| Portal display name | Resource group |

#### StorageAccountName

Storage account that holds the table.

| Property            | Value           |
| ------------------- | --------------- |
| Required            | true            |
| Default Value       |                 |
| Type                | String          |
| Portal display name | Storage account |

#### Days

Usage of the past this many days is collected; days already in the table are updated, not added again.

| Property            | Value             |
| ------------------- | ----------------- |
| Required            | false             |
| Default Value       | 2                 |
| Type                | Int32             |
| Portal display name | Days to look back |

[Back to Runbook Reference overview](/automation/runbooks/runbook-references.md)


---

# 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.realmjoin.com/automation/runbooks/runbook-references/org/general/export-cloudpc-usage_scheduled.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.