3757509 - Joule Integration with Microsoft 365 Copilot Fails with “No Microsoft Tenant ID Specified” Error

• When setting up SAP Joule with Microsoft Copilot, the Joule formation hangs indefinitely with the status 'Synchronizing'.
• When clicking the 'Synchronizing' status and then selecting 'Show Technical Errors' in the popup window, the following log is displayed:
  Synchronization between Joule System das-application-ias and Microsoft 365 Copilot for SAP Joule System Microsoft 365 Copilot
  has failed.
  - Microsoft 365 Copilot for SAP Joule System Microsoft 365 Copilot returned a technical error for assignment with ID
  "Error creating mapping: no microsoft tenant id specified"
  

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental." 

• SAP Business Technology Platform for Cloud Foundry Environment
• Joule AI copilot

joule, Microsoft 365 copilot, formation, booster, system id, tenant id, entra, error creating mapping, no Microsoft tenant id specified, exclude system, resynchronize, mapping, integration, spii Joule, Integration, Microsoft 365, Copilot, Fails, No Microsoft Tenant ID Specified, Error, formation, hangs, Synchronizing, status, popup,  window, click, Show Technical Errors, Synchronization, Joule System, das-application-ias, Microsoft 365 Copilot, failed, assignment, Error creating mapping: no microsoft tenant id specified, create, mapping, system, populating, System ID, booster, delete, deletion, blocked, exclude, resynchronization, proper, configuration, tenant, identification, establishing, successful, BC-CP-MP, Component. , KBA , CA-JOULE-CLT-COP , Joule MS Copilot Client , CA-JOULE-PRV , Provisioning , CA-JOULE , Joule , Problem