Advanced capabilities for managing permissions
The authorization model included out of the box with BizTalk Server is very limited; you can give someone BizTalk administrators or BizTalk operators’ rights, but that is about it. However, this is insufficient, and it’s imperative for organizations to be able to manage access permissions to various resources on the Microsoft BizTalk Server platform.
With BizTalk360, this assumption becomes possible, bringing, included in the product, advanced management permissions capabilities, fully customizable, that will allow organizations to define their own authorization requirements.
📝 One-Minute Brief
Standard BizTalk Server authorization is limited to broad “Administrator” or “Operator” roles, which often poses security risks in shared environments. BizTalk360 solves this by offering a fine-grained, fully customizable permission model. Organizations can now restrict users to specific applications, provide read-only access, or hide confidential messages. This advanced user authorization not only bolsters security but also streamlines the support experience by hiding irrelevant data from project-specific teams.
BizTalk Server is too expensive to be used by only one department of the organization, so it’s normal to be shared between departments or project teams. These features (Advanced User Authorization) will help the BizTalk administration teams to properly define how the project teams or company departments will have access to the production environment without the fear that they will interfere with other resources that are not theirs. Administrative teams will now be able, for example, to:
- Define your own NT roles and dictate how a user can access the environment;
- Restrict users/groups to limited applications, give users read-only access, or set up restrictions for support staff to resume or terminate instances.
- Restricted view for certain users/groups.
- Restricted access to confidential messages.
Fine-grained authorization brings a lot of advantages for the enterprise. The foremost reason is security, by restricting access to the various components, functionalities, applications, or BizTalk artifacts. Also, on the other hand, it makes life easy for application support people; they have hidden away from unnecessary things, which are not related to their task.
