> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/umbraco-cloud/release-notes/overview-2026/2026-05-releasenotes.md).

# May 2026

## Key Takeaways

* **Error pages** - Upload your own HTML error pages and assign them per hostname. Visitors see your page instead of the default Umbraco Cloud error page when your site is temporarily unavailable.
* **Baseline enhancements** - An activity starts when the baseline pushes updates to child projects.
* **Baseline enhancements** - Baseline update UI state is restored when an update is running.
* **Baseline enhancements** - An activity starts on the baseline project during the creation of a child project.
* **Basic Authentication for all plans** - Basic Authentication is now available on all Umbraco Cloud plans.
* **Anonymized backoffice users on team removal** - Removing a team member from a project now anonymizes their backoffice user across every environment. Audit history is preserved while personal data is cleared.
* **Edge traffic analytics on Traffic & Performance** - The Traffic & Performance page now combines Azure application metrics with Cloudflare edge analytics. New edge metric tiles, chart series, and breakdown tables let you analyze HTTP traffic by status code, cache status, geography, devices, and more.
* **Release Umbraco.Cloud.Cms v17.1.3** - Adds support for the new Basic Authentication login form introduced in Umbraco 17.4.0.

## Error pages

You can now upload custom HTML error pages directly from the Umbraco Cloud Portal and assign them to any hostname across your environments. When an environment restarts, like during a deployment, visitors see your page instead of the default Umbraco Cloud error page.

<figure><img src="/files/bomF1p2hjfuogcCNll1N" alt="Manage Error Pages tab listing uploaded custom error pages"><figcaption><p>The Manage Error Pages tab lists all uploaded pages and their hostname assignments.</p></figcaption></figure>

The feature is available under **Settings** > **Error Pages** and has two tabs:

* **Managing Error Pages**: Upload, preview, edit, replace, and delete custom HTML pages (max 20 KB per file). Mark one as the default fallback for all new hostnames.
* **Hostname Assignments**: See every hostname across all environments and which error page it uses. Assign pages individually or in bulk, and filter by environment, domain, or Top Level Domain.

Because error pages are served by Cloudflare directly from blob storage, they must be fully self-contained. All CSS, JavaScript, and fonts need to be inline; external resources will not load. A reload mechanism is recommended, automatically sending visitors back to your site once it recovers.

For authoring guidelines and a ready-to-use HTML template, see the [Error Pages](/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/error-pages.md) documentation.

## Baseline enhancements

Pushing a baseline update to child projects will trigger an activity on the baseline project. The activity is non-blocking, but will run until all children are updated.

The UI restores the current state of a running baseline update when you return to or refresh the **Manage child projects** page. This helps you track update progress, especially for large batches.

When creating a new child project from a baseline, a non-blocking activity starts on the baseline. The activity is available on the **Project history** page for later review, for instance in case of a failed creation.

## Basic Authentication for all plans

Basic Authentication is now available on all Umbraco Cloud plans. You can enable it from **Settings** > **Public Access** to restrict access to your project environments to project members and allowed IPs.

For setup steps and configuration details, see the [Public Access](/umbraco-cloud/build-and-customize-your-solution/set-up-your-project/project-settings/public-access.md) documentation.

## Anonymized backoffice users on team removal

When you remove a team member from a project, Umbraco Cloud now anonymizes the corresponding backoffice user across all environments. The user is disabled, and the name and email are replaced with anonymized values. Content history, audit logs, and other records that reference the user are preserved, so the audit trail stays intact without retaining personal data.

Umbraco does not allow the deletion of a backoffice user who has logged in at least once. Anonymization is the supported method for removing personal data from a project for users who have signed in. After a team member is removed, no project holds personal data for that person.

<figure><img src="/files/FkeebJi4TioMTaGxzhlD" alt="Backoffice user profile after anonymization, showing the name &#x27;Anonymized User&#x27;, a placeholder email at deleted.invalid, and a Disabled status badge."><figcaption><p>A backoffice user profile after anonymization, with a generic name, a placeholder email, and a Disabled status.</p></figcaption></figure>

## Edge traffic analytics on Traffic & Performance

The **Traffic & Performance** page now combines Azure application metrics with Cloudflare edge analytics. Selecting a hostname displays edge metric tiles for Requests and Data Transfer, edge series on the chart, and the Traffic Breakdown Tables section.

<figure><img src="/files/qrHl46eais3dLLrZzeMx" alt="The Traffic &#x26; Performance page showing the selectors, overview tiles, chart, and breakdown tables."><figcaption><p>The Traffic &#x26; Performance page.</p></figcaption></figure>

The breakdown tables let you drill into edge traffic by status code, paths, hosts, geography, browsers, devices, and more. A toggle at the top of the section switches the view between request count and data transferred.

For full details, see the [Traffic and Performance](/umbraco-cloud/optimize-and-maintain-your-site/monitor-and-troubleshoot/traffic-and-performance.md) documentation.

## Release Umbraco.Cloud.Cms v17.1.3

Umbraco.Cloud.Cms v17.1.3 supports the new Basic Authentication login form introduced in Umbraco 17.4.0. When you use a Basic Authentication-only login flow, the CMS redirects to the new login page. For implementation details, see [Umbraco-CMS PR #22168](https://github.com/umbraco/Umbraco-CMS/pull/22168).


---

# 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:

```
GET https://docs.umbraco.com/umbraco-cloud/release-notes/overview-2026/2026-05-releasenotes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
