From BizTalk360 version 8.3, we are enhancing the capabilities of managing Logic App services running on Azure. BizTalk360 is equipped with the framework to be able to manage Logic Apps. If you are new to BizTalk360, please read the Monitoring Logic Apps from BizTalk360 to get a basic idea of monitoring concept and how you can set up Logic Apps monitoring in BizTalk360. To manage Logic Apps from BizTalk360, you have to add the Azure Subscription details to BizTalk360.

To enable permission for BizTalk360 to access the Azure subscription read this article

Adding the Azure Subscription details to BizTalk360

In this section, let us take a look at the process of adding an Azure subscription (with the client identifier, tenant identifier, and application secret key information) to BizTalk360.


Only Super Users will have the permissions to add a new Azure subscription to BizTalk360 (as the configuration has to be made in the BizTalk360 Settings page).

  1. Log in to BizTalk360 (as a Super User). Click the Settings icon at the top of the screen. Navigate to Monitoring and Notification Manage Azure Subscriptions
    configuring biztalk environment for monitoring and notifications

  2. Click Add Azure Subscription. In the Azure Subscription Details page, you will see the below fields: managing azure subscription in biztalk360
    new azure subscription validation
    1. Friendly Subscription Name - You can enter a friendly name for the subscription that you are adding to BizTalk360
    2. Choose Environment - You can select the environment for which you want to add the Azure subscription.
      You can only choose one environment at a time from the drop down. If you have 3 environments and you want to map the Azure subscription for only 2 environments, you need to add the subscription separately for both environments. 
      The normal monitoring restrictions will apply for Normal users. If the normal user does not have access to the environment, he cannot monitor the Azure services. If the normal user does not have permissions to monitor Azure services (under User Access Policy settings), they cannot monitor the Azure Services.
    3. Tenant Identifier - The identifier that authorizes and provides single sign-on and directory access for the application that you integrated with Microsoft Azure AD
    4. Client Identifier - The unique identifier for the application you integrated with Azure AD
    5. Application Secret Key - In order for BizTalk360 to be able to read or write data in Microsoft Azure AD, you need to enter the application key
    6. Publish Settings File - A simple XML file with the subscription details and the management certificate for authenticating the management API requests. You can download the Publish Settings file by clicking the link. You need to add this file in order to validate the Azure subscription details (in addition to the previously entered details in Step 3, 4, 5).
    7. Enable Subscription for Monitoring or Operations - You need to toggle the icon to the active state in order to enable the subscription for monitoring/operations with BizTalk360. 
    8. Validate - Click the button to validate the entered subscription details. You will be prompted to copy a command and execute in PowerShell. Please refer to the steps in this article to see the process of enabling the permission for BizTalk360 to access the Azure subscription.
    9. Done - Once you have successfully executed the command in PowerShell, click Done. You will notice the confirmation message as "You have successfully validated the configurations. Click save to start monitoring the Azure Resources".
      If the PowerShell execution did not happen as expected or if you click Done without performing the PowerShell operation, you will notice an error message as "Azure PowerShell command not executed properly. Try to execute the command successfully and click Done." The Validate button will change to Validated and will be in the disabled state. For further information about the process of executing the PowerShell command, please click the Need Help link.
    10. Save - Click save to start managing Logic Apps from BizTalk360
  3. The Azure subscription details will be updated on the Manage Azure Subscriptions page


Follow the steps as shown below to add a new Azure Subscription in BizTalk360.


enabling new azure subscription for monitoring
azure subscription id validation for monitoring 
executing validation command in powershell
 
managing azure subscription status details in biztalk360


Managing Logic Apps from BizTalk360

When a Logic App gets disabled for some reason, it can be either move to enable state or run trigger or even delete the Logic App. When in the disabled state, the administrators have an option to manually enable the Logic App through the BizTalk360 portal.

Follow the steps as shown below to managing Logic Apps from BizTalk360:

  1. Log in to the BizTalk360 application
  2. Click the 'Operations' tab in the Navigation panel

  3. Click the expand button against the 'Azure Services' and select 'Logic Apps' link
  4. Select the Azure Subscription from the dropdown. The Logic Apps associated with the Subscription will be displayed in the grid. The below information are displayed in the grid:
    • Logic App Name
    • Access End Point
    • Logic App Status
    • Last Run
    • Details
  5. When Azure subscription is suspended or disabled then BizTalk360 will not take any action against the Logic Apps.
    The user can perform the required operation in 2 different ways:
    • Selecting the check boxes against the Logic App(s) and clicking on the Operation buttons (enable/disable/run trigger/delete) at the top of the grid
    • Selecting check box against the Logic App. User will notice an inline operation showing up right next to the check box with the possible operations that can be performed on the Logic App
  6. To view the Logic App details, click the eye icon against the Logic App name
  7. The Logic App Details blade displays the basic information as the Resource Group, Location, Subscription Name, and the Last Run Date. Additionally, there are three tabs displaying the List view, Graph view and the Details view of the Logic App Runs and Triggers.

Important points to remember

  1. The user can only initiate the Logic Apps operation from BizTalk360
  2. The user cannot trigger the first Run from BizTalk360
  3. After performing a Logic App operation, click the Refresh button to reflect the current status of the Logic Apps 
  4. The users can perform bulk operations on Logic Apps by clicking the check box against the Logic Apps
  5. If a Logic app is not Run even once, then the Last Run Column in Azure Services - Operations grid will be left empty