Creating Teams Chat via Flow Designer Without Adding Connection UserSummary This article explains why the connection user is automatically added to Microsoft Teams chats created via Flow Designer and how to handle this scenario if your requirement is to exclude the connection user using application-level permissions. Issue When using the "Create Chat" action in a ServiceNow Flow, the user associated with the access token (connection user) is automatically added to the chat in Microsoft Teams. This behavior is undesirable when the requirement is to initiate the chat between other users without the connection user being included. Cause The “Create Chat” action in the Microsoft Teams Spoke includes pre-processing logic that automatically: Retrieves the connection user’s details from the access token.Adds the connection user to the newly created chat. This is a design behavior and cannot be disabled through standard configuration. Solution & Limitations To achieve this, please consider the following: Workaround (Advanced): Duplicate the existing "Create Chat" action.Customize the duplicated action to remove the logic that adds the connection user by default.Use this modified version in your flows.Note: This requires advanced customization and knowledge of IntegrationHub and custom actions. Limitations with Application Permissions: Microsoft Graph API does not support sending messages to chats using application permissions.This means even if you create a chat without the connection user, you cannot send messages to that chat unless the sender is a participant.Therefore, message delivery to that chat will fail. Recommended Approach Continue using delegated permissions for both chat creation and message sending.Use a dedicated service account as the connection user to maintain control and consistency.This approach is Microsoft-supported and ensures all chat operations work reliably.