Integrate MS apps in MS teams hosted in another cloud
I recently joined a new organisation where PowerBI and Jira are used via a third party vendor and hosted on a different Azure cloud than our office 365. Is it still possible to connect those apps in Teams? Or will this only work when all apps are located in the same cloud/organization?
Issues with placing a call revolving around response error 410 or 487
Hi, if anyone has any insight or has ever experienced a similar issue i would be more than grateful for any tips or help. The issue our users are experiencing is the following: when placing a call to a colleague, the first call placed to that person fails with a message "We couldn't connect your call" or sometimes with "Oops, something went wrong". If the call is placed again, it goes through without issues. When checking for errors in admin center, i stumbled upon 2 response codes. It is either 487 or 410. I gather these are probably SIP codes, however the explanations are somewhat ambiguous to me: 410 Gone The user existed once, but is not available here any more 487 Request Terminated Request has terminated by bye or cancel Issues appear only with direct calls, not with any other function of Teams. So far we tested via Direct Access network, VPN and in internal LAN, however there doesn't seem to be a pattern network wise. It also doesn't seem to be related to OS version or office version, as both users with older version of Windows 10 and Office 2016 and those with newer versions and O365 have similar issues. The issue also seems to be somewhat escalating over the last 10 days, but we are already trying to establish, if any changes happened over this period of time that would would affect the system. So as i said, if anyone has any idea, how to go about trying to trouble shoot this, any help would be greatly appreciated. BR
Teams connectivity issues due to missing DNS PTR records
Hi there, All of the Internet traffic from my corporate LAN has to traverse a web proxy, including traffic to Teams. Our web proxies allow connections to all URLs listed in the “Office 365 URLs and IPs” website but we can't have IP addresses in the web proxy allowed ACL. We have noticed that Teams P2P calls are intermittently failing and after investigation we have found that some of the IP addresses that Teams is trying to connect don't have a DNS PTR record. The web proxy whitelist validation does a DNS lookup when the connection is made to an IP address and if it can resolve a name for the IP address, it will check if that name/URL is in the whitelist, therefore allowing the connection. If the IP address can’t be resolved to a name then the connection is blocked because the web proxy can't validate if that is in the allowed list or not 😉 Using the Teams Network Assessment Tool (https://docs.microsoft.com/en-us/microsoftteams/3-envision-evaluate-my-environment) I can see that TCP/HTTPs connection fails against 4 IP address ranges because those IPs don't have a PTR record - see details below, which is why Teams P2P calls are intermittently failing. I’m fully aware that P2P calls should be using UDP traffic and I’m working with my network team to allow UDP traffic from all of the different subnets we have, but I’m also wondering what else might be intermittently failing given that Teams can’t successfully establish a TCP/HTTPs connection to those IP addresses? - See attached file for full result of the Connectivity Analyzer test Is someone reading this message able to raise a request to have PTR records created for those IP ranges, so there is consistency on all addresses that are used by Teams, please? Thank you, Eduardo 13.107.64.2 world.tr.teams.microsoft.com 13.107.65.5 eu.tr.teams.microsoft.com 52.113.192.2 world52.tr.teams.microsoft.com 52.113.193.5 eu52.tr.teams.microsoft.com 52.114.220.1 52-114-220-1.relay.teams.microsoft.com 52.114.220.254 52-114-220-254.relay.teams.microsoft.com 52.114.221.1 52-114-221-1.relay.teams.microsoft.com 52.114.221.254 52-114-221-254.relay.teams.microsoft.com 52.114.222.1 52-114-222-1.relay.teams.microsoft.com 52.114.222.254 52-114-222-254.relay.teams.microsoft.com 52.114.223.1 52-114-223-1.relay.teams.microsoft.com 52.114.223.254 52-114-223-254.relay.teams.microsoft.com 52.114.124.1 52-114-124-1.relay.teams.microsoft.com 52.114.124.254 52-114-124-254.relay.teams.microsoft.com 52.114.125.1 52-114-125-1.relay.teams.microsoft.com 52.114.125.254 52-114-125-254.relay.teams.microsoft.com 52.114.126.1 52-114-126-1.relay.teams.microsoft.com 52.114.126.254 52-114-126-254.relay.teams.microsoft.com 52.114.127.1 52-114-127-1.relay.teams.microsoft.com 52.114.127.254 52-114-127-254.relay.teams.microsoft.com 52.114.62.1 52-114-62-1.relay.teams.microsoft.com 52.114.62.254 52-114-62-254.relay.teams.microsoft.com 52.114.63.1 52-114-63-1.relay.teams.microsoft.com 52.114.63.254 52-114-63-254.relay.teams.microsoft.com 52.114.188.1 PTR doesn't exist 52.114.188.254 PTR doesn't exist 52.114.189.1 PTR doesn't exist 52.114.189.254 PTR doesn't exist 52.114.190.1 PTR doesn't exist 52.114.190.254 PTR doesn't exist 52.114.191.1 PTR doesn't exist 52.114.191.254 PTR doesn't exist