> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/cloud/knowledge-base/troubleshooting-articles/unable-to-access-devolutions-cloud-when-the-encryption-service-is-enabled.md).

# Unable to access Devolutions Cloud when the encryption service is enabled

Fix the 500 error that blocks Devolutions Cloud access when the encryption service is enabled by disabling it in the Microsoft Azure Portal.

A 500 Error may occur when accessing the Devolutions Cloud web interface in environments where the encryption service has been configured and enabled. This issue is linked to a known bug introduced in a recent update, specifically affecting deployments using the encryption service.

### Regaining access to Devolutions Cloud

To restore access to Devolutions Cloud, disable the encryption service through the Microsoft Azure Portal:

1. In the Microsoft Azure Portal, navigate to the ***Resource groups*** service.
2. Find the resource group that contains the encryption service.
3. Click on the encryption service linked to the Devolutions Cloud instance.
4. Click ***Stop*** to deactivate it.

Once stopped, access to Devolutions Cloud should be restored. If you still cannot access it, contact our customer support team at <service@devolutions.net>.

### Cleaning up the Azure environment

To keep the Azure environment clean and avoid further issues, update the Redirect URI configuration:

1. In the Microsoft Azure Portal, navigate to the ***App registrations*** service.
2. Find the application containing your encryption service.
3. In the main menu, under ***Manage***, click ***Authentication***.
4. In the ***Redirect URIs*** section, remove any encryption service entries and keep only the original URI:

   ```
   https://login.devolutions.com/op/login/callback
   ```
5. Save the changes.


---

# 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.devolutions.net/cloud/knowledge-base/troubleshooting-articles/unable-to-access-devolutions-cloud-when-the-encryption-service-is-enabled.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.