Explanation/Reference:
Explanation:
Squash merging is a merge option that allows you to condense the Git history of topic branches when you complete a pull request. Instead of each commit on the topic branch being added to the history of the default branch, a squash merge takes all the file changes and adds them to a single new commit on the default branch.
A simple way to think about this is that squash merge gives you just the file changes, and a regular merge gives you the file changes and the commit history.
Note: Squash merging keeps your default branch histories clean and easy to follow without demanding any workflow changes on your team. Contributors to the topic branch work how they want in the topic branch, and the default branches keep a linear history through the use of squash merges. The commit history of a master branch updated with squash merges will have one commit for each merged branch. You can step through this history commit by commit to find out exactly when work was done.
References: https://docs.microsoft.com/en-us/azure/devops/repos/git/merging-with-squash

https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-windows?view=azure-devops (Get PAT, run config)

Explanation

Box 1: Upgrade TFS to the most recent RTM release.
One of the major prerequisites for migrating your Team Foundation Server database is to get your database schema version as close as possible to what is currently deployed in Azure Devops Services.
Box 2: Use the TFS Database Import Service
In Phase 3 of your migration project, you will work on upgrading your Team Foundation Server to one of the supported versions for the Database Import Service in Azure Devops Services.
References: Team Foundation Server to Azure Devops Services Migration Guide

References: https://docs.microsoft.com/en-us/azure/devops/pipelines/release/triggers

With the storage account ready, you can configure backs up in the web app or App Service.
Open the App Service az400-11566895-main, which you want to protect, in the Azure Portal and browse to Settings > Backups. Click Configure and a Backup Configuration blade should appear.
Select the storage account.
Click + to create a private container. You could name this container after the web app or App Service.
Select the container.
If you want to schedule backups, then set Scheduled Backup to On and configure a schedule: every five hours Select your retention. Note that 0 means never delete backups.
Decide if at least one backup should always be retained.
Choose if any connected databases should be included in the web app backup.
Click Save to finalize the backup configuration.

Reference:
https://petri.com/backing-azure-app-service