User-tied flight, also referred to as 'sticky' flighting, ensures that a user engages with the same variant throughout an A/B test, regardless of how many times they visit the site. In contrast, un-tied flights randomly assign each of a user's requests to different test variants, without considering which variant the user encountered in prior visits. I would opt for a user-tied flight when the A/B test includes modifications that extend across several page views or sessions, such as improvements to the user interface. This approach guarantees a consistent experience for users. The advantage of user-tied flights is their ability to accurately measure changes that have lasting impacts or necessitate multiple interactions. However, a potential downside is that they might introduce bias due to users' previous exposure. On the other hand, un-tied flights are beneficial for tests that involve changes not reliant on multiple interactions or that don’t accumulate over time. This could encompass alterations to the search algorithm or the Search Engine Results Page (SERP). Un-tied flights are straightforward to implement and offer a fresh perspective each time a user visits Bing. However, they can yield inconsistent results, particularly if there are many returning users.