Instead, you connect HDInsight to your on-premises network by using Azure Virtual Networks and a VPN gateway.
Note: To allow HDInsight and resources in the joined network to communicate by name, you must perform the following actions:
Create Azure Virtual Network.
Create a custom DNS server in the Azure Virtual Network.
Configure the virtual network to use the custom DNS server instead of the default Azure Recursive Resolver.
Configure forwarding between the custom DNS server and your on-premises DNS server.
Reference:
https://docs.microsoft.com/en-us/azure/hdinsight/connect-on-premises-network

Reference:
https://docs.microsoft.com/en-us/azure/security-center/just-in-time-explained

Reference:
https://docs.microsoft.com/en-us/azure/security/azure-log-audit

To register App28681041 to Azure AD and generate a password for it, you can follow these steps:
In the Azure portal, search for and select Azure Active Directory.
In the left pane, select App registrations.
Select New registration.
In the Register an application pane, enter the following information:
Name: App28681041
Supported account types: Select the appropriate account types for your scenario.
Redirect URI: Leave this field blank.
Select Register.
In the App registrations pane, select the newly created App28681041 application.
In the left pane, select Certificates & secrets.
Select New client secret.
In the Add a client secret pane, enter the following information:
Description: Enter a description for the client secret.
Expires: Select an appropriate expiration date for the client secret.
Select Add.
In the Certificates & secrets pane, copy the value of the newly created client secret.
You can find more information on this topic in the following Microsoft documentation: Quickstart: Register an application with the Microsoft identity platform.

Reference:
https://docs.microsoft.com/en-us/azure/security-center/tutorial-security-policy
https://docs.microsoft.com/en-us/azure/security-center/policy-reference