For decades now, the operations and management of a integration solution are always an afterthought. The architects and developers focus mainly on delivering the solution to the business and pay very little attention to how that solution can be managed and operated daily. We have seen companies reluctant to give permission to their operations people for the production subscriptions since it’s so hard to set the correct level of permissions to relevant teams (even though the role based access is very matured in Azure Portal). Every day there are some new changes happening in Azure and it’s so difficult to keep up with operation boundaries.
To cater to these challenges, ServiceBus360 provides the concept of management stack. Where you can restrict users based on role definition to perform CRUD operations on selected Azure Services. This feature also reduces the switching between the tabs in the Azure portal.
Easy to Use
Creating and deleting an Azure resource in ServiceBus360 doesn’t require programming skills – any non-technical member from the support or business user team can perform these operations in just a few clicks. One of the advantages of using ServiceBus360 to create Azure resources with the ability to set a variety of properties while creating the resource. The number of properties that are available to be set while creating in the Azure portal is limited.
Integration solutions are mostly dynamic based on business requirements ie., Azure resource properties set during the creation may not be valid in all cases. ServiceBus360 doesn’t end with creating the resources, you have the control to change and define the properties at any time in the production scenario.
Shared Access Policy
Each Service Bus namespace and each Service Bus entity has a Shared Access Authorization policy made up of rules. The policy at the namespace level applies to all entities inside the namespace, irrespective of their individual policy configuration. You can create new rules for you Service Bus resources within ServiceBus360 UI without switching to the Azure portal.