> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/overview-2/use-cases/azure-portal-link.md).

# Azure Portal link

Create a link to the Azure Portal from DuploCloud

Creating a direct link to the Azure Portal from your DuploCloud Infrastructure saves your time when you work with DuploCloud Azure resources. Instead of toggling between the DuploCloud Portal and the Microsoft Azure Portal, get instant access to the Azure Portal from DuploCloud.

{% hint style="warning" %}
Failure to follow these steps when creating a link to the Azure Portal from the DuploCloud Portal results in the error message:

`Error while fetching Azure portal link: Portal url config does not exist`
{% endhint %}

## Creating a link to the Azure Portal

1. In the DuploCloud Portal, navigate to **Administrator** -> **Infrastructure**. The **Infrastructure** page displays.
2. From the **Name** column, select the Infrastructure for which you want to add a link to the Azure Console.
3. Click the **Metadata** tab.
4. Click **Add**. The **Add Infrastructure Tag** pane displays.
5. In the **Key** field, enter **AzurePortalLink**.<br>

   <div align="left"><figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Fvx1H3PPWWJ1mEdpeKN9E%2Fazure_portal.png?alt=media&amp;token=ea6b37eb-1d73-4fe5-9185-63fe71215729" alt=""><figcaption><p><strong>Add infrastructure Tag</strong> pane with <strong>Key AzurePortalLink</strong></p></figcaption></figure></div>
6. In the **Value** field, enter the URL for your Azure Portal.
7. Click **Create**.

{% hint style="warning" %}
The **Value** in the example above is DuploCloud's internal Azure Portal link.
{% endhint %}

## Accessing the Azure Portal

After you [configure Azure Portal link ](#creating-a-link-to-the-azure-portal)to an Infrastructure, access the Azure Console from the DuploCloud Portal in the **Actions** menu for Azure **Hosts**.

1. In the DuploCloud Portal, navigate to **Cloud Services** -> **Hosts**. The **Hosts** page displays.
2. From the **Name** column, select the Host you are working with.
3. From the **Actions** menu, select **Connect** -> **Azure Portal**.

<figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2Faum9tdINPEwxJB0yrdof%2FScreenshot%20(229).png?alt=media&amp;token=6914162a-aebd-49b8-8ef4-f3fd0302f948" alt=""><figcaption><p>Host details page with with the <strong>Action Menu</strong> and <strong>Azure Portal</strong> link highlighted</p></figcaption></figure>


---

# 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.duplocloud.com/docs/automation-platform/overview-2/use-cases/azure-portal-link.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.
