https://www.quest.com/community/on-demand/en-USTelligent Community 13https://www.quest.com/community/on-demand/f/forum/37446/announcing-general-availability-of-on-demand-migration-for-power-platform/86549Wed, 05 Aug 2026 14:07:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:407c27cc-b9b5-40ba-a8e0-87220209b7eaa foulieHi Thanks for this announcement, You talk about power Platform, but when I read your article, only Power Apps and Power Automate are listed. Power Platform is more than only 2 services, you have Power Pages, Copilot Studio and Dynamics. So, can your product migrate all Power Platform services or just Apps and Automate? Thanks Regardshttps://www.quest.com/community/on-demand/f/forum/37446/announcing-general-availability-of-on-demand-migration-for-power-platformTue, 04 Aug 2026 12:18:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:f7c2bfd8-34d2-4c17-b9d0-425131f23db0gary hughesMicrosoft 365 tenant migrations have evolved significantly over the past decade. Moving Exchange, OneDrive, SharePoint, Teams, and Microsoft 365 Groups has become a well-understood process. But one critical workload has increasingly remained outside the migration scope: Microsoft Power Platform . Today, we're excited to announce the general availability of On Demand Migration for Power Platform, extending Quest's migration leadership to support the discovery, assessment, pre-migration reporting, and migration of Power Apps and Power Automate. This new capability becomes generally available on August 4, 2026, and marks another major milestone in our mission to provide comprehensive Microsoft 365 tenant-to-tenant migration coverage. This launch builds on our successful introduction of On Demand Migration for Power BI, which was added to the platform in Q3 2024, enabling customers to discover and migrate Power BI workloads as part of larger tenant consolidation initiatives. The Missing Piece in Microsoft 365 Migrations Power Platform is no longer just a low-code development toolkit. For many organizations, it has evolved into a critical operational layer within Microsoft 365, supporting everything from employee onboarding and financial approval processes to service desk workflows, HR automation, and custom business applications. Whether built with Power Apps or powered by Power Automate, these solutions often sit at the center of day-to-day business operations and contain the workflows, approvals, and business logic that employees rely on every day. The challenge is that these assets are frequently created outside of centralized IT processes by business users and citizen developers. As a result, organizations often lack complete visibility into what exists, who owns it, and how individual apps and flows are connected to broader business processes. During tenant consolidations, mergers, acquisitions, and divestitures, this makes Power Platform significantly more difficult to assess and migrate than traditional Microsoft 365 workloads. The consequence is a scenario many organizations know all too well. SharePoint sites, Teams, OneDrive content, and user accounts are successfully migrated, only for IT teams to discover later that critical business applications and automations were left behind. These overlooked Power Platform assets can introduce unexpected business disruption, project delays, and additional migration costs long after the primary migration has been completed. With On Demand Migration for Power Platform, Quest is helping organizations close this gap by bringing discovery, assessment, and migration capabilities to Power Apps and Power Automate, ensuring that critical business processes move alongside the rest of the Microsoft 365 environment. What Is On Demand Migration for Power Platform? On Demand Migration for Power Platform is Quest's purpose-built solution for discovering, assessing, and migrating Power Platform workloads between Microsoft 365 tenants. The initial GA release focuses on Power Apps and Power Automate, including the associated environments, Solutions, Flows and other dependencies required for the transition to a new tenant. The solution provides a guided migration workflow that helps organizations move from uncertainty to completion using a structured, repeatable process. Built for the Reality of Power Platform Unlike traditional Microsoft 365 workloads, Power Platform assets rarely exist in isolation. A single Power App can rely on multiple Power Automate flows, environment variables, connectors, Dataverse tables, security permissions, and solution packaging to function correctly. These interconnected dependencies form the foundation of many business-critical processes, yet they are often difficult to identify and manage during tenant-to-tenant migrations. This complexity means that migrating an app is about much more than moving a single object from one tenant to another. Overlooking even a single dependency can result in broken functionality, failed automations, or disrupted business operations after migration. That's why On Demand Migration for Power Platform starts long before migration day, helping organizations discover, assess, validate, and prepare their Power Platform environments to ensure a successful migration outcome. Step 1: Discovery The first challenge in almost every Power Platform project is visibility. Many organizations simply don't know: How many Power Apps exist How many Power Automate flows are running Which environments contain business-critical assets Who owns them What they connect to On Demand Migration performs discovery across the source tenant and builds an inventory of Power Platform assets, helping organizations identify applications and workflows that may otherwise be overlooked. Discovery includes visibility into: Environments Apps Flows Solutions Dataflows Related dependencies This enables migration teams to establish scope before any migration activity begins. Step 2: Pre-Migration Reporting Visibility alone is not enough. Migration teams need actionable intelligence that helps them understand what might prevent a successful migration. Every discovery operation can generate detailed pre-migration reports, providing insight into discovered assets and readiness status. These reports can be exported for offline analysis and project planning. The reports help answer questions such as: Are all assets packaged correctly? Which apps belong to solutions? Which flows may require attention before migration? What dependencies exist across workloads? This allows organizations to identify issues early instead of discovering them during cutover windows. Step 3: Validation & Readiness Checks One of the most unique capabilities within the solution is migration validation. Power Apps and Power Automate assets typically need to exist within solutions to enable reliable migration processing. The validation process reviews the source environment and identifies assets that may not meet migration requirements. Validation checks include: Solution readiness Required components Migration prerequisites Missing dependencies Any issues identified are surfaced through reporting and task events, giving administrators a clear remediation plan before migration begins. Step 4: Optional Remediation Identifying problems is useful. Fixing them automatically is even better. To reduce manual effort, On Demand Migration includes an optional remediation capability that can address certain migration readiness issues before migration begins. Examples include: Adding missing components to solutions Creating solutions where required Preparing apps and flows for migration processing This helps eliminate repetitive administrative work and reduces the likelihood of migration failures caused by configuration issues. Step 5: Migration Once discovery, validation, and remediation have been completed, migration can begin. The migration engine is designed to transfer: Power Apps Power Automate flows Solutions Supporting environment configuration while preserving the relationships and dependencies required for business continuity. Unlike manual approaches that require organizations to repeatedly export and import solutions, track dependencies, and reconfigure components individually, On Demand Migration provides a centralized workflow that simplifies large-scale tenant migration projects. Why This Matters Microsoft provides capabilities for moving certain Power Platform assets and environments, but organizations often face significant planning, dependency management, and manual reconfiguration requirements during tenant-to-tenant migration projects. As Power Platform adoption continues to accelerate, this challenge is becoming increasingly common. The reality is that: More business processes are being automated. More applications are being developed by citizen developers. More organizations are consolidating or separating Microsoft 365 tenants. More migration projects now include Power Platform as a critical workload. Ignoring these workloads is no longer an option. Organizations need visibility, governance, and automation. That's exactly what On Demand Migration for Power Platform delivers. Available Today - August 4th 2026 Power Platform has become one of the fastest-growing workloads inside Microsoft 365. Unfortunately, it's also one of the least understood during migration planning. With On Demand Migration for Power Platform, organizations can finally bring Power Apps and Power Automate into scope with the same level of visibility, assessment, and automation they expect from the rest of their Microsoft 365 migration projects. The result is a simpler migration experience, reduced risk, and improved business continuity. Additional Resources Offical Quest.com Blog for the Announcement Data Sheet: On Demand Migration Power Platform workloads Quest.com - Power Platform + Quest On Demand MigrationPower AppsPower PlatformODMMigrationNew Module SpotlightQuest® On Demand MigrationPower AutomatePremigrationOn Demand MigrationCopilothttps://www.quest.com/community/on-demand/f/forum/37323/announcement-new-teams-application-for-on-demand-migration---teams-app-only-permissions/86477Fri, 26 Jun 2026 13:49:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:d9571dfb-602f-45ed-8a9e-c687bf9cd0acgary hughes# Update: June 2026: This application has now been updated to require READ only permissions. All ReadWrite permissions have been removed #https://www.quest.com/community/on-demand/i/ideas/logo-customization-for-odm-ad-interactive-clientWed, 13 May 2026 05:03:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:d96df1be-4af5-4e2d-a7fa-53d0d2baf1a1rakesh chulliparambilMany customers are giving feed back that when the activity of cutover starts on the desktops people think its some kind of malware attack. This can be addressed by providing the customers an option to customize the popup with some Logo and custom message.https://www.quest.com/community/on-demand/f/forum/37323/announcement-new-teams-application-for-on-demand-migration---teams-app-only-permissions/86412Wed, 29 Apr 2026 20:25:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:4249eb4f-a917-4a26-90be-c2a50427e47bgary hughesthat is correct! I share your enthusiasm :)https://www.quest.com/community/on-demand/f/forum/37323/announcement-new-teams-application-for-on-demand-migration---teams-app-only-permissions/86411Wed, 29 Apr 2026 09:22:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:3bfc8d74-a63b-4013-ac31-5f662af79f23marvin dickhaus_41622Hey Gary, that is great to hear. Could you elaborate on the trade offs? Archiving the source Team with the SharePoint site set to read only So archiving of teams is still possible, but we cannot at the same time set the SharePoint site to read-only using the app-only permission, correct? I'm glad that the trade-offs are this minimal.https://www.quest.com/community/on-demand/f/forum/37323/announcement-new-teams-application-for-on-demand-migration---teams-app-only-permissionsTue, 28 Apr 2026 15:14:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:24b971b5-9d85-4fbe-94ce-b1a926fdebf3gary hughesIntroducing Teams – App Only Permissions for On Demand Migration As Microsoft 365 environments continue to mature, customer expectations around security, compliance, and least privilege access have never been higher. Nowhere is this more evident than in Microsoft Teams migrations, where legacy approaches often rely on broad permissions and service accounts that no longer align with modern compliance standards. To address this, we’re introducing a new application for On Demand Migration for Teams: Teams – App Only Permissions. This new consent option is designed for organizations with strict compliance and security requirements, enabling Teams migrations without delegated permissions and without adding a migration service account to the source tenant for migration purposes. # Update: June 2026: This application has now been updated to require READ only permissions. All ReadWrite permissions have been removed # Why This Matters Many organizations migrating Microsoft Teams often face a difficult challenge: “How do we move collaboration data without expanding access beyond what security and compliance teams are willing to approve?” Prior to the introduction of Teams – App Only Permissions, migrating Teams with On Demand Migration required granting consent using a Global Administrator account, which could then be limited to Teams Administrator and Exchange Administrator roles, along with an active M365 Teams license. While this reduced the scope of permissions, migration still relied on elevated permissions. When using Teams – Minimal applications for the migration, this is still a prerequisite as the Service Account used for the migration is added as a member or owner of source Teams and M365 Groups to access specific Teams, Channels & Groups settings and objects required for a full fidelity migration. From a functional standpoint, this approach works well. From a security and compliance standpoint, however, it introduced challenges. For many organizations, particularly those in regulated industries or with strict internal security controls, introducing a licensed service account with administrator roles enabled into production Teams environments on the source tenant (even temporarily) is not permitted. Delegated permissions and user-based access models can also increase audit scope, identity exposure, and risk. Teams – App Only Permissions directly addresses these concerns by eliminating delegated access entirely and removing the need for a migration service account to participate in Teams on the source tenant, allowing migrations to proceed while staying aligned with modern least‑privilege and compliance requirements. Designed for Compliance Driven Environments This new application is particularly well suited for organizations that: Must avoid delegated permissions entirely Require reduced identity footprint during migration Need stronger separation between migration tooling and production collaboration workloads By using application only access, organizations can proceed with migration plans while staying aligned with internal security policies and external regulatory requirements. Feature Impact and Trade Offs To maintain this restrictive security posture, the Teams – App Only Permissions application intentionally denies access to certain features that require broader or delegated privileges. When using this application, the following capabilities are not available: Channel settings migration during the Teams Provision task Archiving the source Team with the SharePoint site set to read only Collecting statistics using the Advanced option on the source tenant These limitations are a direct result of maintaining application only access and avoiding elevation of privileges. For many compliance driven organizations, this is a deliberate and acceptable trade off. Choosing the Right Consent Model Quest On Demand Migration continues to offer multiple consent models so customers can choose the approach that best aligns with their technical and organizational requirements. Need maximum fidelity and advanced features? Teams – Minimal utilizes a broader permission model to meet expectations. Need to align and comply with stricter compliance rules and a smaller footprint? Teams – App Only Permissions provides a secure, purpose built option. Our goal is not to dictate a single approach, but to enable an informed choice. Advancing Secure Migrations This release reflects our ongoing commitment to: Evolving with Microsoft’s security and identity model Supporting real world compliance requirements Giving customers control over how migrations are executed As security expectations continue to rise, migration tools must evolve alongside them. This new application for On Demand Migration is another step toward making secure, compliant Microsoft 365 migrations not just possible but practical. Learn More You can find and learn more about configuring and using Teams – App Only Permissions in On Demand Migration in our official User Guide & Permissions Reference guide, here: https://support.quest.com/on-demand-migration/current/technical-documentsODMDelegatedpermissionsMigrationTeams MigrationQuest® On Demand MigrationapplicationNew Feature SpotlightOn Demand Migrationhttps://www.quest.com/community/on-demand/f/forum/37322/announcement-on-demand-migration-sites-selected-support-for-onedriveTue, 28 Apr 2026 15:11:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:3f2d1aeb-ac8a-43d0-b84d-e3fc6c201ac4gary hughesAnnouncing Support for Sites.Selected for OneDrive Migrations Extending Least ‑ Privilege Security to Personal Data As Microsoft 365 environments continue to mature, security expectations across all workloads are rising. SharePoint and Teams migrations have already embraced least ‑ privilege access through support for Sites.Selected, while mailbox migrations rely on RBAC for Exchange to scope access to only what is required. OneDrive migrations, since release of such scoping capabilities in On Demand Migration (ODM), had to continue utilising more broader permissions. This was not due to technical limitations, but because focus was placed on other high ‑ priority improvements within the ODM for OneDrive module. Growing customer and partner demand has now elevated least ‑ privilege access for OneDrive as a priority in its own right. That feedback has driven the next step forward. Quest On Demand Migration has now officially extended support for Sites.Selected to OneDrive migrations, allowing organizations to apply a consistent security and governance model across SharePoint, Teams, Exchange mailboxes, and OneDrive. Why Security Matters for OneDrive OneDrive is often viewed as “personal storage,” but in practice it frequently contains some of the most sensitive data in an organization: Executive working documents Personal and regulated user data Files shared broadly across teams or tenants Legacy content accumulated through years of organic usage While Exchange migrations already leverage RBAC to scope mailbox access, and SharePoint and Teams migrations can be constrained using Sites.Selected, OneDrive migrations historically lacked an equivalent least ‑ privilege model. This created an inconsistent security posture across Microsoft 365 workloads. With the introduction of supported Sites.Selected configurations, that gap is now closed. Official Support for Sites.Selected in ODM OneDrive Migrations Quest has completed Quality Assurance validation of OneDrive migrations using Sites.Selected permissions and now officially supports this configuration in On Demand Migration. This means customers can adopt this approach with confidence, benefiting from: Supported and validated configurations Predictable migration behavior Clear troubleshooting and escalation paths The resulting security, compliance, and operational benefits mirror those already available when migrating SharePoint sites, Teams content, and Exchange mailboxes. What Is Sites.Selected (and How It Applies to OneDrive)? Sites.Selected is a Microsoft Graph application permission that allows administrators to grant access only to explicitly approved SharePoint sites, rather than permitting tenant ‑ wide access. Because each OneDrive is backed by an individual SharePoint site collection, the same permission model can be used to precisely control which OneDrive sites are accessible during a migration. Benefits of Using Sites.Selected for OneDrive Migrations Stronger Security for Personal Data Access is limited to explicitly approved OneDrive sites No tenant ‑ wide SharePoint permissions are required Reduced exposure of personal and business ‑ critical files Improved Compliance and Governance Consistent least ‑ privilege model across Exchange, SharePoint, Teams, and OneDrive Better alignment with internal security and privacy standards Reduced risk of over ‑ privileged migration tooling More Granular Control Explicit selection of OneDrive sites included in scope Clear visibility into what the application can access Easier validation prior to migration execution Easier Auditing and Cleanup Clear audit trail for migration access Simple removal of permissions once migration completes No lingering elevated access post ‑ project Current Setup Experience for OneDrive Today, enabling Sites.Selected for OneDrive migrations requires manual configuration steps. These steps are fully documented in the following knowledge base article: https://support.quest.com/kb/4382683 . This approach is fully supported but involves refining application permissions after initial consent. What’s Coming Next: A Dedicated OneDrive Application To further simplify setup and reduce manual steps, Quest is planning a dedicated On Demand Migration OneDrive application, similar to what exists today for SharePoint. Planned Improvements Application provisioned with Sites.Selected only No need to remove broader permissions post ‑ consent Cleaner, safer, and faster initial setup Planned availability: Q3 2026 This will make least ‑ privilege OneDrive migrations the default path from day one. Concluding Thoughts With official support for Sites.Selected in OneDrive migrations, Quest On Demand Migration now enables a consistent, least ‑ privilege security model across all major Microsoft 365 workloads. Customers no longer need to compromise between migration efficiency and security posture as least privilege is now achievable across SharePoint, Teams, Exchange, and OneDrive using Quest On Demand Migration.ODMpermissionsMigrationQuest® On Demand MigrationSiteSelectedNew Feature SpotlightSites.SelectedLeast‑PrivilegeOneDriveOn Demand Migrationhttps://www.quest.com/community/on-demand/i/ideas/enable-persistent-column-configuration-for-ready-devices-viewTue, 07 Apr 2026 07:24:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:29e6d90c-f0ad-4ad1-9b0e-a15a4921feb4g calzolariCurrently, within the On Demand Migration interface for Devices and Servers > Ready Devices , the column selection resets to default every time a user navigates away or refreshes the page. For migration administrators, specific data points (such as OS version, Last Sync, or specific status flags) are critical for daily monitoring. Having to manually re-select these columns multiple times a day is a significant "productivity drain" and creates an inconsistent user experience. Proposed Improvement: Implement "Sticky" or Persistent settings for the column chooser in the Ready Devices view . The interface should remember the user’s last selected columns and layout per session (or ideally, per user profile). Benefit: This change will streamline the migration workflow, reduce repetitive manual tasks, and allow administrators to focus on the migration itself rather than re-configuring their workspace.https://www.quest.com/community/on-demand/f/forum/37224/meeting-link-migration-issue/86337Tue, 17 Mar 2026 09:54:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:6517f8a5-7a6c-4982-a3fb-9267e756dfdealexdanapurI've seen this happen before - sometimes the 'processing' of meeting updates gets suppressed during migration to avoid 'invite storms.' Have you checked the migration project settings to see if 'Send notifications to attendees' was toggled off? If the logs in Exchange show the update but no outbound mail, it’s usually a setting in the migration tool itself or a throttle on the tenant side.https://www.quest.com/community/on-demand/f/forum/37245/enable-qasunixgroup-access-is-denied/86327Fri, 13 Mar 2026 18:56:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:d018f108-8d65-42d1-9013-299776bdea5bJohnnyQuestAlso note that the product is now known as Safeguard Authentication Services. Here's a current article on the Powershell module.https://www.quest.com/community/on-demand/f/forum/37245/enable-qasunixgroup-access-is-denied/86326Fri, 13 Mar 2026 18:36:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:bb4effee-bcb2-4960-984f-a4d78a2587dfJohnnyQuestWhen you launch your Powershell window, make sure you do so using "Run As Administrator" Also, if that doesn't work, try loading the module and executing the command in a **32-bit** Powershell window. Don't forget to use "Run As Administrator" once again.https://www.quest.com/community/on-demand/f/forum/37229/calendar-repair-assistant/86321Thu, 12 Mar 2026 06:27:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:a3784b28-0f7e-4e21-ac9f-155cd7c7ba49alexdanapurFrom what I’ve seen, the Calendar Repair Assistant (CRA) usually runs in the background and tries to fix mismatches between the organizer’s and attendee’s calendars. If a meeting exists on one side but not the other, CRA may recreate or update it automatically. If you’re seeing unexpected meeting updates or items reappearing, it’s often because a meeting was deleted instead of being declined, so CRA assumes it was removed by mistake and restores it. In migration scenarios some admins temporarily disable CRA with PowerShell to avoid these conflicts and then enable it again later.https://www.quest.com/community/on-demand/f/forum/37245/enable-qasunixgroup-access-is-deniedWed, 11 Mar 2026 18:02:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:8035d7c2-6653-4766-ac45-033f0a35da80matt cengicHello. I am trying to run the command Enable-QasUnixGroup (part of the Quest.AuthenticationServices powershell module) and receiving the error "access is denied". The group I am running it against was created by the same account I'm using to run this command. I am unsure of what additional permissions may be needed or what other things I should check. My company apparently does not have any documentation on any internal setup relating to this, so I've just gone by the documentation, which is "Enable-QasUnixGroup -Identity 'group_name_here'"qasPowershellqasunixgrouphttps://www.quest.com/community/on-demand/f/forum/37238/entra-to-entra-tenant-migrationTue, 10 Mar 2026 12:28:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:cc350405-f618-4c99-b8e6-489b1442daf0patrick mcaneneyIs there any documentation for entra joined devices migrating from one tenant to another tenant. Entra to Entra tenant migration. I can only seem to find from active directory to entra. Thank you!https://www.quest.com/community/on-demand/f/forum/37232/teams-personal-chats/86310Wed, 04 Mar 2026 17:07:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:b802e73c-67fd-4a8f-a01d-6f3babbeb859Douglas.RainHello rstevenson , With ODM you would need to ensure the accounts are discovered and matched to be able to access the Teams module in ODM and discover the users chats. When creating a migration task for chats email is not a blocker however OneDrive can be unless you click the checkbox to "Skip OneDrive status check" The following is the descript for this option. Select this option to migrate Chat messages irrespective of the value of the OneDrive Status column in the Chats list view. This can be used when OneDrive accounts are migrated by tools other than On Demand Migration. Links to OneDrive files attached to chat messages will work when the OneDrive account has been migrated and the files are successfully migrated to the OneDrive account in the target tenant. Thanks, Doughttps://www.quest.com/community/on-demand/f/forum/37232/teams-personal-chatsTue, 03 Mar 2026 19:30:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:45783f5b-5d9c-40ec-b4d8-c6620a06a31erstevensonWe have a situation where BiTTitan is being used for mail/onedrive migration. The Teams personal chats were also going to be migrated using BT, but there's some issue they're having that still needs to be resolved, so that's not an option right now. If we use ODM for the Teams personal chat, that means we would also have to migrate the mailbox and onedrive again but with ODM, correct? Even though that part of the migration has been done with BT? Thanks, Richhttps://www.quest.com/community/on-demand/f/forum/37229/calendar-repair-assistant/86308Fri, 27 Feb 2026 15:04:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:841589bb-c7ca-478b-88f5-5bb4e0b4714fDouglas.RainHello rstevenson , It is best to disable the Calendar Repair Assistant to avoid issues during mail migrations and enable it once the mail migrations have completed. We have a few knowledgebase articles below on this subject. https://support.quest.com/on-demand-migration/kb/4376081/odm-your-meeting-was-found-to-be-out-of-date-and-has-been-automatically-updated https://support.quest.com/on-demand-migration/kb/4286933/inconsistencies-caused-by-cra Thanks, Doughttps://www.quest.com/community/on-demand/f/forum/37229/calendar-repair-assistantThu, 26 Feb 2026 18:08:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:12ebdd99-8738-48c7-9a9f-da47c93e74f6rstevensonIs it still recommended to disable the Calendar Repair Assistant when using On Demand for tenant to tenant mail migrations? I didn't see it mentioned in the docs. Thanks!https://www.quest.com/community/on-demand/f/forum/37224/meeting-link-migration-issue/86302Wed, 25 Feb 2026 15:39:00 GMT5f2f4fa7-ebc7-4803-900c-42d427844a5e:d197c220-2510-4775-84ff-b1db20e734bbDouglas.RainHello kevin bogerd , When cancelling the meeting the amil client would handle the sending of the cancellation email. If the email is not reaching the attendees mailbox and spam/junk were already checked, perhaps Exchange Online could be checked by admins to determine if there was any failures attempting to send the cancellation and new meeting. If there is no issues found then I would suggest opening a Quest Support case to have an engineer review. You can open a support case here - https://support.quest.com/create-service-request . Please provide the task diagnostics when opening the task to speed up the investigation. If you have not done this for a support case prior, this article describes the process to get the task details for support. https://support.quest.com/on-demand-migration/kb/4241838/how-to-provide-odm-information-to-quest-support-for-migration-troubleshooting-4241838 Thanks, Doug