User Profile
Jack_Chen1780
Brass Contributor
Joined 5 years ago
User Widgets
Recent Discussions
Re: Microsoft Teams Network Assessment Tool always fail
run the same test from a Azure VM with full Internet access, and got same error. "Relay connectivity and Qos (Media Priority) check is successful for all relays. Please ensure your firewall allows connections to the following domains: *.cc.skype.com Please check if IP 52.114.201.11 is reachable using HTTP Service verifications failed." Maybe the tool is outdated?Re: Microsoft Teams Network Assessment Tool always fail
here is the command line output: C:\Program Files (x86)\Microsoft Teams Network Assessment Tool>NetworkAssessmentTool.exe Microsoft Teams - Network Assessment Tool Starting Relay Connectivity Check: UDP, PseudoTLS, FullTLS, HTTPS connectivity will be checked to this relay (VIP) FQDN: worldaz.tr.teams.microsoft.com If user wants to check connectivity to a particular relay (VIP) IP, please specify in NetworkAssessment.exe.config. Connectivity check source port range: 50000 - 50019 Relay : 52.115.86.6 is the relay load balancer (VIP) Starting Service Connectivity Check: Relay : 52.115.86.6 is reachable using Protocol UDP and Port 3478 Relay : 52.115.86.6 is QOS (Media Priority) enabled Relay : 52.115.86.6 is the relay load balancer (VIP) Relay : 52.115.86.6 is reachable using Protocol PseudoTLS and Port 443 Relay : 52.115.86.6 is the relay load balancer (VIP) Relay : 52.115.86.6 is reachable using Protocol FullTLS and Port 443 Relay : 52.115.86.6 is the relay load balancer (VIP) Relay : 52.115.86.6 is reachable using Protocol HTTPS and Port 443 Relay : 52.115.86.228 is the actual relay instance (DIP) Relay : 52.115.86.228 is reachable using Protocol UDP and Port 3478 Relay : 52.115.86.228 is the actual relay instance (DIP) Relay : 52.115.86.228 is reachable using Protocol UDP and Port 3479 Relay : 52.115.86.228 is the actual relay instance (DIP) Relay : 52.115.86.228 is reachable using Protocol UDP and Port 3480 Relay : 52.115.86.228 is the actual relay instance (DIP) Relay : 52.115.86.228 is reachable using Protocol UDP and Port 3481 Relay connectivity and Qos (Media Priority) check is successful for all relays. Please ensure your firewall allows connections to the following domains: *.cc.skype.com Please check if IP 52.114.201.15 is reachable using HTTP Service verifications failed. More information on Office 365 URLs and IP address ranges can be found at following page. https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2 Service connectivity result has been written to: C:\Users\XXX\AppData\Local\Microsoft Teams Network Assessment Tool\202302150916482595_service_connectivity_check_results.txtMicrosoft Teams Network Assessment Tool always fail
Hi , I am trying to use this Microsoft tool to verify Teams Network connectivity from my office : https://www.microsoft.com/en-us/download/details.aspx?id=103017 But it always showed error: " Starting Service Connectivity Check: Please ensure your firewall allows connections to the following domains: *.cc.skype.com Please check if IP 52.114.201.11 is reachable using HTTP Service verifications failed." It's always the same message, but the IP could change to other 52.114.201.xx IP. The problem is I have no problem to connect to those IP's port 80 and 443. I captured the traffic to 52.114.201.0/24 (attached the capture ) and the communication looks normal: There was TLS handshake and then there are some data transferred via TLS1.2. The server certificate is *.flightproxy.teams.microsoft.com signed by Microsoft ( and I traced DNS and found the real DNS is latm-noam.flightproxy.teams.microsoft.com ). I can access https://latm-noam.flightproxy.teams.microsoft.com/ and confirm the certificate is trusted and signed by "Microsoft RSA TLS CA 02". So I have no idea why the assess tool is complaining 52.114.201.11 is not reachable? Any help is appreciated.having a problem with sysprep on a Azure Windows 10 VM
OS version: 22H2 OS Build 19045.2251 When I run "Sysprep.exe /generalize /oobe /shutdown" , it showed a error : setupact.log has : 2022-12-03 10:31:57, Info SYSPRP ActionPlatform::LaunchModule: Executing method 'ValidateBitLockerState' from C:\Windows\System32\BdeSysprep.dll 2022-12-03 10:31:57, Error SYSPRP BitLocker-Sysprep: BitLocker is on for the OS volume. Turn BitLocker off to run Sysprep. (0x80310039) 2022-12-03 10:31:57, Error SYSPRP ActionPlatform::LaunchModule: Failure occurred while executing 'ValidateBitLockerState' from C:\Windows\System32\BdeSysprep.dll; dwRet = 0x80310039 2022-12-03 10:31:57, Error SYSPRP SysprepSession::Validate: Error in validating actions from C:\Windows\System32\Sysprep\ActionFiles\Generalize.xml; dwRet = 0x80310039 Seems indicate a bitlocker issue. But "manage-bde -status" shows: BitLocker Drive Encryption: Configuration Tool version 10.0.19041 Copyright (C) 2013 Microsoft Corporation. All rights reserved. Disk volumes that can be protected with BitLocker Drive Encryption: Volume C: [Windows] [OS Volume] Size: 126.45 GB BitLocker Version: 2.0 Conversion Status: Fully Decrypted Percentage Encrypted: 0.0% Encryption Method: None Protection Status: Protection Off Lock Status: Unlocked Identification Field: Unknown Key Protectors: Numerical Password Volume E: [DATA] [Data Volume] Size: 255.98 GB BitLocker Version: None Conversion Status: Fully Decrypted Percentage Encrypted: 0.0% Encryption Method: None Protection Status: Protection Off Lock Status: Unlocked Identification Field: None Automatic Unlock: Disabled Key Protectors: None Found Now I have no idea where to troubleshoot.Re: Weird behavior of Exchange Online for none-existing email address
VasilMichev Indeed, It looks like a issue with Exchange Online Canada service, it might have some special rules for Fortimail Cloud. I searched Microsoft Partners and found two partners using Exchange Online and does send 550 for none-existing users : Sherweb.com : MX sherweb-com.mail.protection.outlook.com, Canada. carahsoft.com: MX carahsoft.mail.protection.outlook.com. US. Test result from Fortimail Cloud : Opened a ticket with Fortinet, they are investigating, hopefully they can work it out with Microsoft.Weird behavior of Exchange Online for none-existing email address
I am see a weird behavior of Exchange Online for none-existing email address, wondering if anyone can explain it. I am setting up a Fortimail Cloud service ( third party email protection service ) to Exchange Online, but noticed one function "Recipient address Verification" (using RCPT method) doesn't work as I thought. I did some troubleshooting, my understanding is Fortimail will send a "RCPT TO:" to Exchange Online to verify if the recipient is a valid email. I did traffic capture from Fortimail to Exchange Online : Somehow Exchange Online replied with "250 2.1.5" for the fake email ! But when I do a manual test from a random azure machine, with all the same input, same recipient, Exchange Online return "550 5.4.1" : Now I am really confused why this is happenning. I tested with a second test M365 tenant with a different email domain and it behave same way, the test domain 's MX and TXT SPF record doesn't have any reference to Fortimail Cloud, so there shouldn't be any reason it's treated differently.Re: Endpoint menu missing in security.microsoft.com
John Matrix Did you finally get it resolved? I got the same problem on my dev tenant ( login with global admin account). I have a production tenant with M365 E3 license, and the setting is: But on Dev tenant ( M365 E5 developer without windows and audio conferencing 😞 It's missing endpoints but has email and identities. Maybe because E5 developer doesn't include Windows ?Re: Whiteboard with external participants
I just tested it and whiteboard sharing with external user is kind of working now. https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=In%20development%2CRolling%20out&searchterms=66759 shows: GA April 2022. There are some hops need to go through, whiteboard data need to opt-in to Onedrive for business. Set-SPOTenant -IsWBFluidEnabled $true But there is a big blocker : OneDriveLoopSharingCapability need to be set as ExternalUserAndGuestSharing : Set-SPOTenant -OneDriveLoopSharingCapability ExternalUserAndGuestSharing I found the only way I can change OneDriveLoopSharingCapability is change SharingCapability to ExternalUserAndGuestSharing : Set-SPOTenant -SharingCapability ExternalUserAndGuestSharing But this will change Sharepoint 's global External sharing policy to "Anyone", which is a big security concern. Check https://docs.microsoft.com/en-us/powershell/module/sharepoint-online/set-spotenant?view=sharepoint-ps Would love to know if there is way to enable OneDriveLoopSharingCapability without changing Sharepoint "External Sharing" to anyone.
