Known common issues of Microsoft Teams with Virtual Agent1. Attachment picker not supported on Teams, end users have to copy paste the file. This is known issue from Microsoft Teams. For general Person to Person chat, we see the attachment option is Microsoft Teams but for Now Virtual Agent bot we don't see any attachment option.Normal user conversation: Bot Conversation:So how does image upload control works/ how to workaround this behavior for Microsoft Teams: Microsoft Teams provides copy/paste feature which means that user can copy the image and paste it in the chat. 2) How can customers create a test tenant to test their integration: The Virtual Agent integration with Microsoft Teams creates a one-to-one association between the ServiceNow instance that you are installing from and the Microsoft Teams tenant in which the integration runs. Use a separate Microsoft Teams tenant for each instance that you plan to install the integration in. If you plan to test with a non-production instance and clone the instance, be sure to run the installation steps again on the clone target to associate the bot to the new instance. Running the steps again disassociates the integration between the original non-production instance and the tenant.Issue: Generally customer have multiple ServiceNow instances (QE, Dev, Prod etc) but only have one tenant. The Virtual Agent integration with Microsoft Teams support a one-to-one association between the ServiceNow instance that you are installing from and the Microsoft Teams tenant in which the integration runs. This means that if the customer wants to test the integration with some other instance then they have to override the current integration configuration. But overriding the configuration means that bot will be connected to the new instance instead of the PROD instance.Solution: Instead of using the same tenant, Microsoft Teams provides one option to create a test tenant. Customer can use this option and create a new test tenant to integrate this with ServiceNow test instance. This way we will not alter the PROD configuration and can still test the new/test instance.First join the Developer program using ServiceNow email ID first. Make sure you have required license to join the Microsoft 365 program. https://docs.microsoft.com/en-us/office/developer-program/microsoft-365-developer-program. You will get a subscription that is valid for 90 days free if we keep using bot in this subscription Microsoft auto renews it.Developer 365 subscription (free for Developers) - Follow steps using : https://docs.microsoft.com/en-us/office/developer-program/microsoft-365-developer-program-get-started. Here if you see in Microsoft documentation you will setup an account which has something like xxx@domain.onmicrosoft.com. This gives you access now to create a tenant and in your tenant you can add up to 25 users only.Use an incognito browser window to login to this xxx@domain.onmicrosoft.com , otherwise the chrome browser will keep using Okta and use your ServiceNow email ID.When you are logged in using this account then next step is to Refer to : https://docs.microsoft.com/en-us/microsoftteams/platform/concepts/build-and-test/prepare-your-o365-tenant to create a test tenant.At this point you should have your Test tenant created and your account should have Admin access to test tenant.Add other users to your organization ( in this case developer and QE). This will again issue your users under the tenant - user1@domain.onmicrosoft.comShare the user details and passwords you auto generate with individuals who are working with your test tenant.