# Generated Files Storage

By default, files generated by the **code interpreter** in conversations (spreadsheets, documents, charts and images) are **temporary**: they stop being available shortly after they are generated. With **Generated Files Storage**, each organization keeps these files in an **Azure storage account owned by the organization**, in its own tenant and subscription.

{% hint style="info" %}
This feature is **optional**. Without it, the code interpreter keeps working normally, with temporary files.
{% endhint %}

### Overview

| Topic | How it works |
| --- | --- |
| **Who configures it** | Only the organization **Administrator**. |
| **Where files are kept** | In an Azure storage account in **your subscription**. |
| **Isolation** | Each organization uses a **private, exclusive container** for Omni. |
| **Who pays** | **Azure bills your subscription directly**. Omni does not pass on or cap this cost. |
| **Which files** | Only **new** files generated by the code interpreter and delivered in the conversation after activation. |
| **Destination** | One destination per organization. |

**What is not done:**

* There is no migration of history: files generated before activation remain temporary.
* The **Files** library is not moved.
* Intermediate Python files (code scratch files) are not kept.
* Responses in progress at the moment of activation are not imported.

### Before you start

* You must be an **Administrator** in Power Omni.
* In Azure, you need permission to **create resources** and **assign roles** in the chosen subscription or resource group. Setup uses **your** Azure authorization, which Omni does not store.
* The organization project must use **New Foundry**. Projects on **Classic Foundry** can have the account configured, but activation is only possible with New Foundry, and those projects keep temporary files.
* If your tenant requires it, an Azure administrator may need to **grant consent** to the permission requested at sign-in.

### How to set up

Go to **Settings > Storage**. On first use, Omni may also offer this step during initial setup, as an optional step you can skip and resume later.

{% stepper %}
{% step %}
#### Start the setup

On the **Storage** screen, read the introduction and click **Set up storage**. The wizard has four steps: **Type**, **Destination**, **Retention** and **Review**. Cancelling before you confirm **makes no change in Azure**.
{% endstep %}

{% step %}
#### Choose the type

* **Create a storage account**: Omni creates a dedicated account with the recommended protections.
* **Connect an existing storage account**: use an account you already have. Only an exclusive Omni container (and a role restricted to it) is created; the rest of the account **is not changed**, and other applications can keep using the same account.
{% endstep %}

{% step %}
#### Define the destination

When creating a new account, provide:

* **Azure subscription** and **Resource group**;
* **Storage account name**: 3 to 24 characters, lowercase letters and numbers only, unique in Azure;
* **Region**: Omni suggests the region of the Foundry project;
* **Redundancy**: **ZRS** (recommended; copies in three or more zones of the same region) or **LRS** (lower cost; copies in a single datacenter, with a risk of data loss if the datacenter fails). Neither option replicates data to another region.

When connecting an existing account, select it from the list. Omni runs a **read-only check** of compatibility and tells you whether the account can be used. If a notice about an existing container appears, delete the indicated container in Azure and click **Check again**: Omni never reuses an existing container.
{% endstep %}

{% step %}
#### Choose the retention

Choose how long to keep new files: **7, 30, 60, 90, 180 or 365 days**, or **Unlimited**. Omni suggests **90 days** but **does not apply any option for you**: the choice is required.
{% endstep %}

{% step %}
#### Review and confirm

Check the summary and acknowledge that the account belongs to your subscription and that Azure bills the storage directly to you. Click **Confirm and start** and sign in to Azure in the window that opens.
{% endstep %}

{% step %}
#### Follow the progress

Setup continues in Azure and its progress is saved. **Closing the page does not cancel the work**: reopen **Storage** to pick up where you left off. The stages are:

1. **Azure deployment**: Azure creates the resources;
2. **Permission propagation**: the application's access to the container can take from a few minutes to tens of minutes;
3. **Access validation**: Omni writes, reads and deletes a test file in the container;
4. **Ready to activate**.

If the screen stops checking automatically, use **Keep checking**, **Check deployment in Azure** or **Test storage access**. If an Azure administrator's action is needed, fix the indicated permission or sign in to Azure again and check once more. On failure, you can **Retry the same setup** or **Abandon this setup** (nothing is deleted in Azure).
{% endstep %}

{% step %}
#### Activate preservation

Once access is validated, confirm the retention and the cost acknowledgment and click **Activate preservation**. Activation applies to the **next responses**, including in existing conversations.
{% endstep %}
{% endstepper %}

### What is created in Azure

**New account**: a **StorageV2** account, **Standard** performance, **Hot** tier, blob public access disabled and access only through **Microsoft Entra ID** (access keys disabled). Recovery of deleted blobs and containers (soft delete) is enabled for **7 days**.

**Existing account**: only the exclusive Omni container and the **Storage Blob Data Contributor** role assignment, restricted to that container, for the application identity. The account's protections (soft delete, lifecycle policy, etc.) are **only read and displayed**, never changed.

The application accesses the container with **its own identity**, with no access keys. Omni is not given permanent permission to manage resources in your subscription.

### How it works day to day

1. In a conversation, the code interpreter generates a file (for example, a spreadsheet) and delivers it to the user.
2. If preservation is active and the project is New Foundry, Omni copies the file to the organization's container. The response text **does not depend** on this copy.
3. The file shows its state in the conversation:

| State | Meaning |
| --- | --- |
| **Saving** | The copy to the organization's storage is in progress. |
| **Saved** | The file is stored and available, with its validity (**available until** a date or **no expiry**). |
| **Temporary** | Preservation is inactive or paused: the file may stop being available shortly after it is generated. |
| **Could not save** | The copy failed. The response text is not affected. Automatic retries happen while the source is still available, and you can use **Try saving again**. |
| **Expired / Unavailable** | The validity ended or the file was deleted. |

4. Saved files remain available for download after the temporary source expires, including when reopening the history. Every download goes through Omni, which checks the user's access to that conversation: **anyone without access to the conversation cannot access the file**. The administrator screen shows volumes and health, and is not a browser of users' private files.

{% hint style="warning" %}
If writing to storage fails, Omni does **not** use any other storage as a fallback: the file is marked as failed and the response text is kept.
{% endhint %}

### Retention and deletion

* Retention applies **per file**: the validity is fixed **at the moment the file is generated**. Changing the retention later affects **future files only**.
* When a file expires, it **immediately stops being accessible** in Omni, and physical removal in Azure is done by Omni's cleanup.
* Deleting a conversation (or a project that removes conversations) revokes access and schedules deletion of the corresponding files.
* **Unlimited** retention keeps the files, and the cost, until they are deleted along with the conversation.
* Omni **does not change** your account's lifecycle policies: expiry and deletion of Omni's files are controlled by the application.

### Managing the active destination

In **Settings > Storage**, with the destination active, the Administrator can:

* See the **status** (**Active**, **Paused** or **Degraded access**), the account, the container, the origin (account created by Omni or existing account connected), the retention and the protections read from the account;
* Change the **retention** for new files;
* See the **access health** and use **Validate access now**;
* See the **managed volume** (active files, pending deletion and uncertain) and **Refresh** the measurement;
* Open **See actual cost in Azure**, which takes you to the resource group in the Azure portal;
* **Pause** and **Resume** preservation.

**Pausing** applies to the next responses: new files become temporary again. Nothing is deleted, no validity changes, and files already saved remain available until each one's expiry. **Pausing does not stop Azure billing.**

### Costs

{% hint style="warning" %}
Storage is **billed directly by Azure** to your subscription. Omni **does not cap spending**: Azure budget alerts notify you but do not stop consumption. This cost is not part of the Power Omni invoice or of Omni Budgets.
{% endhint %}

The cost depends on:

* **Stored capacity** and the chosen **retention** (unlimited retention keeps accumulating cost);
* **Region** and **redundancy** (LRS costs less than ZRS);
* **Operations** and, when applicable, **data transfer**;
* **Recovery copies**: soft delete (7 days on a new account) keeps being billed while the copies exist, even after the file has expired or been deleted in Omni;
* **Other data**: on an existing account, the account's cost also includes what other applications store in it.

The **managed volume** shown in Omni is the logical size of the files it controls. **It is not an invoice or a limit**, and it does not include recovery copies, versions or other data in the account. For the actual cost, use **See actual cost in Azure** (Cost Management) and, if needed, filter by the account resource. The portal depends on your permissions and may open in the default directory: switch directory if necessary.

See Microsoft's **Azure Blob Storage pricing** and **Azure pricing calculator** to estimate the amount.

### Frequently asked questions

**Will old files be migrated?** No. Only files generated after activation are stored.

**Can I use the same account with other applications?** Yes, when connecting an existing account. Omni uses only its own container and does not change the rest of the account.

**Can I switch accounts later?** In this version there is one destination per organization, and switching or deleting the account through Omni is not available.

**Can Omni see my data in Azure?** Access uses the application identity, limited to the organization's container, with no access keys.

**I closed the page during setup. What happens?** The work in Azure continues. Reopen **Storage** to follow it.

**Why is validation taking so long?** Permission propagation in Azure can take from a few minutes to tens of minutes.
