# Forbidden page in Elastic Cloud in Azure

**URL:** <https://discuss.elastic.co/t/forbidden-page-in-elastic-cloud-in-azure/309985>\
**Category:** Elasticsearch\
**Created:** [July 19, 2022, 7:22am UTC](https://discuss.elastic.co/t/forbidden-page-in-elastic-cloud-in-azure/309985 "2022-07-19T07:22:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![arks](https://avatars.discourse-cdn.com/v4/letter/a/d2c977/32.png) [@arks](https://discuss.elastic.co/u/arks)\
**Post date:** [July 19, 2022, 7:22am UTC](https://discuss.elastic.co/t/forbidden-page-in-elastic-cloud-in-azure/309985/1 "2022-07-19T07:22:25Z")

</div>

Hello there,

First of all let me start by saying that I feel silly posting a problem like this, because it feels like something particularly easy to solve, but somehow we struggle to find a way of doing it.

We have a Elasticsearch (Elastic Cloud) resource deployed on Azure. When we get into the Elastic's UI, everyone (besides the person who deployed the resource) gets a "Forbidden. You are not allowed to access this resource" page. We log into Elastic with our Microsoft accounts that have access to the Azure resource.  
This sounds like we should explicitly grant users access to Elastic, however we are not sure how to do that. We tried granting some extra accesses directly in Azure but it doesn't seem to do anything. On the other hand we can't find anything like that in Elastic.

How would we go about that problem? Thanks in advance

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [July 19, 2022, 7:35am UTC](https://discuss.elastic.co/t/forbidden-page-in-elastic-cloud-in-azure/309985/2 "2022-07-19T07:35:15Z")

</div>

Welcome to our community! 😃

You can definitely ask the Support team this question. However are all of your users subscription owners? That is the level that they need to be to access things as I understand it from [the docs](https://www.elastic.co/guide/en/cloud/current/ec-azure-marketplace-native.html).

---

<div class="post-metadata">

**Author:** ![arks](https://avatars.discourse-cdn.com/v4/letter/a/d2c977/32.png) [@arks](https://discuss.elastic.co/u/arks)\
**Post date:** [July 19, 2022, 9:50am UTC](https://discuss.elastic.co/t/forbidden-page-in-elastic-cloud-in-azure/309985/3 "2022-07-19T09:50:24Z")

</div>

Hmmm I don't think that giving all of us the owner privileges is the solution here. The docs say that about deployment and we don't need to deploy it anymore, we just want to access the Elastic stuff 🙂 Also, we have two people over here that are the owners of the subscription and only one of them can access the deployed resource

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 2, 2022, 9:51am UTC](https://discuss.elastic.co/t/forbidden-page-in-elastic-cloud-in-azure/309985/4 "2022-08-02T09:51:19Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
