Iniatiate conference call functionality not working and throwing error "Failed to create a meeting - No application access policy found for this app".Issue Customer has integrated Microsoft teams with Servicenow. When they open any incident, click on "Initiate Teams conference call" and trying to add users to start the call, getting the error as ""Failed to create a meeting - No application access policy found for this app".ReleaseSan DiegoCauseCustomer wants the single tenant and have single Azure tenant, but configured multi tenant configuration in servicenow instance.Hence when they try to initiate a conference call, it is looking for the application policy for the client ID in multi tenant configuration which is not there.Resolution- Requested to delete the record created in tenant connections module and setup the above configuration as per the below document.https://docs.servicenow.com/en-US/bundle/tokyo-employee-service-management/page/product/notify2/concept/setup-notify-ms-teams-single-tenant.html- Once they've configured it, customer has another error when they initiate conference call. Error is: "Failed to create meeting - Invalid access token. Please check your credential alias.- Need to provide complete set of API permissions, when provided, it is required to remove token and refetch the token on login again.- Hence deleted the existing tokens under manage tokens module, cleared the cache and when tried to initiate conference call, the conference call has been placed.