Give Read Only Access to Support Engineers
  • 08 Jun 2021
  • 1 Okunan Dakika
  • katkıda
  • karanlık
    ışık
  • Pdf

Give Read Only Access to Support Engineers

  • karanlık
    ışık
  • Pdf

The content is currently unavailable in Türkçe. You are viewing the default English version.
Makale özeti

Give Read-Only access to users in Serverless360

Enterprises face the challenge to provide access to their Azure Integrations to support users in different parts of the globe. Today, it is difficult for the administrators to keep track of the user activities and to restrict the shared access policy of the Azure entities for certain users through the Azure portal. Once the users have access to the Azure portal, they can pretty much do anything on the integration environment such as delete/edit properties of a mission critical Azure entity which could lead to serious consequences for the organization.

Let's consider a scenario, ACME Corp has a built a complex integration scenario using distributed Azure services and they want their support enginners (first level people) across the world to have access to that Azure integration environment. In this case, the business requirement is to allow read-only access to that integration environment to the Level 1 support engineer. This means Scott (level 1 support engineer) will only be able to view the information in the environment and will not have the permission to make any changes to the configurations.

To achieve this, account owner/super user can create a custom user role as 'Support Engineers' in Serverless360.

Restricting Users to only selected Azure Services/Composite Applications

A typical Azure integration environment can have many Azure Services belonging to different business units or departments within the organization. With the Azure portal, it is not possible to segregate the integration scenarios for a specific set of users — say, "user 1 should only be able to access Azure Service Bus Queues and Topics, and user 2 should be able to access Azure Event Hubs and so on". With the Azure portal if an user by mistake, changes any configurations then that could lead to catastrophes in the business operations.
Let's say, Bob, is the support person in ACME Corp who is responsible to manage and monitor only the Azure Service Bus Queues and Topics associated with a composite application. He must be able to access only that composite appliction and it is the responsibility of the account owner/super user to set up the appropriate custom role with need only permissions and add Bob as a user in that role.
SBonly.PNG


Bu makale size yardımcı oldu mu?

What's Next
Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.