When you are migrating to Azure DevOps you MUST provide an PAT

[nkofctg]

While running 15.2, I was able to run migrations from many sources to many destinations. After upgrading to 16.0.1, all migration attempts end after a few seconds, with the error stating that the PersonalAccessToken is missing from my Target configuration. However, my configuration does include a PAT.

I have attempted this with several 15.2 versioned config files, as well as the above, which was taken from a newly initialized config file (with relevant configs added, including of course my PAT). I have also attempted to change to Prompt authentication, and tried adding / removing the NetworkCredentials block.

"Target": {
        "EndpointType": "TfsTeamProjectEndpoint",
        "Collection": "https://dev.azure.com/ContosoInc/",
        "Project": "Company Project",
        "Authentication": {
          "AuthenticationMode": "AccessToken",
          "AccessToken": "thisiswhereatokengoesanditalmostkindalookslikethis"
        },
        "ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId",
        "AllowCrossProjectLinking": false,
        "LanguageMaps": {
          "AreaPath": "Area",
          "IterationPath": "Iteration"
        },

[08:26:13 INF] [16.0.1] Migration Context Start: TfsWorkItemMigrationProcessor
[08:26:13 ERR] [16.0.1] When you are migrating to Azure DevOps you MUST provide an PAT so that we can call the REST API for certain actions. For example we would be unable to deal with a Work item Type change. 
System.InvalidOperationException: Missing PersonalAccessToken from Target

[nkdagility-actions-bot[bot]]

Hi there,

ACTION REQUIRED

In order for us to help you will need to provide both the log, and the configration file that you are using.

Generate and Attach Log

Steps:

1. In the Config file, change LogLevel to Debug.
2. Identify a work item ID that exhibits this issue and create a query that only selects this work item.
3. Delete any existing copy of that work item from the target.
4. Run the migration.
5. Comment here with the full Log attached as well as the full (redacted) configration file that you are using.

Your assistance is greatly appreciated!

Thanks, Azure DevOps Migration Tools team

[MrHinsh]

Can you provide the full configuration?

Things to check:

1. Ensure the endpoint is listed under "MigrationTools:Endpoints".
2. Verify that the processor references the correct endpoint.

---

Note on the new format:

The new configuration format supports multiple endpoints. We transitioned from a grouped set of lists to a single set of named entries. This change allows overrides via the command line and environment variables.

The validation error you're encountering adds an extra layer to ensure a Personal Access Token (PAT) is used when connecting to Azure DevOps (ADO).

---

PAT Token Validation Logic:

private void ValidatePatTokenRequirement()
{
    string collUrl = Target.Options.Collection.ToString();
    if (collUrl.Contains("dev.azure.com") || collUrl.Contains(".visualstudio.com"))
    {
        var token = Target.Options.Authentication.AccessToken;
        
        // Check if the token is missing
        if (token.IsNullOrEmpty())
        {
            var ex = new InvalidOperationException("Missing PersonalAccessToken from Target");
            Log.LogError(ex, "When migrating to Azure DevOps, you MUST provide a PAT to access the REST API for certain actions. For example, handling Work Item Type changes would be impossible without it.");
            Environment.Exit(-1);
        }
    }
}

---

Endpoint Configuration Example:

Your endpoint should be structured like this:

{
  "MigrationTools": {
    "Endpoints": {
      "Target": {
        "EndpointType": "TfsTeamProjectEndpoint",
        "Collection": "https://dev.azure.com/ContosoInc/",
        "Project": "Company Project",
        "Authentication": {
          "AuthenticationMode": "AccessToken",
          "AccessToken": "thisiswhereatokengoesanditalmostkindalookslikethis"
        },
        "ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId",
        "AllowCrossProjectLinking": false,
        "LanguageMaps": {
          "AreaPath": "Area",
          "IterationPath": "Iteration"
        }
      }
    }
  }
}

---

Supporting Multiple Endpoints:

To support multiple endpoints, you can use named entries:

{
  "MigrationTools": {
    "Endpoints": {
      "Target": {
        "EndpointType": "TfsTeamProjectEndpoint",
        "Collection": "https://dev.azure.com/ContosoInc/",
        "Project": "Company Project",
        "Authentication": {
          "AuthenticationMode": "AccessToken",
          "AccessToken": "thisiswhereatokengoesanditalmostkindalookslikethis"
        },
        "ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId",
        "AllowCrossProjectLinking": false,
        "LanguageMaps": {
          "AreaPath": "Area",
          "IterationPath": "Iteration"
        }
      },
      "Alpha": {
        "EndpointType": "TfsTeamProjectEndpoint",
        "Collection": "https://dev.azure.com/ContosoInc/",
        "Project": "Company Project",
        "Authentication": {
          "AuthenticationMode": "AccessToken",
          "AccessToken": "thisiswhereatokengoesanditalmostkindalookslikethis"
        },
        "ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId",
        "AllowCrossProjectLinking": false,
        "LanguageMaps": {
          "AreaPath": "Area",
          "IterationPath": "Iteration"
        }
      },
      "Beta": {
        "EndpointType": "TfsTeamProjectEndpoint",
        "Collection": "https://dev.azure.com/ContosoInc/",
        "Project": "Company Project",
        "Authentication": {
          "AuthenticationMode": "AccessToken",
          "AccessToken": "thisiswhereatokengoesanditalmostkindalookslikethis"
        },
        "ReflectedWorkItemIdField": "Custom.ReflectedWorkItemId",
        "AllowCrossProjectLinking": false,
        "LanguageMaps": {
          "AreaPath": "Area",
          "IterationPath": "Iteration"
        }
      }
    }
  }
}

---

This structure allows you to define multiple endpoints with the flexibility to customize their configurations as needed.

[nkdagility-actions-bot[bot]]

Hi there,

ACTION REQUIRED

In order for us to help you will need to provide both the log, and the configration file that you are using.

Generate and Attach Log

Steps:

1. In the Config file, change LogLevel to Debug.
2. Identify a work item ID that exhibits this issue and create a query that only selects this work item.
3. Delete any existing copy of that work item from the target.
4. Run the migration.
5. Comment here with the full Log attached as well as the full (redacted) configration file that you are using.

Your assistance is greatly appreciated!

Thanks, Azure DevOps Migration Tools team