Teams Calendar App test now available in Microsoft Remote Connectivity Analyzer

Published 12-18-2020 01:54 PM 5,959 Views
Microsoft

Hi Teams Community,

We're back with another great addition to Support Diagnostics for Microsoft Teams.  @João Loureiro has written our first offering in the Microsoft Remote Connectivity Analyzer, the Teams Calendar App test.   

 

As you know, Teams and Exchange integration needs to be properly configured for users to get the full feature experience in Teams with Calendar functionality.  This new test will help you troubleshoot and test your Exchange On-Premises Hybrid configuration to ensure it's properly setup for Teams users.

 

If you're experiencing issues with the Calendar App missing in Teams, or getting odd error messages in the Teams Meeting Add-in for Outlook like "We couldn't schedule the meeting.  Please try again later." AND you have On-Premises Exchange server, you should use this diagnostic to help you troubleshoot.  

 

To access the new diagnostic, navigate to Microsoft Remote Connectivity Analyzer, select Microsoft Teams, then click on the Microsoft Teams Calendar Tab test.  

 

MRCA_TeamsCalTest.png

 

You'll need to enter valid credentials of an account with an On-Premises Exchange Server mailbox.  Keep in mind your end users can also perform these tests, you do not need to be an Administrator of your tenant.  In some scenarios you'll want to work with your impacted end user to run the tests and collect additional data for Microsoft Support.  

 

At a high level the test checks a couple things:

  • The user is licensed and fully provisioned for Teams
  • The user's mailbox is accessible via Exchange Web Services (EWS)
  • We can get items from the user's Calendar

You'll also want to go over the following documents carefully when configuring your environment or troubleshooting these issues:

How Exchange and Microsoft Teams interact

Configuring Teams calendar access for Exchange on-premises mailboxes

Troubleshoot Microsoft Teams and Exchange Server interaction issues

 

Please give the new diagnostic a try if you're using Exchange Server On-Premises and having trouble with Teams users' Calendar apps or Outlook add-ins for Teams Meetings and let us know if it helped?

 

Thanks!
Microsoft Teams Support

5 Comments
Occasional Visitor

Unfortunately it just says "User mailbox is marked as undiscoverable by Teams middle-tier service." and i had that already from Teams Logs "isMailboxDiscoverable: false"

So some info from the backend where it failed would be great to investigate further e.g. host xy.acme.com/Autodiscover returned 5xx or invalid cert etc.

I'm already through all the articles like Troubleshoot Microsoft Teams and Exchange Server interaction issues - Microsoft Teams | Microsoft Do... +removed preauth completely from ReverseProxy, checked IIS logs (autodiscover.json success from Useragent SkypeSpaces), disabled/enabled OAuth on VDir, ...

Weird is: Test-HMAEAS.ps1 returns "mail.acme.com and invalid certificate" at the end which is weird as that name is unrelated to Exchange and the old decomissioned MX mailflow/http redirect to website <- is there some guessing machanism that has this as a fixed name? (trying to have the customer delete the DNS records)

Two other things i feel are special about this customer to my others:
1) we switched from modern Hybrid to Classic (for Teams calendar access of OnPrem Mbx)
2) they started with free Teams licenses and are now switching to "O365 business.."
We opened a service request but any more tips would be welcome
But most of all if you increase the debug info, the tool will be the perfect troubleshootingtool to see "what the server is seeing"
Thanks Thorsten
PS: the Autodiscover and EWS tests themselves were successfull so it might "just" be a incorrect Flag that prevents him from trying?
The Office 365 Autodiscover V2 endpoint returned a valid response. -> Request: https://outlook.office365.com/autodiscover/autodiscover.json?Email=jdoe%40acme.com&Protocol=EWS Response: {"Protocol":"EWS","Url":"https://as.acme.com/EWS/Exchange.asmx"}

Exchange Web Services (EWS) service request was successfull. -> Additional Details: GET request URL: https://as.acme.com/EWS/Exchange.asmx Server name: FRAMAIL1

Microsoft

Hi @ThorstenK2 

 

Thank for your feedback. EWS and Rest URL/endpoint are cached by Teams middle tier service. This means Exchange autodiscoverV2 lookup is not performed on every single call preventing exposing additional info from backend. Requests from teams middle tier have specific user agent value 'User-Agent: MicrosoftNinja/1.0 Teams/1.0 (ExchangeServicesClient/0.0.0.0) SkypeSpaces/1.0a$*+' so youc an trace external requests (eventually using IIS failed request tracing) and confirm if they make autodiscover and EWS. If they don't even make Exchange / reverse proxy please review firewall exclusions. If they make Exchagen on-premises but forbidden 403 is returned confirm if oauth was properly configured by running Test-OAuthConnectivity. Last but not least confirm if issue is affecting all users or only a subset as that can eventually be a caching issue if mailbox was recently moved (last 3 days). If these suggestions still don't help and support case still not resolved please provide me support case ID and I can help addressing this issue.

Regular Visitor

hi @ThorstenK2 

Did you ever solve what was the root cause of the issue?

I'm facing an identical error in a new setup, and am kind of stumped what is causing it

 

/mikkel

Occasional Visitor

Test was successful still cant see the calendar tab 

 

Robin_Poulose775_0-1621758203295.png

 

Robin_Poulose775_4-1621758237021.png

 

 

Microsoft

Hi @Robin_Poulose775 

 

In order to help you further I suggest to open support ticket or alternatively provide MRCA test result / user UPN (feel free to send me a message) so i can investigate this further. The API you have highlighted is also tested as part of MRCA Teams Calendar App missing diagnostic. So curious if the problem reproduces while connected to public / home internet connection?

 

João

%3CLINGO-SUB%20id%3D%22lingo-sub-2002698%22%20slang%3D%22en-US%22%3ETeams%20Calendar%20App%20test%20now%20available%20in%20Microsoft%20Remote%20Connectivity%20Analyzer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2002698%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Teams%20Community%2C%3C%2FP%3E%0A%3CP%3EWe're%20back%20with%20another%20great%20addition%20to%20Support%20Diagnostics%20for%20Microsoft%20Teams.%26nbsp%3B%20%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F160794%22%20target%3D%22_blank%22%3E%40Jo%C3%A3o%20Loureiro%3C%2FA%3E%20has%20written%20our%20first%20offering%20in%20the%20Microsoft%20Remote%20Connectivity%20Analyzer%2C%20the%20Teams%20Calendar%20App%20test.%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20you%20know%2C%20Teams%20and%20Exchange%20integration%20needs%20to%20be%20properly%20configured%20for%20users%20to%20get%20the%20full%20feature%20experience%20in%20Teams%20with%20Calendar%20functionality.%26nbsp%3B%20This%20new%20test%20will%20help%20you%20troubleshoot%20and%20test%20your%20%3CSTRONG%3EExchange%20On-Premises%20Hybrid%3C%2FSTRONG%3E%20configuration%20to%20ensure%20it's%20properly%20setup%20for%20Teams%20users.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you're%20experiencing%20issues%20with%20the%20Calendar%20App%20missing%20in%20Teams%2C%20or%20getting%20odd%20error%20messages%20in%20the%20Teams%20Meeting%20Add-in%20for%20Outlook%20like%20%22We%20couldn't%20schedule%20the%20meeting.%26nbsp%3B%20Please%20try%20again%20later.%22%20AND%20you%20have%26nbsp%3B%3CSTRONG%3EOn-Premises%26nbsp%3B%3C%2FSTRONG%3EExchange%20server%2C%20you%20should%20use%20this%20diagnostic%20to%20help%20you%20troubleshoot.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20access%20the%20new%20diagnostic%2C%20navigate%20to%20%3CA%20href%3D%22https%3A%2F%2Ftestconnectivity.microsoft.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMicrosoft%20Remote%20Connectivity%20Analyzer%3C%2FA%3E%2C%20select%20Microsoft%20Teams%2C%20then%20click%20on%20the%20Microsoft%20Teams%20Calendar%20Tab%20test.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22MRCA_TeamsCalTest.png%22%20style%3D%22width%3A%20935px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F241640iB523403EB77A7D83%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22MRCA_TeamsCalTest.png%22%20alt%3D%22MRCA_TeamsCalTest.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou'll%20need%20to%20enter%20valid%20credentials%20of%20an%20account%20with%20an%20On-Premises%20Exchange%20Server%20mailbox.%26nbsp%3B%20Keep%20in%20mind%20your%20end%20users%20can%20also%20perform%20these%20tests%2C%20you%20do%20not%20need%20to%20be%20an%20Administrator%20of%20your%20tenant.%26nbsp%3B%20In%20some%20scenarios%20you'll%20want%20to%20work%20with%20your%20impacted%20end%20user%20to%20run%20the%20tests%20and%20collect%20additional%20data%20for%20Microsoft%20Support.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAt%20a%20high%20level%20the%20test%20checks%20a%20couple%20things%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EThe%20user%20is%20licensed%20and%20fully%20provisioned%20for%20Teams%3C%2FLI%3E%0A%3CLI%3EThe%20user's%20mailbox%20is%20accessible%20via%20Exchange%20Web%20Services%20(EWS)%3C%2FLI%3E%0A%3CLI%3EWe%20can%20get%20items%20from%20the%20user's%20Calendar%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EYou'll%20also%20want%20to%20go%20over%20the%20following%20documents%20carefully%20when%20configuring%20your%20environment%20or%20troubleshooting%20these%20issues%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Fexchange-teams-interact%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EHow%20Exchange%20and%20Microsoft%20Teams%20interact%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fconfiguring-teams-calendar-access-for-exchange-on-premises%2Fba-p%2F1484009%22%20target%3D%22_blank%22%3EConfiguring%20Teams%20calendar%20access%20for%20Exchange%20on-premises%20mailboxes%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoftteams%2Ftroubleshoot%2Fknown-issues%2Fteams-exchange-interaction-issue%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ETroubleshoot%20Microsoft%20Teams%20and%20Exchange%20Server%20interaction%20issues%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPlease%20give%20the%20new%20diagnostic%20a%20try%20if%20you're%20using%20Exchange%20Server%20On-Premises%20and%20having%20trouble%20with%20Teams%20users'%20Calendar%20apps%20or%20Outlook%20add-ins%20for%20Teams%20Meetings%20and%20let%20us%20know%20if%20it%20helped%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks!%3CBR%20%2F%3EMicrosoft%20Teams%20Support%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-2002698%22%20slang%3D%22en-US%22%3E%3CP%3ENew%20Diagnostic%20for%20Teams%20and%20Exchange%20Interaction%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2002698%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%20Add%20in%20for%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETeams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2005857%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Calendar%20App%20test%20now%20available%20in%20Microsoft%20Remote%20Connectivity%20Analyzer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2005857%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EUnfortunately%20it%20just%20says%20%22User%20mailbox%20is%20marked%20as%20undiscoverable%20by%20Teams%20middle-tier%20service.%22%20and%20i%20had%20that%20already%20from%20Teams%20Logs%20%22isMailboxDiscoverable%3A%20false%22%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ESo%20some%20info%20from%20the%20backend%20where%20it%20failed%20would%20be%20great%20to%20investigate%20further%20e.g.%20host%20xy.acme.com%2FAutodiscover%20returned%205xx%20or%20invalid%20cert%20etc.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EI'm%20already%20through%20all%20the%20articles%20like%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2Fmicrosoftteams%2Ftroubleshoot%2Fknown-issues%2Fteams-exchange-interaction-issue%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ETroubleshoot%20Microsoft%20Teams%20and%20Exchange%20Server%20interaction%20issues%20-%20Microsoft%20Teams%20%7C%20Microsoft%20Docs%2C%3C%2FA%3E%26nbsp%3B%2Bremoved%20preauth%20completely%20from%20ReverseProxy%2C%20checked%20IIS%20logs%20(autodiscover.json%20success%20from%20Useragent%20SkypeSpaces)%2C%20disabled%2Fenabled%20OAuth%20on%20VDir%2C%20...%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EWeird%20is%3A%20Test-HMAEAS.ps1%20returns%20%22mail.acme.com%20and%20invalid%20certificate%22%20at%20the%20end%20which%20is%20weird%20as%20that%20name%20is%20unrelated%20to%20Exchange%20and%20the%20old%20decomissioned%20MX%20mailflow%2Fhttp%20redirect%20to%20website%20%26lt%3B-%20is%20there%20some%20guessing%20machanism%20that%20has%20this%20as%20a%20fixed%20name%3F%20(trying%20to%20have%20the%20customer%20delete%20the%20DNS%20records)%3C%2FP%3E%3CP%3ETwo%20other%20things%20i%20feel%20are%20special%20about%20this%20customer%20to%20my%20others%3A%3CBR%20%2F%3E1)%20we%20switched%20from%20modern%20Hybrid%20to%20Classic%20(for%20Teams%20calendar%20access%20of%20OnPrem%20Mbx)%3CBR%20%2F%3E2)%20they%20started%20with%20free%20Teams%20licenses%20and%20are%20now%20switching%20to%20%22O365%20business..%22%3CBR%20%2F%3EWe%20opened%20a%20service%20request%20but%26nbsp%3Bany%20more%20tips%20would%20be%20welcome%3CBR%20%2F%3EBut%20most%20of%20all%20if%20you%20increase%20the%20debug%20info%2C%20the%20tool%20will%20be%20the%20perfect%20troubleshootingtool%20to%20see%20%22what%20the%20server%20is%20seeing%22%3CBR%20%2F%3EThanks%20Thorsten%3CBR%20%2F%3E%3CSTRONG%3EPS%3A%20the%20Autodiscover%20and%20EWS%20tests%20themselves%20were%20successfull%20so%20it%20might%20%22just%22%20be%20a%20incorrect%20Flag%20that%20prevents%20him%20from%20trying%3F%3C%2FSTRONG%3E%3CBR%20%2F%3E%3CSPAN%20class%3D%22css-137%22%3EThe%20Office%20365%20Autodiscover%20V2%20endpoint%20returned%20a%20valid%20response.%20-%26gt%3B%26nbsp%3B%3C%2FSPAN%3ERequest%3A%20%3CA%20href%3D%22https%3A%2F%2Foutlook.office365.com%2Fautodiscover%2Fautodiscover.json%3FEmail%3Djdoe%2540acme.com%26amp%3BProtocol%3DEWS%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Foutlook.office365.com%2Fautodiscover%2Fautodiscover.json%3FEmail%3Djdoe%2540acme.com%26amp%3BProtocol%3DEWS%3C%2FA%3E%20Response%3A%20%7B%22Protocol%22%3A%22EWS%22%2C%22Url%22%3A%22%3CA%20href%3D%22https%3A%2F%2Fas.acme.com%2FEWS%2FExchange.asmx%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fas.acme.com%2FEWS%2FExchange.asmx%3C%2FA%3E%22%7D%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22css-137%22%3EExchange%20Web%20Services%20(EWS)%20service%20request%20was%20successfull.%20-%26gt%3B%26nbsp%3B%3C%2FSPAN%3EAdditional%20Details%3A%20GET%20request%20URL%3A%20%3CA%20href%3D%22https%3A%2F%2Fas.acme.com%2FEWS%2FExchange.asmx%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fas.acme.com%2FEWS%2FExchange.asmx%3C%2FA%3E%20Server%20name%3A%20FRAMAIL1%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2020792%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Calendar%20App%20test%20now%20available%20in%20Microsoft%20Remote%20Connectivity%20Analyzer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2020792%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F908170%22%20target%3D%22_blank%22%3E%40ThorstenK2%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThank%20for%20your%20feedback.%20EWS%20and%20Rest%20URL%2Fendpoint%20are%20cached%20by%20Teams%20middle%20tier%20service.%20This%20means%20Exchange%20autodiscoverV2%20lookup%20is%20not%20performed%20on%20every%20single%20call%20preventing%20exposing%20additional%20info%20from%20backend.%20Requests%20from%20teams%20middle%20tier%20have%20specific%20user%20agent%20value%20'User-Agent%3A%20MicrosoftNinja%2F1.0%20Teams%2F1.0%20(ExchangeServicesClient%2F0.0.0.0)%20SkypeSpaces%2F1.0a%24*%2B%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3E'%20so%20youc%20an%20trace%20external%20requests%20(eventually%20using%20IIS%20failed%20request%20tracing)%20and%20confirm%20if%20they%20make%20autodiscover%20and%20EWS.%20If%20they%20don't%20even%20make%20Exchange%20%2F%20reverse%20proxy%20please%20review%20firewall%20exclusions.%20If%20they%20make%20Exchagen%20on-premises%20but%20forbidden%20403%20is%20returned%20confirm%20if%20oauth%20was%20properly%20configured%20by%20running%20Test-OAuthConnectivity.%20Last%20but%20not%20least%20confirm%20if%20issue%20is%20affecting%20all%20users%20or%20only%20a%20subset%20as%20that%20can%20eventually%20be%20a%20caching%20issue%20if%20mailbox%20was%20recently%20moved%20(last%203%20days).%20If%20these%20suggestions%20still%20don't%20help%20and%20support%20case%20still%20not%20resolved%20please%20provide%20me%20support%20case%20ID%20and%20I%20can%20help%20addressing%20this%20issue.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CDIV%20class%3D%22content-container%22%3E%0A%3CDIV%20id%3D%22section_compact%22%20class%3D%22hidden%22%3E%0A%3CTABLE%20border%3D%221%22%20cellspacing%3D%220%22%20cellpadding%3D%220%22%3E%0A%3CTBODY%3E%0A%3CTR%20class%3D%22alt%22%3E%0A%3CTD%3EMicrosoftNinja%2F1.0%20Teams%2F1.0%20(ExchangeServicesClient%2F0.0.0.0)%20SkypeSpaces%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3CDIV%20class%3D%22content-container%22%3E%0A%3CDIV%20id%3D%22section_compact%22%20class%3D%22hidden%22%3E%0A%3CTABLE%20border%3D%221%22%20cellspacing%3D%220%22%20cellpadding%3D%220%22%3E%0A%3CTBODY%3E%0A%3CTR%20class%3D%22alt%22%3E%0A%3CTD%3EUser-Agent%3A%20MicrosoftNinja%2F1.0%20Teams%2F1.0%20(ExchangeServicesClient%2F0.0.0.0)%20SkypeSpaces%2F1.0a%24*%2B%3CDIV%20class%3D%22content-container%22%3E%0A%3CDIV%20id%3D%22section_compact%22%20class%3D%22hidden%22%3E%0A%3CTABLE%20border%3D%221%22%20cellspacing%3D%220%22%20cellpadding%3D%220%22%3E%0A%3CTBODY%3E%0A%3CTR%20class%3D%22alt%22%3E%0A%3CTD%3EUser-Agent%3A%20MicrosoftNinja%2F1.0%20Teams%2F1.0%20(ExchangeServicesClient%2F0.0.0.0)%20SkypeSpaces%2F1.0a%24*%2BUser-Agent%3A%20MicrosoftNinja%2F1.0%20Teams%2F1.0%20(ExchangeServicesClient%2F0.0.0.0)%20SkypeSpaces%2F1.0a%24*%2B%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3C%2FTD%3E%0A%3C%2FTR%3E%0A%3C%2FTBODY%3E%0A%3C%2FTABLE%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2159178%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Calendar%20App%20test%20now%20available%20in%20Microsoft%20Remote%20Connectivity%20Analyzer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2159178%22%20slang%3D%22en-US%22%3E%3CP%3Ehi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F908170%22%20target%3D%22_blank%22%3E%40ThorstenK2%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDid%20you%20ever%20solve%20what%20was%20the%20root%20cause%20of%20the%20issue%3F%3C%2FP%3E%3CP%3EI'm%20facing%20an%20identical%20error%20in%20a%20new%20setup%2C%20and%20am%20kind%20of%20stumped%20what%20is%20causing%20it%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%2Fmikkel%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2378792%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Calendar%20App%20test%20now%20available%20in%20Microsoft%20Remote%20Connectivity%20Analyzer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2378792%22%20slang%3D%22en-US%22%3E%3CP%3ETest%20was%20successful%20still%20can%20see%20the%20calendar%20tab%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Robin_Poulose775_0-1621758203295.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F282930iAD89897F77CAFBD6%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22Robin_Poulose775_0-1621758203295.png%22%20alt%3D%22Robin_Poulose775_0-1621758203295.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Robin_Poulose775_4-1621758237021.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F282934i29AC74BD2B646429%2Fimage-size%2Fmedium%3Fv%3Dv2%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22Robin_Poulose775_4-1621758237021.png%22%20alt%3D%22Robin_Poulose775_4-1621758237021.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2379059%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Calendar%20App%20test%20now%20available%20in%20Microsoft%20Remote%20Connectivity%20Analyzer%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2379059%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1060969%22%20target%3D%22_blank%22%3E%40Robin_Poulose775%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20order%20to%20help%20you%20further%20I%20suggest%20to%20open%20support%20ticket%20or%20alternatively%20provide%20MRCA%20test%20result%20%2F%20user%20UPN%20(feel%20free%20to%20send%20me%20a%20message)%20so%20i%20can%20investigate%20this%20further.%20The%20API%20you%20have%20highlighted%20is%20also%20tested%20as%20part%20of%20MRCA%20Teams%20Calendar%20App%20missing%20diagnostic.%20So%20curious%20if%20the%20problem%20reproduces%20while%20connected%20to%20public%20%2F%20home%20internet%20connection%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJo%C3%A3o%3C%2FP%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎Dec 18 2020 01:54 PM
Updated by: