Explanation/Reference:
Explanation:
Use a Pull request trigger.
Note: Batch changes
Select this check box if you have a lot of team members uploading changes often and you want to reduce the number of builds you are running. If you select this option, when a build is running, the system waits until the build is completed and then queues another build of all changes that have not yet been built.
References: https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers

Explanation/Reference:
Explanation:
ENABLE DIAGNOSTICS TO LOG ANALYTICS
This configuration is done PER DATABASE
1. Click on Diagnostics Settings and then Turn On Diagnostics

2. Select to Send to Log Analytics and select the Log Analytics workspace. For this sample I will selected only Errors

Reference:
https://techcommunity.microsoft.com/t5/azure-database-support-blog/azure-sql-db-and-log-analytics-better- together-part-1/ba-p/794833

In Azure Automation State Configuration, the Desired State Configuration (DSC) configuration files are used to define the desired state of resources on a system. The structure of the code blocks in a DSC configuration file should be organized in a logical and meaningful way.
One way to structure the code blocks is as follows:
Configuration: This block defines the overall configuration, including any parameters that are used in the configuration.
Node: This block defines the target node(s) for the configuration, typically specified by the hostname or IP address of the target system.
Resource: This block defines the resources that are managed by the configuration, including the resource type, module, and properties.
"A configuration script consists of the following parts:
The Configuration block. This is the outermost script block. You define it by using the Configuration keyword and providing a name. In this case, the name of the configuration is MyDscConfiguration.
One or more Node blocks. These define the nodes (computers or VMs) that you are configuring. In the above configuration, there is one Node block that targets a computer named TEST-PC1. The Node block can accept multiple computer names.
One or more resource blocks. This is where the configuration sets the properties for the resources that it is configuring. In this case, there are two resource blocks, each of which call the WindowsFeature resource."
https://docs.microsoft.com/en-us/powershell/dsc/configurations/configurations?view=dsc-1.1#configuration-syntax

Explanation

Box 1: Microsoft Visual Studio App Center distribution Groups
Distribution Groups are used to control access to releases. A Distribution Group represents a set of users that can be managed jointly and can have common access to releases. Example of Distribution Groups can be teams of users, like the QA Team or External Beta Testers or can represent stages or rings of releases, such as Staging.
Box 2: Shared
Shared distribution groups are private or public distribution groups that are shared across multiple apps in a single organization. Shared distribution groups eliminate the need to replicate distribution groups across multiple apps.
Note: With the Deploy with App Center Task in Visual Studio Team Services, you can deploy your apps from Azure DevOps (formerly known as VSTS) to App Center. By deploying to App Center, you will be able to distribute your builds to your users.
References: https://docs.microsoft.com/en-us/appcenter/distribution/groups