Troubleshooting: Subscriptions Visibility Issue in Azure Stack Hub
Question
Consider a scenario where your Azure Stack Hub instance is disconnected and you have 2 different domains where users in domain1 create subscriptions that are consumed by users in domain2
You identify an issue that some subscriptions are visible in the admin portal but not in the user portal.How can this issue be fixed?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: B
In a disconnected Azure Stack Hub, instance and 2 different domains where users of a domain create the subscriptions and users of another domain consume them, some subscriptions might be visible in the admin portal but not in the user portal.
This issue can be fixed by having the users in domain1 set the right RBAC for the subscriptions in domain2.
Option A is incorrect.
The right solution is to have the users in domain1 set the right RBAC for the subscriptions in domain2 as these are the users from domain1 that create the subscriptions.
Option B is correct.
Having the users in domain1 set the right RBAC for the subscriptions in domain2 will help in fixing the issue.
Option C is incorrect.
Restarting the Azure Stack Hub Admin Portal is not the right solution.
Option D is incorrect.
Users from the different domains can consume the subscriptions created by the users from another domain.
To know more about Azure Stack Hub services, plans, offers, subscriptions, visit the below-given link:
In this scenario, the issue is that some subscriptions are visible in the admin portal but not in the user portal. This indicates a permissions or RBAC (Role-Based Access Control) issue. RBAC is used to manage access to resources and services in Azure Stack Hub.
Option A suggests having users in domain2 set the right RBAC for the subscriptions in domain1. This could potentially work if the issue is related to permissions, but it would only address half of the problem. Users in domain1 would also need to set the correct RBAC for subscriptions consumed by users in domain2.
Option B suggests having users in domain1 set the right RBAC for the subscriptions in domain2. This is a more complete solution as it would ensure that both domains have the correct RBAC settings for subscriptions created and consumed by each other.
Option C suggests restarting the Azure Stack Hub Admin portal. While restarting the portal may resolve some issues, it is unlikely to address a permissions or RBAC issue.
Option D states that users from different domains cannot consume subscriptions created by users from some other domain. This is not entirely true, as cross-domain consumption of subscriptions is possible with the correct RBAC settings in place.
Therefore, the correct answer to this scenario is B: Have the users in domain1 set the right RBAC for the subscriptions in domain2.
