Do you validate source tenant permissions when you create the BitTitan project, then assume they will stay valid for the rest of pre-stage?

BitTitan endpoints depend on source tenant credentials that are correct at the moment you configure them. During a longer pre-stage period, those same credentials can become unusable for reasons the migration team does not control: scheduled password rotation by the security team, conditional access changes that introduce MFA for accounts that were previously excluded, service account expiration, or Entra ID changes that alter the account group memberships and remove a CA exclusion.

That is why an overnight BitTitan pre-stage run can start at midnight and fail because the credentials broke earlier in the day, then go unnoticed until someone checks job status the next morning. Unless you have set notification thresholds to trigger on failures, you can lose hours of pre-stage time with no alert.

A cadence that prevents this is simple: before each scheduled pre-stage pass, manually validate the endpoint in the BitTitan portal and only then submit jobs. The validation typically takes under 2 minutes and confirms the credentials are still valid before the batch runs. When overnight passes make manual validation impractical, configure BitTitan error threshold notifications so failures trigger alerts within the first 30 minutes of the pass.

Are you validating BitTitan source tenant endpoint credentials before each pre-stage pass submission throughout the pre-stage period?

#BitTitan #MigrationWiz