NOW Virtual Agent / ServiceNow for Microsoft 365/Teams Does not respondSummaryNOW Virtual Agent / ServiceNow for Microsoft 365/Teams stopped working suddenly. If you had followed the steps in ServiceNow doc as per this here, then you are most probably a victim of new changes made by Microsoft to Teams admin center, see below. If you did not do this step, then the below is not for you! This is due to a recent change in Microsoft Admin Center. Microsoft moved from "App permission policies" to a newer "App centric management". When you go to admin.teams.microsoft.com and open -> Teams apps -> Permission policies and if you see the below update from Microsoft, this is most probably their recent push to upgrade all the AZURE/Entra tenant's with newer features/functionalities The problem is due to "Now virtual agent" being in blocked state, after the newer functionality change, this is affecting all the customers. We are working with Microsoft to get this addressed, since this a REGRESSION caused by their latest update. See documentation pertaining to the newer policy changes. Resolutions Option 1: Temporary relief Until Microsoft gets back with a solution, we will have to just UNBLOCK the already BLOCKED "Now Virtual agent", follow these steps From admin.teams.microsoft.com and open -> Teams apps -> Manage apps page.Go to "Now virtual agent" app and unblock the app, make sure from "User and groups" tab "Available to" is set to either everyone or specific users or groups. Keeping it "No one" will not work.After this change is made, wait for 24-48 hours for the changes to be pushed across the tenant and all the users to get the update. Now ping a message in the BOT, the BOT should respond post these changes. Option 2: Custom BOT Create a Custom BOT and integrate with ServiceNow. Follow the below process and for MANIFEST go to the second link, do not download manifest from the BOT integration page. Creating a custom BOT: https://docs.servicenow.com/bundle/utah-servicenow-platform/page/administer/virtual-agent/concept/va-integ-single-teams.htmlDownload ServiceNow For Teams manifest (pre-published apps): https://docs.servicenow.com/bundle/utah-employee-service-management/page/product/sn-teams/task/download-manifest-file-mt.html - Make sure you choose the right BOT, created in the step above Note: Update from Microsoft Microsoft has fixed the issue and this should be working as expected in customers tenant without any changes required. Technical Details: Before Fix: If two apps, App A1 and App A2 share the same bot B1, then if admin blocks app A1 for the entire org, due to ACM migration the bot B1 is blocked resulting in blocked notifications for App A2 as well. After Fix: Even if one of the apps A1 or A2 is blocked which shares the same bot B1, the bot notifications will continue to work as one of the apps is still unblocked.