Posted: 18 August 2026, 11:43 (UTC)

We have added new public IP address ranges for UKDC4 and UKDC5 to our network requirements. Please ensure you allow these ranges.

our customers would like to be able to perform a full Tenant Restore directly from the Console using BYOK, without relying on Microsoft.

The goal is to restore all accounts within a tenant in a single operation, rather than having to restore each account individually.

Currently, the Console only allows individual Backup Sets or accounts to be restored via InstantData. For larger tenants, this can be very time-consuming and requires a lot of manual interaction.

It would be great if Redstor could provide a Full Tenant Restore option that allows all accounts within a tenant to be selected and restored in a single operation, while still supporting BYOK and without requiring Microsoft as an intermediary.

Is this functionality already planned or available on the roadmap?

Thanks!

This server will not be available for backups while maintenance takes place. Any urgent restores can be attempted from ukdc5ms95.pro.redstor.com using the steps in this article: 1118 - How to restore data from a MirrorServer

No timeline is currently available. Updates will be provided here.

During these maintenance windows, connectivity may be impacted for up to six hours, as detailed below. The maintenance is not expected to affect both ZADC1 and ZADC2 at the same time, and any urgent restores can be performed using the steps in this article: 1118 - How to restore data from a MirrorServer

Activity Window 1: 

• Estimated Event Start time: 18:00 GMT on 29 July 2026 

• Estimated Event End time: 04:00 GMT on 30 July 2026

• Maintenance Window: 10 Hours

• Expected Downtime: 6 Hours

Activity Window 2:

• Estimated Event Start time: 18:00 GMT on 31 July 2026

• Estimated Event End time: 04:00 GMT on 1 August 2026

• Maintenance Window: 10 Hours

• Expected Downtime: 6 Hours

Should you require assistance, please reach out to us, where a member of our team will be happy to assist you.

We are actively working to resolve this and will post updates here as they become available.

 If you have any questions, please log a support ticket.

Updates will be posted here as they become available.

The Backup & Recovery products for Xero and Salesforce are being retired. 

• These products are no longer available for new sales as of 28 May 2026.

• Existing customers can continue using the products until the planned end of support date in August 2026. 

• The products will reach end of life from October 2026. 

We will support customers with data egress from the CyberSentriq platform at no additional cost. 

We recommend reviewing your protected Xero and/or Salesforce data to determine what you need to export before the products reach end of life.

Please contact your account manager or our Support team if you have any questions.

We are experiencing timeouts to our storage servers in UKDC4. M365 and Google Workspace backups to these servers are currently failing. Our engineers are investigating and updates will be posted here as they become available.

You can now open a detailed restore log for any Azure Virtual Machine, so you can see exactly what happened during a restore instead of piecing it together yourself.

When a restore succeeds, you get confirmation that everything completed as expected. When it fails, you get the reason in plain language, along with a clear sense of what to do next.

What's included

Each restore log pulls the full picture into a single panel:

• A clear status at the top of every log, so you know straight away whether a restore succeeded or failed.

• A restore overview covering the job's key context, including subscription, resource group, tenant, and who ran it.

• A result summary with key metrics like data restored, elapsed time, and the backup point used.

• Plain-language errors that tell you why a restore failed and where to look.

• One-click copy of the key details for notes or a support ticket.

The panel keeps the overview, the result summary, and any errors in separate sections, so you can confirm a clean recovery at a glance or pinpoint a problem the moment it happens. For example, if a restore is blocked by an Azure policy, the log tells you directly and points you to your subscription's compliance assignments, so you know exactly where to start.

To open a restore log, go to the Restore tab for an Azure VM and select View details next to any restore.

For more details, see Recovery troubleshooting in the knowledge base.

We'd love your thoughts

Now that Azure VM restore logs are available, we'd like to know:

• Has this made it easier to understand and troubleshoot restore failures?

• Have you encountered any restore errors where the information provided wasn't enough to understand what went wrong or what to do next?

Please share your feedback in the comments below, or reach out to our team directly.

During this process, we discovered that Microsoft 365 organisations can be moved between customers/partners, but Microsoft Entra ID organisations cannot currently be moved or renamed once created.

This has left us with Entra ID organisations displaying legacy names (for example, names with suffixes such as "01") that no longer reflect the actual tenant or customer structure. Whilst this is primarily a cosmetic issue, it creates unnecessary confusion when managing multiple tenants and makes the platform appear inconsistent.

Suggested enhancements:

• Allow Microsoft Entra ID organisations to be renamed after creation.

• Allow Microsoft Entra ID organisations to be moved between customers/partners in the same way as Microsoft 365 organisations.

• Provide an administrator-controlled method to correct naming mistakes without requiring deletion and re-protection of the tenant.

For organisations such as Multi-Academy Trusts, MSPs and groups managing multiple Microsoft tenants, these capabilities would make tenant management significantly cleaner and easier.