Salesforce Outlook Integration add-in

Hi @Dan, 

Thank you for reaching out to the Microsoft Q&A forum.  

The issue you are experiencing is that the Salesforce Outlook Integration add-in is not passing the current meeting recordId into your Salesforce Flow. This typically occurs when the add-in cannot retrieve the meeting context or when configuration settings between Outlook and Salesforce are not fully aligned. 

Please follow the steps below that suit for your situation: 

1/ Start by ensuring the add-in is deployed correctly and permissions are set (Global admin only) 

• In Microsoft 365 Admin Center → Integrated Apps → Salesforce Outlook Integration, confirm:  
  • The add-in is deployed via Centralized Deployment. 
  • ExtensionPoints include:  
    • AppointmentOrganizerCommandSurface 
    • AppointmentAttendeeCommandSurface 
  • Permissions: ReadItem (and if required, ReadWriteItem). 
  • SupportsPinning is enabled for calendar surfaces. 

2/ Then, validate the Outlook client and confirm the meeting context. 

• Since you are using Classic Outlook, start by testing the same action in Outlook on the Web (OWA) to confirm baseline functionality. 
• Ensure the meeting is opened as an occurrence if it is part of a recurring series, and that the user performing the action is the organizer.  

3/ After that, review the Salesforce and Flow configuration settings. 

• In Salesforce Setup:  
  • Confirm Outlook Integration and Sync is enabled. 
  • Check which object the add-in creates when logging (Event or Task) and ensure your Flow trigger matches this. 
• Add a debug step in your Flow to capture incoming variables and verify whether the add-in sends recordId or another field such as targetId or whatId.  

4/ Proceed by applying the latest update to the add-in and pinning it for visibility. 

• Make sure the add-in version matches the latest release in Microsoft AppSource. 
• After updating, restart Outlook and pin the add-in for calendar surfaces so it is always available when opening meetings.  

5/ Finally, confirm authentication and validate policy settings. 

• Ask your Exchange admin to verify:  
  • Modern Authentication is enabled. 
  • No mailbox policy blocks add-in access to calendar items. 
  • OAuth scopes for Office add-ins are active. 
• Ensure the add-in is pinned for calendar read/compose surfaces so users see the Salesforce icon consistently. 

Please understand that our initial response does not always resolve the issue immediately. However, with your help and more detailed information, we can work together to find a solution.   

I hope this information is helpful. Please follow these steps and let me know if it works for you. If not, we can work together to resolve this.    

Thank you for your patience and your understanding. If you have any questions or need further assistance, please feel free to share them in the comments on this post so I can continue to support you. 

I look forward to continuing the conversation.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".   

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.   

To troubleshoot the issue with the Salesforce Outlook Integration add-in not passing the current meeting recordId into your Salesforce flow, you may want to check the following configurations:

1. Add-in Configuration: Ensure that the Salesforce for Outlook add-in is correctly installed and configured. Sometimes, uninstalling and reinstalling the add-in can resolve issues related to configuration.
2. Permissions: Verify that the integration user has the necessary permissions to access and log meeting details in Salesforce. If the integration user does not have the right permissions, it may not be able to pass the required data.
3. Connected App Settings: Check the settings of the connected app in Salesforce. Ensure that the app is properly set up to handle the data being passed from Outlook. This includes confirming that the integration user is approved to access the connected app.
4. Debugging: Since you mentioned that you have debugged with Salesforce, ensure that you are also checking the logs for any errors or warnings that might indicate what is going wrong during the data transfer.
5. Outlook Add-in Updates: Make sure that you are using the latest version of the Salesforce for Outlook add-in. Sometimes, updates can fix bugs or improve functionality.

If these steps do not resolve the issue, consider reaching out to your Outlook/Exchange admin for further assistance, as they may have access to additional tools or logs that can help identify the problem.