Explanation:

Box 1: Reader
Members of a group named Developers must be able to install packages.
Feeds have four levels of access: Owners, Contributors, Collaborators, and Readers. Ownerscan add any type of identity-individuals, teams, and groups-to any access level.
Box 2: Owner
Members of a group named Team Leaders must be able to create new packages and edit the permissions of package feeds.

For containerized applications that serve traffic, you might want to verify that your container is ready to handle incoming requests. Azure Container Instances supports readiness probes to include configurations so that your container can't be accessed under certain conditions.
Reference:
https://docs.microsoft.com/en-us/azure/container-instances/container-instances-readiness-probe

See the solution below in explanation.
Explanation:
To create an instance of Azure Application Insights namedaz400-38443478-mainand configure it to receive telemetry data from an Azure web app with the same name, you'll need to follow these steps:
* Create a Log Analytics Workspace:
* Go to theAzure Portal.
* Search for Log Analytics Workspaces and select Add.
* Select a Subscription and either use an existing Resource Group or create a new one.
* Provide a unique name for your Log Analytics workspace.
* Choose the Region that is appropriate for you.
* Review the settings and then selectCreate1.
* Create an Azure Application Insights Instance:
* In the Azure Portal, navigate to Application Insights.
* Click on + Create.
* Fill in the instance details, ensuring the name isaz400-38443478-main.
* Link the instance to the Log Analytics workspace you created in the previous step.
* Review and create the Application Insights instance2.
* Configure the Azure Web App to Send Telemetry Data:
* Go to the Azure Web Appaz400-38443478-main.
* Under Monitoring, selectApplication Insights.
* Choose to use an existing resource and select the Application Insights instance you created.
* Follow the prompts to set up the connection, which may involve adding the appropriate SDK to your web app and configuring the connection string or instrumentation key.
* Verify Telemetry Data Reception:
* After setting up, send some test traffic to your web app.
* Then, go to the Application Insights instance and check the Overview or Performance sections to see if telemetry data is being received.
Remember to replace placeholder names with the actual names of your resources where necessary. These steps will help you set up Azure Application Insights to monitor your web app effectively.

You can create a service hook for Azure DevOps Services and TFS with Jenkins.
However, the service subscription event should use the code pushed event, is triggered when the code is pushed to a Git repository.