Demystifying Hybrid Free/Busy: Finding errors and troubleshooting

Published Mar 02 2018 06:59 AM 95.9K Views

In this second part of the Demystifying Hybrid Free/Busy, we will cover troubleshooting of Hybrid Free/Busy scenarios, more specifically – how and where to find an actual error that will indicate where the problem is. Before venturing forth, please make sure that you have seen Part 1 of this demystifying series! Here is the graphics we posted in the previous post; use this as a reference for users that we will be referring to when troubleshooting: FB2_1

Do you really have a Free/Busy issue?

Usually when a user creates a new meeting in Outlook on the web (OWA) or Outlook, clicks on Scheduling Assistant, adds his or her colleague to the meeting, they try to see when the user is available to meet. If they see the hash marks \\\\\\\ instead of seeing if the other user is free or busy, there is an issue. FB2_2 You can often see an error message by hovering over hash marks, however we usually find that the error is not very specific. Instead we would need to take slightly more advanced steps to diagnose the issues by checking things like the Outlook logs, F12 Network tab, or Fiddler. Before getting to actual Free/Busy errors it is worthy to know that there is a Free/Busy test on Remote Connectivity Analyzer, Office 365 tab that can help us with some configuration /functional issues. FB2_3 This Free/Busy test is useful for checking DNS records, Autodiscover and EWS connectivity issues, pre-authentication for Autodiscover or EWS requests. It is, however not a relevant Free/Busy test per se, as it uses Basic authentication and not Federated authentication used in actual Free/Busy lookups. Therefore, don’t be surprised if you see this test as green (successful) but Free/Busy is not working in your Hybrid Organization. FB2_4 I would also like to mention that there is a Free/Busy troubleshooter in Beta version, incorporated into SARA tool (Microsoft Support and Recovery Assistant for Office 365) which you can download it from here : https://diagnostics.outlook.com/#/ Open SARA and select Outlook, click Next, select I’m having problems with my calendar, input email address and password of the source mailbox (cloud mailbox if direction not working is cloud > on-premises) and then select I can’t see when someone is free or busy. FB2_5 Due to underlying complexity of it all, this is not a completely reliable way of determining the cause of free/busy issues in Hybrid Deployments, but it is a good start when troubleshooting. This F/B test from SARA covers mostly cloud to cloud scenarios but I recommend it here because it does connectivity and additional checks on tenant, licensing and Autodiscover.

Where can we see actual Free/Busy error message?

First, we need to understand in which direction we have a lookup problem. Please see Part 1 for discussion of directionality. Sources of logs:

  • Outlook logs
  • OWA F12 Network Tab
  • Fiddler – Outlook and OWA

These steps are important in order for us to see the relevant message error for Free/Busy issues. Once we know the error message, it’s much easier to resolve the issue.

OUTLOOK

Note: you will be able to see the Free/Busy error in plain text in Outlook 2010 logs only, if you are using Outlook 2013/2016, you can’t see the error in the Outlook log and you would need to provide the Outlook ETL log containing the error to Microsoft Support to parse it. You will still be able to use Fiddler to see the Free/Busy error yourself if you have Outlook 2013/2016 or you can use OWA F12 method while reproducing issue in OWA client but that only works if the on-premises Exchange server version is 2013 or above for the Source Mailbox user. For the Outlook F/B error, we need to first enable Outlook logging and after this we will reproduce issue (\\\\\\). After repro, we will collect Outlook logs. 1. Enable Outlook logging: Follow this KB article and check the Enable troubleshooting logging (this requires restarting Outlook) option. Restart Outlook. 2. Reproduce the issue for the non-working direction. Suppose Free/Busy direction not working is cloud to on-premises, logged on as a cloud user, add some on-premises users to a meeting until you see the hash marks (instead of Free/Busy information). You do not need to save or send a meeting request. Note that if Outlook logging is turned on, you will see the following notification in Outlook: FB2_6 Example: In this screenshot, Jane is a cloud user mailbox. Jane logged on to a mailbox using Outlook 2016 and she is creating the meeting (organizer). She adds 3 participants: ex2010mbx1, ex2013mbx1 and Joe – who are all on-premises user mailboxes. Jane cannot see Free/Busy for any of them. FB2_7 3. Collect Outlook logs Outlook 2010: we need the AS.log from %temp%\OlkAS folder (reference here) Open the AS.log and look for the error. FB2_8 (click thumbnail to view larger) Outlook 2013 / 2016: we need Outlook-#####.etl log from %temp%\Outlook Logging folder (reference here). You would need to send the ETL file to Microsoft Support to get it analyzed as we are parsing this log with an internal tool. You might not know this but Hybrid free/busy support cases are free of charge! Of course, you can still use the other methods (fiddler for Outlook/OWA or browser for OWA) to see Free/Busy error yourself, however we (Support) might ask you additionally to get this log as in the Outlook ETL log we have the best logging for the Free/Busy errors.

OWA / Outlook on the web

Cloud OWA F12 Network tab You need to login to OWA as the source mailbox, hit F12 (Developer Tools for browser) and select the Network Tab. You would then lookup Free/Busy for the target mailbox (reproduce the issue). Once you see the hashmarks, look for GetUserAvailabilityInternal Action then look at Response Body to see the error message. Note: The source mailbox needs to be hosted on Exchange 2013 or above in on-premises or in Exchange Online for us to be able to see the error message in OWA using F12. This method will not work for Exchange 2010 source mailboxes. This is how this could look like in Internet Explorer (similar in other browsers): FB2_9 (click thumbnail to view larger) Fiddler – OWA or Outlook You would need to download and install Fiddler tool and reproduce the Free/Busy issue in OWA or Outlook. If you reproduce the problem in OWA, you would search for GetUserAvailabilityInternal Action for owa service.svc entry and then look at JSON /Raw tab to see the error message. If the source mailbox is on Exchange 2010 server, this is what you’ll need to do. OWA View - Fiddler: FB2_10 (click thumbnail to view larger) If you are logged in with Outlook, you would search for GetUserAvailabilityResponse, check the Raw tab and you can click on “View in Notepad” button on the right bottom corner. Outlook view Exchange Online - Fiddler: FB2_11 (click thumbnail to view larger) Outlook view Exchange 2010 Source Mailbox - Fiddler FB2_12 (click thumbnail to view larger) When troubleshooting Free/Busy issues, the following on-premises logs can be very useful, especially for Cloud to On-Premises Free/Busy direction. IIS logs Default Web Site (DWS) %SystemDrive%\inetpub\logs\LogFiles\W3SVC1 Example: C:\inetpub\logs\LogFiles\W3SVC1 Example of Autodiscover and EWS entries with IOC Enabled in IIS W3SVC1 logs: Autodiscover – OAUTH (autodiscover.svc without /WSSecurity)

2016-01-06 17:45:27 10.0.0.5 POST /autodiscover/autodiscover.svc &CorrelationID=<empty>;&ClientId=QNFNHKEEKYENCJITQQ&cafeReqId=7972d1fc-a9d9-44c6-8851-480d3601cbd7; 443 S2S~00000002-0000-0ff1-ce00-000000000000 132.245.65.28 ASAutoDiscover/CrossForest/EmailDomain//15.01.0361.007 200 0 0 109

EWS – OAUTH (exchange.asmx without /WSSecurity)

2016-01-06 17:45:27 10.0.0.5 POST /ews/exchange.asmx &CorrelationID=<empty>;&ClientId=WSIVGUUAUWWRFACJBWDA&cafeReqId=6ce8864c-74a0-4ad2-a3dc-7b69e0415403; 443 <unverified>actas1(sip:joe@contoso.com|smtp:joe@contoso.com|upn:joe@contoso.com) 132.245.65.28 ASProxy/CrossForest/EmailDomain//15.01.0361.007 200 0 0 703

Example of EWS entry with Organization Relationship Enabled in IIS W3SVC1 logs: EWS – DAUTH (exchange.asmx with /WSSecurity)

2016-01-06 18:04:41 10.0.0.5 POST /ews/exchange.asmx/WSSecurity &CorrelationID=<empty>;&ClientId=VOMGJKAWURSVKOXQLBVA&cafeReqId=18fd3a2e-7b1c-4828-8943-6b20912e2e44; 443 - 132.245.65.28 ASProxy/CrossForest/EmailDomain//15.01.0361.007 200 0 0 296

IIS logs Exchange BackEnd (BE) %SystemDrive%\inetpub\logs\LogFiles\W3SVC2 Example: C:\inetpub\logs\LogFiles\W3SVC2 Example of EWS entry with Organization Relationship Enabled (DAUTH) in IIS W3SVC2 logs:

2016-01-06 18:04:41 fe80::f17f:beef:a5e3:7d3c%25 POST /ews/exchange.asmx/WSSecurity - 444 - fe80::f17f:beef:a5e3:7d3c%25 ASProxy/CrossForest/EmailDomain//15.01.0361.007 200 0 0 93

HTTPProxy logs for Autodiscover %ExchangeInstallPath%Logging\HttpProxy\Autodiscover Example: C:\Program Files\Microsoft\Exchange Server\V15\Logging\HttpProxy\Autodiscover Example of Autodiscover entry with Organization Relationship Enabled (DAUTH)

2016-01-06T18:05:20.552Z,bcdfbed5-f11f-4250-a616-e38cb475cd3f,15,0,1104,2,,Autodiscover,autodiscover.contoso.com,/autodiscover/autodiscover.svc /WSSecurity,,,false,,contoso.com,Smtp~joe@contoso.com,ASAutoDiscover/CrossForest/EmailDomain/ /15.01.0361.007,132.245.65.28,exch-2013,200,200,,POST,Proxy,exch-2013.contoso.com,15.00.1104.000,IntraForest,AnchorMailboxHeader-SMTP,[…],BeginRequest=2016-01-06T18:05:20.192Z;CorrelationID=<empty>;ProxyState-Run=None;FEAuth=BEVersion-1941996624;NewConnection=fe80::f17f:beef:a5e3:7d3c%25&0;

HTTPProxy logs for EWS %ExchangeInstallPath%Logging\HttpProxy\Ews Example: C:\Program Files\Microsoft\Exchange Server\V15\Logging\HttpProxy\Ews Example of EWS entry with Organization Relationship Enabled (DAUTH):

2016-01-06T18:04:41.490Z,4757ab2c-8ccc-4d1a-ae39-0780ecc8eabb,15,0,1104,2,{02CD833F-18AB-413A-83CB-0E86F4DA5362},Ews,mail.contoso.com,/ews/exchange.asmx/WSSecurity,,,false,,contoso.com, Smtp~joe@contoso.com,ASProxy/CrossForest/EmailDomain//15.01.0361.007,132.245.65.28,exch-2013,200,200,,POST,Proxy,exch-2013.contoso.com,15.00.1104.000,IntraForest,AnchorMailboxHeader-SMTP,[…],BeginRequest=2016-01-06T18:04:41.380Z;

EWS logs %ExchangeInstallPath%Logging\Ews Example: C:\Program Files\Microsoft\Exchange Server\V15\Logging\Ews Example of EWS entry with Organization Relationship Enabled (DAUTH):

2016-01-06T18:04:41.490Z,4757ab2c-8ccc-4d1a-ae39-0780ecc8eabb,15,0,1104,2,{02CD833F-18AB-413A-83CB-0E86F4DA5362}, External,true,jane@contoso.mail.onmicrosoft.com,, ASProxy/CrossForest/EmailDomain//15.01.0361.007,Target=None;Req=Exchange2012/Exchange2013; ,132.245.65.28,exch-2013,exch-2013.contoso.com,GetUserAvailability,200,12150,,,,,,ebd34d71ac7342c19d947d881db4ad55,f866c73e-6c91-475e-bdec-0428bdeaa423,PrimaryServer; Requester=jane@contoso.mail.onmicrosoft.com; Failures=0

Event Viewer Application logs on Exchange Server References here and here. Example of Event ID 4002 for MSExchange Availability:

Log Name: Application
Source: MSExchange Availability
Event ID: 4002
Task Category: Availability Service
Level: Error
Description:
Process 4568: ProxyWebRequest CrossSite from S-1-5-21-391720751-1508397712-925700815-508779 to https://hybrid.contoso.com/ews/exchange.asmx failed. Caller SIDs: NetworkCredentials. The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException: System.Web.Services.Protocols.SoapException: You have exceeded the available concurrent connections for your account. Try again once your other requests have completed.
at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)

IIS tracing for the error code in the IIS logs Reference here.

Free/Busy errors and fixes

Ray Fong and I made a table (ATTACHED) with the Free/Busy errors encountered so far in Support and their possible resolutions. We cannot cover all possible scenarios and errors even though we have a good-sized list. This is meant to illustrate ways we can resolve specific errors and these suggestions might not work for you even if you have the same error. If you know the exact Free/Busy error that you get and checked configuration as discussed in part 1 of this series, this is already a tremendous progress, and this will help us resolve your issue faster. Of course, you can follow these suggestions on your own as most of the actions are harmless but if you don’t feel confident in troubleshooting on your own or you fear that actions are dangerous or irreversible, please contact us.

Free/Busy Errors discussed in the attached table:

FB_Errors.FixesV6

  1.  “An internal server error occurred. The operation failed”
  2.  "The remote user mailbox must specify the the explicit local mailbox in the header"
  3.  "An error occurred when verifying security for the message"
  4.  "Unable to connect to the remote server"
  5.  “Autodiscover failed for email address <> with error ‘The request failed with HTTP status 404: Not Found’ ”
  6.  “The request failed with HTTP status 401: Unauthorized - The user specified by the user-context in the token is ambiguous”
  7.  "An existing connection was forcibly closed by the remote host - An unexpected error occurred on a receive "
  8.  "An existing connection was forcibly closed by the remote host - An unexpected error occurred on a send ”
  9.  "Configuration information for forest/domain could not be found in Active Directory"
  10.  "Proxy web request failed.,inner exception: The request failed with HTTP status 401: Unauthorized."
  11.  "The response from the Autodiscover service at 'https://autodiscover/autodiscover.svc/WSSecurity' failed due to an error in user setting 'ExternalEwsUrl'. Error message: InvalidUser."
  12.  “The caller does not have access to free/busy data"
  13.  “The request failed with HTTP status 403: Forbidden (The server denied the specified Uniform Resource Locator (URL). “
  14.  “Unable to resolve e-mail address user@notes.domain.com to an Active Directory object”
  15.  “An error occurred when processing the security tokens in the message.”
  16.  “The cross-organization request for mailbox yyy@contoso.com is not allowed because the requester is from a different organization”
  17.  “The request failed with HTTP status 401: Unauthorized - Microsoft.Exchange.Security.OAuth.OAuth TokenRequestFailedException: Missing signing certificate “
  18.  “The application is missing a linked account for RBAC roles, or the linked account has no RBAC role assignments, or the calling users account is logon disabled”
  19.  “The entered and stored passwords do not match“
  20.  “The password has to be changed.”
  21.  “The password for the account has expired” or “Provision is needed before federated account can be logged in”
  22.  “The request timed out”
  23.  “The specified member name is either invalid or empty”
  24.  “The result set contains too many calendar entries”
  25.  “The request failed with HTTP status 401: Unauthorized - The token has an invalid signature.”
  26.  “The request failed with HTTP status 401: Unauthorized - Client assertion contains an invalid signature. [Reason - The key was not found., Thumbprint of key used by client: 'XXX’ “
  27.  “Proxy web request failed., inner exception: Response is not well-formed XML “
  28.  “Failed to communicate with https://login.microsoftonline.com/extSTS.srf., inner exception: Unable to connect to the remote server”
  29.  “Autodiscover failed for E-Mail Address joe@contoso.com with error System.Net.WebException: The remote name could not be resolved: 'mail.contoso.com'”
  30.  “Failed to get ASURL. Error 8004010F”
  31.  “Proxy web request failed. , inner exception: System.Net.WebException: The request failed with the error message: -- &lt;head&gt;&lt;title&gt;Object moved”
  32.  “The request was aborted: Could not create SSL/TLS secure channel.”
  33. “The user specified by the user-context in the token does not exist.";error_category="invalid_user“
  34.  “The hostname component of the audience claim value 'https://<hybrid.domain.com>’ is invalid";error_category="invalid_resource“

Thanks to all that contributed to this content: Ray Fong, Nino Bilic, Tim Heeney, Greg Taylor and Brian Day. Mirela Buruiana

60 Comments
Senior Member

Ciao Mirela

I have an Exchange Hybrid Deployment (with Exchange 2016)

Everything was working fine, but after we have switched the publication on Web Application Proxy, the availability stopt to work.

All the services are published in Pass trough and all the other exchange services are ok autodiscover included.

There some settings that we have to check on the WAP server?

Thank you

Michele Foffano

Microsoft

Ciao Michele,

We would need the Free/Busy error for the affected direction. Assuming it is cloud to on-premises, check the error with Fiddler or OWA F12 (look at GetUserAvailability* as explained above) and check Get-IntraOrganizationConnector and Get-OrganizationRelationship settings in Cloud. And also on exrca.com the free/busy test under O365 for Cloud user to OnPrem user (assuming direction is cloud -> onprem). This will say if pass through is there indeed at least for Basic Auth (what exrca tests now) and other things like ports , certificates. Could be also a TLS issue, I cannot guess, so we need the F/B error message and you can also check the most common errors here: FB_Errors.FixesV6

Microsoft

For everyone: my name is Mirela Buruiana and I am the main author of this blog. Reply to this comment if you want me to get notified about your question /comment.

Senior Member

Hi Mirela,

quering Get-IntraOrganizationConnector we have noticed that the discovery endpoint URL is  https://webmail.domain.com/autodiscover/autodiscover.svc.

On the Web Application Proxy server we have published all the services individually :

We didn't pubblish the url https://webmail.domain.com/autodiscover .

This was the problem  :smile:

do you know if on the WAP services we can publish the root URL https://webmail.domain.com/ ?

or we must create a pubblication for every service?

 

Thank you for your help

best regards

Ciao

Michele

 

Microsoft

Hi Michele, I don't know WAP :) but you can change the Discovery endpoint on the IOC to autodiscover.domain.com. Unfortunately, HCW by default sets the discoveryEndpoint to the EWS Fqdn /autodiscover . 

New Contributor

I am having a free busy issue from Cloud to On-Prem, I've run the free/busy test from EXRCA and all results show that the mailbox is accessible, the trace shows calendar info but testing from a cloud account (OWA) to on-prem does not return results. If the EXRCA works what else should I look at. Is this a permission error?

Microsoft

 

check  "Where can we see actual Free/Busy error message?", look at OWA F12 method or Fiddler and search for GetUserAvailability call as shown above in the blog.
Once you get the error message, check the PDF with errors and fixes, see if something similar.
New Contributor

I'm puzzled why The connectivity analyzer shows it all but the actual OWA user it's not working. I would think I'd see some indicator on the report. Thanks for the reply, I'll see if I can see anything in the OWA analysis. I do a lot of hybrids and Free/Busy is the most likely place I run into problems.

Microsoft

RCA test is not accurate. We are working on it.

New Contributor

It's showing data from the mailbox that we are looking to get free/busy data from, I see a list of meetings that should be coming back to the cloud user. So even though I see this it may not be a real result? Blocked from sending back to the OWA user in the cloud?

Microsoft

Sorry for delay, @Robert Styles , can you please retry RCA Free/Busy test now and let me know if there is now an error?

New Contributor

@Mirela_Buru Thanks for looking at this. The free busy actually looked great. We dug a little deeper and found during the scheduling assistant look up we were getting an authentication error... 

 

The hostname component of the audience claim value 'https://email.customer.com' is invalid


It had been a while since the client had run the HCW, and once we ran through that again it repaired the federation and we were immediately able to see free/busy. In these situations I think I'll try that earlier and hopefully save some frustration!

Occasional Visitor
Any thoughts on what the issue is?
 
Performing Free/Busy LookupFree/Busy Lookup failed.
Additional Details
Free/Busy Lookup failed with exception: Proxy web request failed. , inner exception: System.Net.WebException: The request failed with HTTP status 504: Gateway Timeout. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult) at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult) at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, IService service, IAsyncResult asyncResult) at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult) at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()
 
Microsoft

@chris280 , I assume it is from EXO to Exchange onpremises? it fails at ews request and usually network related issues. You need to check httpproxy logs / iis logs to see if the request reaches Exchange when you repro the issue or it is stuck at some network device in front. If you are in Modern Hybrid Topology and your Cloud IntraOrganizationConnector or OrganizationRelationship's TargetSharingEpr is pointing to the Hybrid Agent, you need to see if the agent is active /still installed and your firewall/ proxy is allowing outbound traffic to EXO. You can check the troubleshooting suggestions from Scenario 1 from my other blog on Hybrid Migration Endpoints (EWS), these are applicable also here if f/b direction is cloud -> onpremises: https://techcommunity.microsoft.com/t5/exchange-team-blog/troubleshooting-hybrid-migration-endpoints...

Senior Member

Hi Mirela_Buru

 

We have an issue with not seeing free/busy from only online exchange to on-prem exchange (works in the other direction fine) I have reviewed you post (great) and have a getuseravailabiltyinternal that is kind of like #3 from your list but not quite. We suspect that something on our cloud configuration is not correct. Do you have any thoughts? 

 

{"Header":{"ServerVersionInfo":{"MajorVersion":15,"MinorVersion":20,"MajorBuildNumber":3433,"MinorBuildNumber":45,"Version":"V2018_01_08"}},"Body":{"Responses":[{"ResponseMessage":{"__type":"SingleResponseMessage:#Exchange","MessageText":"Proxy web request failed. , inner exception: System.Web.Services.Protocols.SoapHeaderException: An error occurred when verifying security for the message.\r\n at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)\r\n at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)\r\n at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)\r\n at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, IService service, IAsyncResult asyncResult)\r\n at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)\r\n at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()","ResponseCode":"ErrorProxyRequestProcessingFailed","MessageXml":"<?xml version=\"1.0\"?>\r\n<XmlNodeArray xmlns:t=\"http://schemas.microsoft.com/exchange/services/2006/types\" xmlns:m=\"http://schemas.microsoft.com/exchange/services/2006/messages\">\r\n <ExceptionType xmlns=\"http://schemas.microsoft.com/exchange/services/2006/errors\">ProxyWebRequestProcessingException</Exc... <ExceptionCode xmlns=\"http://schemas.microsoft.com/exchange/services/2006/errors\">5016</ExceptionCode>\r\n <ExceptionServerName xmlns=\"http://schemas.microsoft.com/exchange/services/2006/errors\">CH2PR19MB3832</ExceptionServerName>\r\n <ExceptionMessage xmlns=\"http://schemas.microsoft.com/exchange/services/2006/errors\">Proxy web request failed. , inner exception: An error occurred when verifying security for the message. LID: 59916</ExceptionMessage>\r\n</XmlNodeArray>","ResponseClass":"Error"},"CalendarView":{"MergedFreeBusy":null,"Items":null,"WorkingHours":null,"FreeBusyViewType":"None"}}],"ResponseCode":"NoError","ResponseClass":"Success"}}

 

 

I have also ran Get-IntraOrganizationConnector  on both on-prem and exch online and both do not show any output?

 

 

thanks!

Eric

Senior Member

Hi Mirela_Buru

 

We have an issue with not seeing free/busy from only online exchange to on-prem exchange (works in the other direction fine) I have reviewed you post (great) and have a getuseravailabiltyinternal that is kind of like #3 from your list but not quite. We suspect that something on our cloud configuration is not correct. Do you have any thoughts? 

 

{"Header":{"ServerVersionInfo":{"MajorVersion":15,"MinorVersion":20,"MajorBuildNumber":3433,"MinorBuildNumber":45,"Version":"V2018_01_08"}},"Body":{"Responses":[{"ResponseMessage":{"__type":"SingleResponseMessage:#Exchange","MessageText":"Proxy web request failed. , inner exception: System.Web.Services.Protocols.SoapHeaderException: An error occurred when verifying security for the message.\r\n at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)\r\n at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)\r\n at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)\r\n at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, IService service, IAsyncResult asyncResult)\r\n at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)\r\n at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()","ResponseCode":"ErrorProxyRequestProcessingFailed","MessageXml":"<?xml version=\"1.0\"?>\r\n<XmlNodeArray xmlns:t=\"http://schemas.microsoft.com/exchange/services/2006/types\" xmlns:m=\"http://schemas.microsoft.com/exchange/services/2006/messages\">\r\n <ExceptionType xmlns=\"http://schemas.microsoft.com/exchange/services/2006/errors\">ProxyWebRequestProcessingException</Exc... <ExceptionCode xmlns=\"http://schemas.microsoft.com/exchange/services/2006/errors\">5016</ExceptionCode>\r\n <ExceptionServerName xmlns=\"http://schemas.microsoft.com/exchange/services/2006/errors\">CH2PR19MB3832</ExceptionServerName>\r\n <ExceptionMessage xmlns=\"http://schemas.microsoft.com/exchange/services/2006/errors\">Proxy web request failed. , inner exception: An error occurred when verifying security for the message. LID: 59916</ExceptionMessage>\r\n</XmlNodeArray>","ResponseClass":"Error"},"CalendarView":{"MergedFreeBusy":null,"Items":null,"WorkingHours":null,"FreeBusyViewType":"None"}}],"ResponseCode":"NoError","ResponseClass":"Success"}}

 

 

I have also ran Get-IntraOrganizationConnector  on both on-prem and exch online and both do not show any output?

 

 

thanks!

Eric

Senior Member

Hi Mirela_Buru

 

We have an issue with not seeing free/busy from only online exchange to on-prem exchange (works in the other direction fine) I have reviewed you post (great) and have a getuseravailabiltyinternal that is kind of like #3 from your list but not quite. We suspect that something on our cloud configuration is not correct. Do you have any thoughts? 

 

{"Header":{"ServerVersionInfo":{"MajorVersion":15,"MinorVersion":20,"MajorBuildNumber":3433,"MinorBuildNumber":45,"Version":"V2018_01_08"}},"Body":{"Responses":[{"ResponseMessage":{"__type":"SingleResponseMessage:#Exchange","MessageText":"Proxy web request failed. , inner exception: System.Web.Services.Protocols.SoapHeaderException: An error occurred when verifying security for the message.\r\n at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)\r\n at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)\r\n at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)\r\n at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, IService service, IAsyncResult asyncResult)\r\n at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)\r\n at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()","ResponseCode":"ErrorProxyRequestProcessingFailed","MessageXml":"<?xml version=\"1.0\"?>\r\n<XmlNodeArray xmlns:t=\"http://schemas.microsoft.com/exchange/services/2006/types\" xmlns:m=\"http://schemas.microsoft.com/exchange/services/2006/messages\">\r\n <ExceptionType xmlns=\"http://schemas.microsoft.com/exchange/services/2006/errors\">ProxyWebRequestProcessingException</Exc... <ExceptionCode xmlns=\"http://schemas.microsoft.com/exchange/services/2006/errors\">5016</ExceptionCode>\r\n <ExceptionServerName xmlns=\"http://schemas.microsoft.com/exchange/services/2006/errors\">CH2PR19MB3832</ExceptionServerName>\r\n <ExceptionMessage xmlns=\"http://schemas.microsoft.com/exchange/services/2006/errors\">Proxy web request failed. , inner exception: An error occurred when verifying security for the message. LID: 59916</ExceptionMessage>\r\n</XmlNodeArray>","ResponseClass":"Error"},"CalendarView":{"MergedFreeBusy":null,"Items":null,"WorkingHours":null,"FreeBusyViewType":"None"}}],"ResponseCode":"NoError","ResponseClass":"Success"}}

 

 

I have also ran Get-IntraOrganizationConnector  on both on-prem and exch online and both do not show any output?

 

 

thanks!

Eric

Microsoft

Hi Eric, as mentioned in the first blog comment, make sure we are looking at the right Organization Relationship in Exchange Online (Office 365 > On-Premises ) and that is configured properly. If indeed the request reaches on-premises servers and not EXO servers,  then please recycle EWS App Pool on-premises /IISreset like I mentioned in the PDF with errors.

Occasional Visitor

(deleted)

Microsoft

@ADynes , provide me with the case number (you can also send me a private message) so that I can check it.

Senior Member

Hi @Mirela_Buru 

 

Your help was great and helped me figure out our main problem. We used a service to help us with setting up hybrid, they had us change our on-prem autodiscover dns record to point to outlook.com before we ran the wizard. I changed it back to our on-prem ip address after the wizard was run initially.  After I ran the wizard again (with the correct autodiscover record)  we are now seeing on-prem free/busy for our exchange 2013 users. We have exchange 2010 and 2013 on-prem and unfortunately we are unable to see the exchange 2010 users free/busy. The free/busy troubleshooter comes up with the error message below when I point to an exchange 2010 mailbox:

 

Any ideas where I should look next?

 

Performing Free/Busy Test. See guidance about the Hybrid Configuration Wizard at http://aka.ms/HCWFree/Busy test failed
Test Steps
Determining where the source mailbox is hosted.The check to determine if the source mailbox is hosted in Office 365 completed successfully.
Additional Details
Determining where the target mailbox is hosted. The check to determine if the target mailbox is hosted in Office 365 completed successfully.
Additional Details
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for xx .Autodiscover was tested successfully.
Test Steps
Verifying connectivity to the specified endpointSuccessfully verified pass-through connectivity.
Additional Details
Verifying connectivity to the specified endpointSuccessfully verified pass-through connectivity.
Additional Details
Performing Free/Busy LookupFree/Busy Lookup failed.
Additional Details
Free/Busy Lookup failed with exception: Proxy web request failed. , inner exception: System.Web.Services.Protocols.SoapHeaderException: An error occurred when verifying security for the message. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult) at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult) at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, IService service, IAsyncResult asyncResult) at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult) at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()
Microsoft

Hi @epeterson79 , for the security of the message error, just follow the previous suggestions: 
recycle EWS App Pool on all Exchange servers / run IISreset  like I mentioned in the PDF FB_Errors.FixesV6 (error #3) : https://support.microsoft.com/en-us/help/2752387/users-from-a-federated-organization-cannot-see-the-... 

 

Regular Visitor

Hello @Mirela_Buru 

First of all, Thanks a million, I've solved lots of Hybrid Free / Busy issues by taking help from this blog. However, currently I'm having an issue, I've spent a few hours on it but haven't been able to solve it. Our On-Premise Users can not see Cloud Users free / busy.

- First I found Federation Certificate was expired, I renewed it and recreated federation, Test-Federation is now all good.

- After that I found OAuth Certificate was expired, I was able to renew it and publish to all Exchange Servers, Test-OAuthConnectivity is all good.

- Test-OrganizationRelationship is all good.

- IntraOrganizationConnector is enabled.

- I checked your FB errors table but I couldn't found the error I'm facing.

- I've done tonnes of changes at On Premise OrganizationRelationship populating TargetSharingEPR, Testing with / without WSSecurity, Disabling IOC but no luck. I'm stuck on below error.

- In OWA Network Response for Get-Useravailablity as well as at MS RCA I get error, I suspect this is still related to OAuth between EXO and EX-On-Premise ?

 

Free/Busy Lookup failed with exception: Autodiscover failed for email address USER@INITIALDOMAIN.mail.onmicrosoft.com with error System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 52.98.32.2:443

 

Microsoft

@Mashal_Khan , this is a network issue between Exchange On-Premises Servers and Exchange Online Server IP Addresses (52.98.32.2 is EXO server where probably your target cloud user USER@INITIALDOMAIN.mail.onmicrosoft.comis hosted).

How are your Exchange On-premises servers going out on the internet? Proxy or Firewall? You seem to be blocking outbound connections to 52.98.32.2. If using proxy, make sure this is set on the Exchange Servers, you can do Get-ExchangeServer |FL identity, internetwebproxy to check if there and Set-ExchangeServer to set one. Make sure you allow all your Exchange Servers to connect to all EXO IP addresses https://docs.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-world... 

You should follow Suggestions from Error 22, points 2 and 3 and make sure you can access from Exchange System Account (on each Exchange Server CAS/MBX) the following URLs:
https://autodiscover-s.outlook.com/autodiscover/autodiscover.svc ( EXO Autodiscover Service)

https://52.98.32.2/autodiscover/autodiscover.svc  (continue to certificate error because we put ip)

http://autodiscover.<YOUR-INITIAL-DOMAIN.mail.onmicrosoft.com/autodiscover/autodiscover.svc  (this should redirect to https EXO Autodiscover Service)

https://outlook.office365.com/ews/exchange.asmx ( EXO EWS Service, this can also be set on the TargetSharingEpr on the on-premises Organization Relationship when On-Premises IOC is disabled). 

Regular Visitor

@Mirela_Buru 

Thank You, Sorry I forgot to mention, I checked on all Exchange Servers, they're doing out to the Internet directly i.e. internetwebproxy is empty on all. We don't have internet access on any Exchange Server but Hybrid Server can make outbound requests to anywhere on port 80, 443. I checked all URLs are accessible on Hybrid Server. Free / Busy was fine previously with the same network access. Do I these URLs need to be accessible on all Exchange Servers or just Hybrid Server is enough ?

 

The other thing you advised is that if I disable On Premise IOC and populate OrganizationRelationship with https://outlook.office365.com/ews/exchange.asmx Free / Busy look up will not use Autodiscover but it will use EWS and that may resolve my issue ?

 

Also I will have my network team allow outbound connections to anywhere on port 80, 443 for a small duration to test and let you know if that worked.

Microsoft

1.  Do I these URLs need to be accessible on all Exchange Servers or just Hybrid Server is enough ?

>> ALL the Exchange 2010 MBX & CAS or 2013 MBX (backend) or 2016 would need outbound Internet access to all these:

Reference: https://docs.microsoft.com/en-us/previous-versions/office/exchange-server-2010/dd638083(v=exchg.141)... 

 

2. The other thing you advised is that if I disable On Premise IOC and populate Organization Relationship with https://outlook.office365.com/ews/exchange.asmx Free / Busy look up will not use Autodiscover but it will use EWS and that may resolve my issue ?

>>Yes, correct, you can try to bypass AutoD query and see if it works by going directly to EWS but this can be any on-premises Exchange Server in your organization, so internet access is needed from each.

Regular Visitor

@Mirela_BuruThank you for great help, I was able to create a User on Hybrid Server, that User is able to see Cloud Users Free / Busy as Hybrid Server has required outbound access to anywhere on port 80,443, We need to grant all Exchange Servers outbound access to the Office 365 IPs/ Urls to solve this, THANKS A BILLION !!!!

Senior Member

Can you confirm in section 22 "https://login.microsoftonline.com/extSTS.srf [<-- You should be prompted to
download the file.]" - that the file should be downloadable? (I've tried from a variety of different machines but get the same experience)

 

When i run the psexec test I get a webpage that says

 

"Sorry, but we’re having trouble with signing you in.

AADSTS900561: The endpoint only accepts POST requests. Received a GET request."

 

I'm seeing errors in outlook (onprem) to 365 mailbox f/b lookups that state 

 

"<MessageText>Failed to communicate with https://login.microsoftonline.com/extSTS.srf."

 

so it seems a very similar error but i'm struggling to troubleshoot further.

 

Thanks for any pointers.

Microsoft

Hi @David Hood , you are correct, the PDF is outdated. I will try to update it soon.

The https://login.microsoftonline.com/extSTS.srf   should give [<-- You should see “Sorry, but we’re having trouble signing you in”.]

 

For MFG URLs issues, you can also check my other blog on Federation Trust, especially error 3: https://techcommunity.microsoft.com/t5/exchange-team-blog/how-to-address-federation-trust-issues-in-... 

 

New Contributor

Hi all,

 

I tried to find out a problem with F/B - Exchange 2016 on-premises users  are not able to view the free/busy information of the office 365 users. They have in Outlook 2016 (could not be updated),

I check OWA F12 and error is: System.Net.WebException: The request failed with HTTP status 401: Unauthorized.

 

I was able to find almost same error in the Microsoft free/busy troubleshooting guide (Index 26) attached below as well: https://anishjohnes.files.wordpress.com/2019/10/fb_errors.fixesv6.pdf

 

but when i test Test-OAuthConnectivity -Service EWS -TargetUri https://outlook.office365.com/ews/exchange.asmx -Mailbox OnPremises 

my exception are:

System.Net.WebException: The request was aborted: The request was canceled. ---> Microsoft.Exchange.Security.OAuth.OAuthTokenRequestFailedException: The trusted issuers contained the followi
ng entries '00000001-0000-0000-c000-000000000000@*'. None of them are configured locally.

 

Also I check following guide (index 26) check certificate mismatch but i have the same on perm and Azure.

 

I found solution, I explaind what I did on the forum: https://social.technet.microsoft.com/Forums/en-US/a0bb1d0a-6639-4fdf-92e1-7fa350e47057/exchange-2016...

 

Regards,

Rafal

Microsoft

Thanks for your feedback, @rchmielarski , for such error we would normally need more outputs on how the OAuth is configured and it's interesting that apparently IISreset did the trick here. Would have been good to know your CU for Exchange 2016 and if by any chance Get-AuthServer  had previously or maybe it still has the  -DomainName populated with an SMTP domain and if the user used in Test-OauthConnectivity had that domain in primary SMTP address.

Frequent Visitor
Issue exchange 2013 cannot see free busy information 2007

Hi @Mirela_Buru, I have enviroment with exchange 2007 and exchange 2013. I Have a event id in my exchange 2013: 

 

Process 15040: ProxyWebRequest CrossSite from S-1-5-21-190996285-3174742192-1521001504-11052 to https://mail.teste.com.br:443/EWS/Exchange.asmx failed. Caller SIDs: NetworkCredentials. The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException: Proxy web request failed. ---> System.Net.WebException: The request failed with HTTP status 401: Unauthorized.

 

 

And there is a problem "exchange 2013 cannot see free busy information 2007" . The o rest all work fine 

 

But i don't have in my enviroment exchange online.

This solutions cab se aply in my enviroment? (https://techcommunity.microsoft.com/legacyfs/online/media/2019/01/FB_Errors.FixesV6.pdf  index 10: Proxy web request failed.,inner exception: The
request failed with HTTP status 401:
Unauthorized.) 

 

 

Thank you for your help

best regards

 

Agostinho Martini

Microsoft

@Agostinho_Martini , the solutions from this PDF don't apply to this scenario.

I would suggest to check HTTPProxy EWS logs on the Ex2013 and IIS logs on Ex2007, eventually FREB logs for 401 sub code.

Check Authentication Methods in EWS on Ex2007 server. Make sure Default user doesn't have NONE in the Get-MailboxFolderPermission TargetUser:\Calendar.  Exchange 2007 users can see Free/Busy between them and set OOF replies successfully?

Frequent Visitor

@Mirela_Buru  Thank you very much!

 

Users in exchange 2007 can see free busy information amoung user in exchange 2007.

 

User in exchange 2007 can see free busy information users exchange 2013.

 

Only users exchange 2013 cant seee frre busy information user exchange 2007.

 

EWS autentication exchange 2013: Default and Back End site

 

[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory -server smxpoa05 | fl InternalUrl,ExternalUrl,Identity,Name,*au
th* | fl
Creating a new session for implicit remoting of "Get-WebServicesVirtualDirectory" command...


InternalUrl : https://mail.teste1.com.br/ews/exchange.asmx
ExternalUrl : https://mail.teste1.com.br/ews/exchange.asmx
Identity : servidor1\EWS (Default Web Site)
Name : EWS (Default Web Site)
CertificateAuthentication :
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity, OAuth}
ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity, OAuth}
LiveIdNegotiateAuthentication :
WSSecurityAuthentication : True
LiveIdBasicAuthentication : False
BasicAuthentication : False
DigestAuthentication : False
WindowsAuthentication : True
OAuthAuthentication : True
AdfsAuthentication : False

 

[PS] C:\Windows\system32>Get-WebServicesVirtualDirectory -ShowMailboxVirtualDirectories -Server smxpoa05 | fl


RunspaceId : ca5a7de9-75a2-4fdb-97f2-284da2ac5af2
CertificateAuthentication :
InternalNLBBypassUrl : https://mail.teste1.local:444/ews/exchange.asmx
GzipLevel : High
MRSProxyEnabled : False
Name : EWS (Exchange Back End)
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity}
ExternalAuthenticationMethods : {Ntlm, WindowsIntegrated, WSSecurity}
LiveIdNegotiateAuthentication :
WSSecurityAuthentication : True
LiveIdBasicAuthentication : False
BasicAuthentication : False
DigestAuthentication : False
WindowsAuthentication : True
OAuthAuthentication : False
AdfsAuthentication : False


EWS autentication exchange 2007: Default


Get-WebServicesVirtualDirectory
-server smxpoa01 | fl InternalUrl,ExternalUrl,Identity,Name,*auth* | fl


InternalUrl : https://legacy.teste1.com.br/EWS/Exchange.asmx
ExternalUrl : https://legacy.teste1.com.br/EWS/Exchange.asmx
Identity : SMXPOA01\EWS (Default Web Site)
Name : EWS (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
ExternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
BasicAuthentication : True
DigestAuthentication : False
WindowsAuthentication : True

 

In my logs iis 2007 and 2013 i found:

Log IIS 2007:


C:\WINDOWS\system32\LogFiles\HTTPERR

2020-11-09 19:42:28 10.63.78.187 53295 10.63.70.231 443 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?SMXPOA04.teste1.local:6001 400 1 BadRequest DefaultAppPool
2020-11-09 19:42:28 170.233.237.115 16855 10.63.70.231 443 - - - - - Timer_ConnectionIdle -
2020-11-09 19:42:32 10.63.51.188 59668 10.63.70.231 443 - - - - - Timer_ConnectionIdle -
2020-11-09 19:42:34 10.63.78.185 56960 10.63.70.231 443 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?SMXPOA03.teste1.local:6001 400 1 BadRequest DefaultAppPool
2020-11-09 19:42:34 10.63.78.186 22997 10.63.70.231 443 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?SMXPOA03:6001 400 1 BadRequest DefaultAppPool


Log IIS 2013:

C:\Windows\System32\LogFiles\HTTPERR

2020-11-09 20:52:43 10.63.78.185 19986 10.63.78.185 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?smxpoa05.teste1.local:6001 400 2 Connection_Dropped MSExchangeRpcProxyAppPool
2020-11-09 20:52:43 10.63.75.43 50880 10.63.78.185 443 HTTP/1.1 POST /Microsoft-Server-ActiveSync?User=abiliolima&DeviceId=7QULD3E1SP1FR5ERG8Q5IHK68G&DeviceType=iPhone&Cmd=Ping - 1 Connection_Dropped MSExchangeSyncAppPool
2020-11-09 20:52:43 10.63.75.43 50908 10.63.78.185 443 HTTP/1.1 POST /Microsoft-Server-ActiveSync?eQAWBBAl2wZcQIhAIrRyDVtNyO9ABOj7SokLV2luZG93c01haWw= - 1 Connection_Dropped MSExchangeSyncAppPool

 

For me i am very confused because i found only event id exchange 2013:

 

Process 15040: ProxyWebRequest CrossSite from S-1-5-21-190996285-3174742192-1521001504-11052 to https://mail.teste1.com.br:443/EWS/Exchange.asmx failed. Caller SIDs: NetworkCredentials. The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException: Proxy web request failed. ---> System.Net.WebException: The request failed with HTTP status 401: Unauthorized.

 

Any idea?

 

 

Microsoft

I would say to make sure that is indeed the error (401 Unauthorized) for this free/busy direction ex2013 -> ex2007 .

You can try free/Busy test https://testconnectivity.microsoft.com/tests/FreeBusy/input or OWA F12 Network tab GetUserAvailability call and check Response body. 

And in logs, you would look at EWS/Exchange.asmx or WebServicesAppPool stuff. 

Senior Member

Hello Mirela, amazing article.

 

We have a story where 2 onprem exchange Organizations (org1 and orerg2) share an smtp address space (@company.com). 1 org is already hybrid with O365. All works there, including mail routing via EOP and transport rules to decide left or right.

Now the second org wants their mailboxes also moved to Exchange Online. Both Orgs have company.com as primary SMTP for all users. We will be able to setup a second hybrid (minimal hybrid with manual corrections) to support migration and some level of co-existence. We expect F/B onprem (org2 user) to cloud will work. However Cloud to Org2 user onpremise is likely to fail. What would be required, if at all possible, to make this scenario work ? 


Thanks a lot,
Toni

New Contributor

Unless it's a new feature, you'll not be able to assign the primary SMTP to two different tenants. I have used hybrid to migrate 7 different schools into their own tenant, one at a time. We connected the Hybrid to the first domain and migrated, then move it to the second domain and repeat down the line. The assumption is that the 'hybrid' is only needed for free/busy during the migration. Once everyone is moved up, you can still maintain SMTP connectivity for remaining mail flow.

Microsoft

@tonivervloet , So the first question is related to tenants, is it Org1 and Org2 to same Tenant1 or different tenant, Tenant2? 

Then yes, like Robert said above, you won't be able to migrate if the SMTP domain is shared between 2 tenants, you need to have an accepted domain verified, unique in Tenant 2. 
If same tenant and 2 on-premises organizations, then I also don't see how to work-around the free/busy part if the on-premises users will have same SMTP. The Target Address Domain is the cloud organization relationships or cloud intra-organization connectors must be unique (even if you can set targetSharingEpr to point to EWS of each on-premises organization).

Senior Member

hello @Mirela_Buru , @Robert Styles ,

 

Indeed the address spaces is only assigned to 1 tenant of course, but shared between a tenant (onprem + hybrid) and an onprem org that soon will be hybrid (to the same tenant) as well. But environments have company.com users (primary) and that works fine. Ideally that would have the shared as secondary, then we could uniquely identify both orgs.

We can get an accepted domain verified for org 2 no problem, but that domain is only used as a proxy. Its the old name space.

 

Seems we are stuck ?


thanks already for your time,both.

 

Toni

Established Member

I didnt see this error on your list.  The issue we are having is an O365 user can not see the free/busy calendar for an Exchange 2010 user.  The Exchange user can see the Free/Busy of the O365 user.  When this issue happened in the past, I would run IISREST on the Exchange 2010 CAS servers and the problem would be fixed.  This time, its not working.  Any ideas?

 

Performing Free/Busy LookupFree/Busy Lookup failed.

 
Additional Details
Free/Busy Lookup failed with exception: Proxy web request failed. , inner exception: System.Web.Services.Protocols.SoapHeaderException: An error occurred when processing the security tokens in the message. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult) at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult) at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, IService service, IAsyncResult asyncResult) at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult) at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()
Established Member

Found the solution to my problem.  I ran IISRESET again, waited for a bit and no change.  Then I ran this command on both Exchange 2010 CAS server and now the Free/Busy is showing.

Get-FederationTrust | Set-FederationTrust -RefreshMetadata

 

Microsoft

@JeffP2021 , glad you managed to fix it.
This is  similar to error #3 from the PDF : "An error occurred when verifying security for the message" so you would follow the exact steps / resolution 

Mirela_Buru_0-1611835955607.png

You might want to create a scheduled task for this as mentioned here  https://techcommunity.microsoft.com/t5/exchange-team-blog/keep-your-federation-trust-up-to-date/bc-p... 

 

Established Member

Thank you for the reply.  Im not sure how I missed number 3.  My problem is partially solved.  It worked for the calendar I had previously added.  I am still having the trouble adding new calendars.  I will look at number 3 again and follow the suggested steps.

 

I have call scheduled with MS Support today.  Hopefully it will be fixed by then.

Established Member

Mirela

 

Why can I see one on-premise account (the original one that was working) an no other on-premise account?  The free/busy connectivity test passes for this user, but the others get the error in number 3.

 

I am now working with MS Support.

Occasional Visitor

Hello,

 

We have exchange 2010 Sp3 environment coexistence with 2016 exchange server as hybrid. We have recently configured hybrid and migrated successfully migrated user to office 365.

 

We have noticed that free busy is not working from office 365 to On-prem users and vice versa.

 

We have checked the Autodiscover endpoint from outside the network it is giving authentication prompt same for EWS gives the authentication prompt however free busy not working. As per the article I have set the target sharingepr but still we have issues. Also we have toggled wssauthentication for exchange 2010 and 2016 and restarted the app pool but no luck.

 

Can you please suggest us we are kind of stuck and not migrating any mailboxes to cloud.

Microsoft

@Shady111 , you should first check this blog announcement Keep your Federation Trust up-to-date - Microsoft Tech Community

 and make sure you performed RefreshMetadata (recommended it to run it twice).

Second, run the Free/Busy test on exrca.com here: Microsoft Remote Connectivity Analyzer and see what is the error message for free/busy lookup from Cloud Source User to On-Premises Target User(s).  You might get different errors. 

Once you know the free/busy error message, you can lookup the list with 34 errors from above and see if you find your error or similar one in the list. And in the PDF you have some suggestions to fix / troubleshoot this:

Free/Busy Errors discussed in the attached table:

FB_Errors.FixesV6

Microsoft

@JeffP2021 , might be needed to run RefreshMetadata twice and possibly iisreset on each server? Can you provide me with the case number (private message), I can maybe take a look there?

Established Member

Thank you Mirela_Buru.  I have ran RefreshMetadata twice and ran IISRESET on both servers, no change.

 

I will send PM with MS case #.  He could use all the help he can get.  Thank you!

Senior Member

Hello,

my free busy is failing with this error on both sides , Any thoughts inputs appreciated

ManjunBN_0-1612463716420.png

 

Microsoft

Hi @ManjunBN , I would need a Test-FederationTrust -Verbose output from onpremises organization executed in Exchange Management Shell if Exchange 2010 server, if Ex2013/2016/2019, then you would do it like this:

Open Windows PowerShell (blue)

add-pssnapin *exchange*

start-transcript

Test-FederationTrust -Verbose | fl

Get-FederationTrust | fl

Get-FederatedOrganizationIdentifier | fl

stop-transcript

You can open a case and upload transcript there and send me the case number or you can send me a private message with the output.

Also, did Free/Busy work so far?

Did you do any modification to the federation trust recently? like Set-FederatedOrganizationIdentifier?

 

%3CLINGO-SUB%20id%3D%22lingo-sub-1105282%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1105282%22%20slang%3D%22en-US%22%3E%3CP%3ECiao%20Mirela%3C%2FP%3E%3CP%3EI%20have%20an%20Exchange%20Hybrid%20Deployment%20(with%20Exchange%202016)%3C%2FP%3E%3CP%3EEverything%20was%20working%20fine%2C%20but%20after%20we%20have%20switched%20the%20publication%20on%20Web%20Application%20Proxy%2C%20the%20availability%20stopt%20to%20work.%3C%2FP%3E%3CP%3EAll%20the%20services%20are%20published%20in%20Pass%20trough%20and%20all%20the%20other%20exchange%20services%20are%20ok%20autodiscover%20included.%3C%2FP%3E%3CP%3EThere%20some%20settings%20that%20we%20have%20to%20check%20on%20the%20WAP%20server%3F%3C%2FP%3E%3CP%3EThank%20you%3C%2FP%3E%3CP%3EMichele%20Foffano%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1107835%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1107835%22%20slang%3D%22en-US%22%3E%3CP%3ECiao%20Michele%2C%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3EWe%20would%20need%20the%20Free%2FBusy%20error%20for%20the%20affected%20direction.%20Assuming%20it%20is%20cloud%20to%20on-premises%2C%20check%20the%20error%20with%20Fiddler%20or%20OWA%20F12%20(look%20at%20GetUserAvailability*%20as%20explained%20above)%20and%20check%20Get-IntraOrganizationConnector%20and%20Get-OrganizationRelationship%20settings%20in%20Cloud.%20And%20also%20on%20exrca.com%20the%20free%2Fbusy%20test%20under%20O365%20for%20Cloud%20user%20to%20OnPrem%20user%20(assuming%20direction%20is%20cloud%20-%26gt%3B%20onprem).%20This%20will%20say%20if%20pass%20through%20is%20there%20indeed%20at%20least%20for%20Basic%20Auth%20(what%20exrca%20tests%20now)%20and%20other%20things%20like%20ports%20%2C%20certificates.%20Could%20be%20also%20a%20TLS%20issue%2C%20I%20cannot%20guess%2C%20so%20we%20need%20the%20F%2FB%20error%20message%20and%20you%20can%20also%20check%20the%20most%20common%20errors%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F01%2FFB_Errors.FixesV6.pdf%22%20target%3D%22_blank%22%3EFB_Errors.FixesV6%3C%2FA%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1107915%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1107915%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20everyone%3A%20my%20name%20is%20Mirela%20Buruiana%20and%20I%20am%20the%20main%20author%20of%20this%20blog.%20Reply%20to%20this%20comment%20if%20you%20want%20me%20to%20get%20notified%20about%20your%20question%20%2Fcomment.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1112122%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1112122%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Mirela%2C%3C%2FP%3E%3CP%3Equering%26nbsp%3BGet-IntraOrganizationConnector%20we%20have%20noticed%20that%20the%20discovery%20endpoint%20URL%20is%26nbsp%3B%20%3CA%20href%3D%22https%3A%2F%2Fwebmail.domain.com%2Fautodiscover%2Fautodiscover.svc%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwebmail.domain.com%2Fautodiscover%2Fautodiscover.svc%3C%2FA%3E.%3C%2FP%3E%3CP%3EOn%20the%20Web%20Application%20Proxy%20server%20we%20have%20published%20all%20the%20services%20individually%20%3A%3C%2FP%3E%3CUL%3E%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fwebmail.domain.com%2Fowa%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwebmail.domain.com%2Fowa%2F%3C%2FA%3E%3C%2FLI%3E%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fwebmail.domain.com%2Fews%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwebmail.domain.com%2Fews%2F%3C%2FA%3E%3C%2FLI%3E%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fwebmail.domain.com%2Frpc%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwebmail.domain.com%2Frpc%2F%3C%2FA%3E%3C%2FLI%3E%3CLI%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fautodiscover.domain.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fautodiscover.domain.com%2F%3C%2FA%3E%3C%2FLI%3E%3CLI%3Eetc%3C%2FLI%3E%3C%2FUL%3E%3CP%3EWe%20didn't%20pubblish%20the%20url%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwebmail.domain.com%2Fautodiscover%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwebmail.domain.com%2Fautodiscover%3C%2FA%3E%20.%3C%2FP%3E%3CP%3EThis%20was%20the%20problem%26nbsp%3B%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Fhtml%2Fimages%2Femoticons%2Fsmile_40x40.gif%22%20alt%3D%22%3Asmile%3A%22%20title%3D%22%3Asmile%3A%22%20%2F%3E%3C%2FP%3E%3CP%3Edo%20you%20know%20if%20on%20the%20WAP%20services%20we%20can%20publish%20the%20root%20URL%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwebmail.domain.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwebmail.domain.com%2F%3C%2FA%3E%20%3F%3C%2FP%3E%3CP%3Eor%20we%20must%20create%20a%20pubblication%20for%20every%20service%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20your%20help%3C%2FP%3E%3CP%3Ebest%20regards%3C%2FP%3E%3CP%3ECiao%3C%2FP%3E%3CP%3EMichele%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1112941%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1112941%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Michele%2C%20I%20don't%20know%20WAP%20%3A)%3C%2Fimg%3E%20but%20you%20can%20change%20the%20Discovery%20endpoint%20on%20the%20IOC%20to%20autodiscover.domain.com.%20Unfortunately%2C%20HCW%20by%20default%20sets%20the%20discoveryEndpoint%20to%20the%20EWS%20Fqdn%20%2Fautodiscover%20.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1340792%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1340792%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20having%20a%20free%20busy%20issue%20from%20Cloud%20to%20On-Prem%2C%20I've%20run%20the%20free%2Fbusy%20test%20from%20EXRCA%20and%20all%20results%20show%20that%20the%20mailbox%20is%20accessible%2C%20the%20trace%20shows%20calendar%20info%20but%20testing%20from%20a%20cloud%20account%20(OWA)%20to%20on-prem%20does%20not%20return%20results.%20If%20the%20EXRCA%20works%20what%20else%20should%20I%20look%20at.%20Is%20this%20a%20permission%20error%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1341489%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1341489%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CDIV%20class%3D%22lia-message-author-with-avatar%22%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20display%3A%20inline-block%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20padding-top%3A%2010px%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20vertical-align%3A%20top%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3E%3CSPAN%20class%3D%22UserName%20lia-user-name%20lia-user-rank-New-Contributor%20lia-component-message-view-widget-author-username%22%20style%3D%22box-sizing%3A%20border-box%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20white-space%3A%20nowrap%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F73611%22%20target%3D%22_blank%22%3E%40Robert%20Styles%3C%2FA%3E%20%3C%2FSPAN%3E%3C%2FDIV%3E%0A%3CDIV%20class%3D%22lia-message-author-rank%20lia-component-author-rank%20lia-component-message-view-widget-author-rank%22%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20display%3A%20inline-block%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20overflow%3A%20hidden%3B%20padding-top%3A%2010px%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-overflow%3A%20ellipsis%3B%20text-transform%3A%20none%3B%20vertical-align%3A%20top%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20nowrap%3B%20word-spacing%3A%200px%3B%22%3Echeck%26nbsp%3B%20%22Where%20can%20we%20see%20actual%20Free%2FBusy%20error%20message%3F%22%2C%20look%20at%20OWA%20F12%20method%20or%20Fiddler%20and%20search%20for%20GetUserAvailability%20call%20as%20shown%20above%20in%20the%20blog.%3C%2FDIV%3E%0A%3CDIV%20class%3D%22lia-message-author-rank%20lia-component-author-rank%20lia-component-message-view-widget-author-rank%22%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20%23333333%3B%20display%3A%20inline-block%3B%20font-family%3A%20%26amp%3Bquot%3B%20segoeui%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blato%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%2014px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20overflow%3A%20hidden%3B%20padding-top%3A%2010px%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-overflow%3A%20ellipsis%3B%20text-transform%3A%20none%3B%20vertical-align%3A%20top%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20nowrap%3B%20word-spacing%3A%200px%3B%22%3EOnce%20you%20get%20the%20error%20message%2C%20check%20the%20PDF%20with%20errors%20and%20fixes%2C%20see%20if%20something%20similar.%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1341542%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1341542%22%20slang%3D%22en-US%22%3E%3CP%3EI'm%20puzzled%20why%20The%20connectivity%20analyzer%20shows%20it%20all%20but%20the%20actual%20OWA%20user%20it's%20not%20working.%20I%20would%20think%20I'd%20see%20some%20indicator%20on%20the%20report.%20Thanks%20for%20the%20reply%2C%20I'll%20see%20if%20I%20can%20see%20anything%20in%20the%20OWA%20analysis.%20I%20do%20a%20lot%20of%20hybrids%20and%20Free%2FBusy%20is%20the%20most%20likely%20place%20I%20run%20into%20problems.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1341547%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1341547%22%20slang%3D%22en-US%22%3E%3CP%3ERCA%20test%20is%20not%20accurate.%20We%20are%20working%20on%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1341553%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1341553%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20showing%20data%20from%20the%20mailbox%20that%20we%20are%20looking%20to%20get%20free%2Fbusy%20data%20from%2C%20I%20see%20a%20list%20of%20meetings%20that%20should%20be%20coming%20back%20to%20the%20cloud%20user.%20So%20even%20though%20I%20see%20this%20it%20may%20not%20be%20a%20real%20result%3F%20Blocked%20from%20sending%20back%20to%20the%20OWA%20user%20in%20the%20cloud%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1358223%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1358223%22%20slang%3D%22en-US%22%3E%3CP%3ESorry%20for%20delay%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F73611%22%20target%3D%22_blank%22%3E%40Robert%20Styles%3C%2FA%3E%26nbsp%3B%2C%20can%20you%20please%20retry%20RCA%20Free%2FBusy%20test%20now%20and%20let%20me%20know%20if%20there%20is%20now%20an%20error%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1358246%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1358246%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F395212%22%20target%3D%22_blank%22%3E%40Mirela_Buru%3C%2FA%3E%26nbsp%3BThanks%20for%20looking%20at%20this.%20The%20free%20busy%20actually%20looked%20great.%20We%20dug%20a%20little%20deeper%20and%20found%20during%20the%20scheduling%20assistant%20look%20up%20we%20were%20getting%20an%20authentication%20error...%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20hostname%20component%20of%20the%20audience%20claim%20value%20'%3CA%20href%3D%22https%3A%2F%2Femail.nppd.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Femail.customer.com%3C%2FA%3E'%20is%20invalid%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EIt%20had%20been%20a%20while%20since%20the%20client%20had%20run%20the%20HCW%2C%20and%20once%20we%20ran%20through%20that%20again%20it%20repaired%20the%20federation%20and%20we%20were%20immediately%20able%20to%20see%20free%2Fbusy.%20In%20these%20situations%20I%20think%20I'll%20try%20that%20earlier%20and%20hopefully%20save%20some%20frustration!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-607727%22%20slang%3D%22en-US%22%3EDemystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-607727%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20this%20second%20part%20of%20the%20Demystifying%20Hybrid%20Free%2FBusy%2C%20we%20will%20cover%20troubleshooting%20of%20Hybrid%20Free%2FBusy%20scenarios%2C%20more%20specifically%20%E2%80%93%20how%20and%20where%20to%20find%20an%20actual%20error%20that%20will%20indicate%20where%20the%20problem%20is.%20Before%20venturing%20forth%2C%20please%20make%20sure%20that%20you%20have%20seen%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fdemystifying-hybrid-free-busy-what-are-the-moving-parts%2Fba-p%2F607704%22%20target%3D%22_blank%22%3EPart%201%20of%20this%20demystifying%20series%3C%2FA%3E!%20Here%20is%20the%20graphics%20we%20posted%20in%20the%20previous%20post%3B%20use%20this%20as%20a%20reference%20for%20users%20that%20we%20will%20be%20referring%20to%20when%20troubleshooting%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_1.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20style%3D%22border%3A%200px%20currentcolor%3B%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_1_thumb.jpg%22%20border%3D%220%22%20alt%3D%22FB2_1%22%20title%3D%22FB2_1%22%20width%3D%22884%22%20height%3D%22399%22%20%2F%3E%3C%2FA%3E%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId-1760057957%22%20id%3D%22toc-hId--1415474507%22%3EDo%20you%20really%20have%20a%20Free%2FBusy%20issue%3F%3C%2FH2%3E%0A%3CP%3EUsually%20when%20a%20user%20creates%20a%20new%20meeting%20in%20Outlook%20on%20the%20web%20(OWA)%20or%20Outlook%2C%20clicks%20on%20%3CSTRONG%3EScheduling%20Assistant%3C%2FSTRONG%3E%2C%20adds%20his%20or%20her%20colleague%20to%20the%20meeting%2C%20they%20try%20to%20see%20when%20the%20user%20is%20available%20to%20meet.%20If%20they%20see%20the%20hash%20marks%20%3CSTRONG%3E%5C%5C%5C%5C%5C%5C%5C%3C%2FSTRONG%3E%20instead%20of%20seeing%20if%20the%20other%20user%20is%20free%20or%20busy%2C%20there%20is%20an%20issue.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_2.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20style%3D%22border%3A%200px%20currentcolor%3B%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_2_thumb.jpg%22%20border%3D%220%22%20alt%3D%22FB2_2%22%20title%3D%22FB2_2%22%20width%3D%22708%22%20height%3D%22398%22%20%2F%3E%3C%2FA%3E%20You%20can%20often%20see%20an%20error%20message%20by%20hovering%20over%20hash%20marks%2C%20however%20we%20usually%20find%20that%20the%20error%20is%20not%20very%20specific.%20Instead%20we%20would%20need%20to%20take%20slightly%20more%20advanced%20steps%20to%20diagnose%20the%20issues%20by%20checking%20things%20like%20the%20Outlook%20logs%2C%20F12%20Network%20tab%2C%20or%20Fiddler.%20Before%20getting%20to%20actual%20Free%2FBusy%20errors%20it%20is%20worthy%20to%20know%20that%20there%20is%20a%20Free%2FBusy%20test%20on%20%3CA%20href%3D%22https%3A%2F%2Ftestconnectivity.microsoft.com%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ERemote%20Connectivity%20Analyzer%3C%2FA%3E%2C%20Office%20365%20tab%20that%20can%20help%20us%20with%20some%20configuration%20%2Ffunctional%20issues.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_3.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20style%3D%22border%3A%200px%20currentcolor%3B%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_3_thumb.jpg%22%20border%3D%220%22%20alt%3D%22FB2_3%22%20title%3D%22FB2_3%22%20width%3D%22234%22%20height%3D%2271%22%20%2F%3E%3C%2FA%3E%20This%20Free%2FBusy%20test%20is%20useful%20for%20checking%20DNS%20records%2C%20Autodiscover%20and%20EWS%20connectivity%20issues%2C%20pre-authentication%20for%20Autodiscover%20or%20EWS%20requests.%20It%20is%2C%20however%20not%20a%20relevant%20Free%2FBusy%20test%20per%20se%2C%20as%20it%20uses%20Basic%20authentication%20and%20not%20Federated%20authentication%20used%20in%20actual%20Free%2FBusy%20lookups.%20Therefore%2C%20don%E2%80%99t%20be%20surprised%20if%20you%20see%20this%20test%20as%20green%20(successful)%20but%20Free%2FBusy%20is%20not%20working%20in%20your%20Hybrid%20Organization.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_4.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20style%3D%22border%3A%200px%20currentcolor%3B%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_4_thumb.jpg%22%20border%3D%220%22%20alt%3D%22FB2_4%22%20title%3D%22FB2_4%22%20width%3D%22593%22%20height%3D%22504%22%20%2F%3E%3C%2FA%3E%20I%20would%20also%20like%20to%20mention%20that%20there%20is%20a%20Free%2FBusy%20troubleshooter%20in%20Beta%20version%2C%20incorporated%20into%20SARA%20tool%20(Microsoft%20Support%20and%20Recovery%20Assistant%20for%20Office%20365)%20which%20you%20can%20download%20it%20from%20here%20%3A%20%3CA%20href%3D%22https%3A%2F%2Fdiagnostics.outlook.com%2F%23%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3E%3CSTRONG%3Ehttps%3A%2F%2Fdiagnostics.outlook.com%2F%23%2F%3C%2FSTRONG%3E%3C%2FA%3E%20Open%20SARA%20and%20select%20Outlook%2C%20click%20Next%2C%20select%20%3CI%3EI%E2%80%99m%20having%20problems%20with%20my%20calendar%3C%2FI%3E%2C%20input%20email%20address%20and%20password%20of%20the%20source%20mailbox%20(cloud%20mailbox%20if%20direction%20not%20working%20is%20cloud%20%26gt%3B%20on-premises)%20and%20then%20select%20%3CI%3EI%20can%E2%80%99t%20see%20when%20someone%20is%20free%20or%20busy%3C%2FI%3E.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_5.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20style%3D%22border%3A%200px%20currentcolor%3B%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_5_thumb.jpg%22%20border%3D%220%22%20alt%3D%22FB2_5%22%20title%3D%22FB2_5%22%20width%3D%22584%22%20height%3D%22437%22%20%2F%3E%3C%2FA%3E%20Due%20to%20underlying%20complexity%20of%20it%20all%2C%20this%20is%20not%20a%20completely%20reliable%20way%20of%20determining%20the%20cause%20of%20free%2Fbusy%20issues%20in%20Hybrid%20Deployments%2C%20but%20it%20is%20a%20good%20start%20when%20troubleshooting.%20This%20F%2FB%20test%20from%20SARA%20covers%20mostly%20cloud%20to%20cloud%20scenarios%20but%20I%20recommend%20it%20here%20because%20it%20does%20connectivity%20and%20additional%20checks%20on%20tenant%2C%20licensing%20and%20Autodiscover.%3C%2FP%3E%0A%3CH2%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId--792099004%22%20id%3D%22toc-hId-1072038326%22%3EWhere%20can%20we%20see%20actual%20Free%2FBusy%20error%20message%3F%3C%2FH2%3E%0A%3CP%3EFirst%2C%20we%20need%20to%20understand%20in%20which%20direction%20we%20have%20a%20lookup%20problem.%20Please%20see%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fdemystifying-hybrid-free-busy-what-are-the-moving-parts%2Fba-p%2F607704%22%20target%3D%22_blank%22%3EPart%201%20for%20discussion%20of%20directionality%3C%2FA%3E.%20Sources%20of%20logs%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EOutlook%20logs%3C%2FLI%3E%0A%3CLI%3EOWA%20F12%20Network%20Tab%3C%2FLI%3E%0A%3CLI%3EFiddler%20%E2%80%93%20Outlook%20and%20OWA%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EThese%20steps%20are%20important%20in%20order%20for%20us%20to%20see%20the%20relevant%20message%20error%20for%20Free%2FBusy%20issues.%20Once%20we%20know%20the%20error%20message%2C%20it%E2%80%99s%20much%20easier%20to%20resolve%20the%20issue.%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-754197826%22%20id%3D%22toc-hId-1762599800%22%3E%3CSTRONG%3EOUTLOOK%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3E%3CSTRONG%3ENote%3C%2FSTRONG%3E%3A%20you%20will%20be%20able%20to%20see%20the%20Free%2FBusy%20error%20in%20plain%20text%20in%20Outlook%202010%20logs%20only%2C%20if%20you%20are%20using%20Outlook%202013%2F2016%2C%20you%20can%E2%80%99t%20see%20the%20error%20in%20the%20Outlook%20log%20and%20you%20would%20need%20to%20provide%20the%20Outlook%20ETL%20log%20containing%20the%20error%20to%20Microsoft%20Support%20to%20parse%20it.%20You%20will%20still%20be%20able%20to%20use%20Fiddler%20to%20see%20the%20Free%2FBusy%20error%20yourself%20if%20you%20have%20Outlook%202013%2F2016%20or%20you%20can%20use%20OWA%20F12%20method%20while%20reproducing%20issue%20in%20OWA%20client%20but%20that%20only%20works%20if%20the%20on-premises%20Exchange%20server%20version%20is%202013%20or%20above%20for%20the%20Source%20Mailbox%20user.%20For%20the%20Outlook%20F%2FB%20error%2C%20we%20need%20to%20first%20enable%20Outlook%20logging%20and%20after%20this%20we%20will%20reproduce%20issue%20(%5C%5C%5C%5C%5C%5C).%20After%20repro%2C%20we%20will%20collect%20Outlook%20logs.%20%3CSTRONG%3E1.%20Enable%20Outlook%20logging%3A%3C%2FSTRONG%3E%20Follow%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fkb%2F2862843%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ethis%20KB%20article%3C%2FA%3E%20and%20check%20the%20Enable%20troubleshooting%20logging%20(this%20requires%20restarting%20Outlook)%20option.%20Restart%20Outlook.%20%3CSTRONG%3E2.%20Reproduce%20the%20issue%20for%20the%20non-working%20direction.%3C%2FSTRONG%3E%20Suppose%20Free%2FBusy%20direction%20not%20working%20is%20cloud%20to%20on-premises%2C%20logged%20on%20as%20a%20cloud%20user%2C%20add%20some%20on-premises%20users%20to%20a%20meeting%20until%20you%20see%20the%20hash%20marks%20(instead%20of%20Free%2FBusy%20information).%20You%20do%20not%20need%20to%20save%20or%20send%20a%20meeting%20request.%20Note%20that%20if%20Outlook%20logging%20is%20turned%20on%2C%20you%20will%20see%20the%20following%20notification%20in%20Outlook%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_6.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20style%3D%22border%3A%200px%20currentcolor%3B%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_6_thumb.jpg%22%20border%3D%220%22%20alt%3D%22FB2_6%22%20title%3D%22FB2_6%22%20width%3D%22405%22%20height%3D%2238%22%20%2F%3E%3C%2FA%3E%20%3CSTRONG%3EExample%3A%20%3C%2FSTRONG%3E%20In%20this%20screenshot%2C%20Jane%20is%20a%20cloud%20user%20mailbox.%20Jane%20logged%20on%20to%20a%20mailbox%20using%20Outlook%202016%20and%20she%20is%20creating%20the%20meeting%20(organizer).%20She%20adds%203%20participants%3A%20ex2010mbx1%2C%20ex2013mbx1%20and%20Joe%20%E2%80%93%20who%20are%20all%20on-premises%20user%20mailboxes.%20Jane%20cannot%20see%20Free%2FBusy%20for%20any%20of%20them.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_7.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20style%3D%22border%3A%200px%20currentcolor%3B%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_7_thumb.jpg%22%20border%3D%220%22%20alt%3D%22FB2_7%22%20title%3D%22FB2_7%22%20width%3D%22668%22%20height%3D%22372%22%20%2F%3E%3C%2FA%3E%20%3CSTRONG%3E3.%20Collect%20Outlook%20logs%3C%2FSTRONG%3E%20%3CSTRONG%3EOutlook%202010%3C%2FSTRONG%3E%3A%20we%20need%20the%20AS.log%20from%20%3CSTRONG%3E%25temp%25%5COlkAS%3C%2FSTRONG%3E%20folder%20(reference%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fkb%2F2862843%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E)%20Open%20the%20AS.log%20and%20look%20for%20the%20error.%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_8.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_8_thumb.jpg%22%20border%3D%220%22%20alt%3D%22FB2_8%22%20title%3D%22FB2_8%22%20width%3D%22640%22%20height%3D%22195%22%20%2F%3E%3C%2FA%3E%20%3CEM%3E(click%20thumbnail%20to%20view%20larger)%3C%2FEM%3E%20%3CSTRONG%3EOutlook%202013%20%2F%202016%3C%2FSTRONG%3E%3A%20we%20need%20Outlook-%23%23%23%23%23.etl%20log%20from%20%3CSTRONG%3E%25temp%25%5COutlook%20Logging%3C%2FSTRONG%3E%20folder%20(reference%20%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fkb%2F2862843%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E).%20You%20would%20need%20to%20send%20the%20ETL%20file%20to%20Microsoft%20Support%20to%20get%20it%20analyzed%20as%20we%20are%20parsing%20this%20log%20with%20an%20internal%20tool.%20You%20might%20not%20know%20this%20but%20Hybrid%20free%2Fbusy%20support%20cases%20are%20free%20of%20charge!%20Of%20course%2C%20you%20can%20still%20use%20the%20other%20methods%20(fiddler%20for%20Outlook%2FOWA%20or%20browser%20for%20OWA)%20to%20see%20Free%2FBusy%20error%20yourself%2C%20however%20we%20(Support)%20might%20ask%20you%20additionally%20to%20get%20this%20log%20as%20in%20the%20Outlook%20ETL%20log%20we%20have%20the%20best%20logging%20for%20the%20Free%2FBusy%20errors.%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--1797959135%22%20id%3D%22toc-hId--44854663%22%3E%3CSTRONG%3EOWA%20%2F%20Outlook%20on%20the%20web%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3ECloud%20OWA%20F12%20Network%20tab%20You%20need%20to%20login%20to%20OWA%20as%20the%20source%20mailbox%2C%20hit%20F12%20(Developer%20Tools%20for%20browser)%20and%20select%20the%20Network%20Tab.%20You%20would%20then%20lookup%20Free%2FBusy%20for%20the%20target%20mailbox%20(reproduce%20the%20issue).%20Once%20you%20see%20the%20hashmarks%2C%20look%20for%20GetUserAvailabilityInternal%20Action%20then%20look%20at%20Response%20Body%20to%20see%20the%20error%20message.%20Note%3A%20The%20source%20mailbox%20needs%20to%20be%20hosted%20on%20Exchange%202013%20or%20above%20in%20on-premises%20or%20in%20Exchange%20Online%20for%20us%20to%20be%20able%20to%20see%20the%20error%20message%20in%20OWA%20using%20F12.%20This%20method%20will%20not%20work%20for%20Exchange%202010%20source%20mailboxes.%20This%20is%20how%20this%20could%20look%20like%20in%20Internet%20Explorer%20(similar%20in%20other%20browsers)%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_9.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_9_thumb.jpg%22%20border%3D%220%22%20alt%3D%22FB2_9%22%20title%3D%22FB2_9%22%20width%3D%22640%22%20height%3D%22407%22%20%2F%3E%3C%2FA%3E%20%3CEM%3E(click%20thumbnail%20to%20view%20larger)%3C%2FEM%3E%20Fiddler%20%E2%80%93%20OWA%20or%20Outlook%20You%20would%20need%20to%20download%20and%20install%20Fiddler%20tool%20and%20reproduce%20the%20Free%2FBusy%20issue%20in%20OWA%20or%20Outlook.%20If%20you%20reproduce%20the%20problem%20in%20OWA%2C%20you%20would%20search%20for%20GetUserAvailabilityInternal%20Action%20for%20owa%20service.svc%20entry%20and%20then%20look%20at%20JSON%20%2FRaw%20tab%20to%20see%20the%20error%20message.%20If%20the%20source%20mailbox%20is%20on%20Exchange%202010%20server%2C%20this%20is%20what%20you%E2%80%99ll%20need%20to%20do.%20%3CSTRONG%3EOWA%20View%20-%20Fiddler%3C%2FSTRONG%3E%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_10.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_10_thumb.jpg%22%20border%3D%220%22%20alt%3D%22FB2_10%22%20title%3D%22FB2_10%22%20width%3D%22640%22%20height%3D%22420%22%20%2F%3E%3C%2FA%3E%20%3CEM%3E(click%20thumbnail%20to%20view%20larger)%3C%2FEM%3E%20If%20you%20are%20logged%20in%20with%20Outlook%2C%20you%20would%20search%20for%20GetUserAvailabilityResponse%2C%20check%20the%20Raw%20tab%20and%20you%20can%20click%20on%20%E2%80%9CView%20in%20Notepad%E2%80%9D%20button%20on%20the%20right%20bottom%20corner.%20%3CSTRONG%3EOutlook%20view%20Exchange%20Online%20-%20Fiddler%3A%3C%2FSTRONG%3E%20%3CSTRONG%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_11.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_11_thumb.jpg%22%20border%3D%220%22%20alt%3D%22FB2_11%22%20title%3D%22FB2_11%22%20width%3D%22640%22%20height%3D%22285%22%20%2F%3E%3C%2FA%3E%20%3C%2FSTRONG%3E%3CEM%3E(click%20thumbnail%20to%20view%20larger)%3C%2FEM%3E%20%3CSTRONG%3EOutlook%20view%20Exchange%202010%20Source%20Mailbox%3C%2FSTRONG%3E%20-%20%3CSTRONG%3EFiddler%3C%2FSTRONG%3E%20%3CSTRONG%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_12.jpg%22%20target%3D%22_blank%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2018%2F03%2FFB2_12_thumb.jpg%22%20border%3D%220%22%20alt%3D%22FB2_12%22%20title%3D%22FB2_12%22%20width%3D%22640%22%20height%3D%22273%22%20%2F%3E%3C%2FA%3E%20%3C%2FSTRONG%3E%3CEM%3E(click%20thumbnail%20to%20view%20larger)%3C%2FEM%3E%20When%20troubleshooting%20Free%2FBusy%20issues%2C%20the%20following%20on-premises%20logs%20can%20be%20very%20useful%2C%20especially%20for%20Cloud%20to%20On-Premises%20Free%2FBusy%20direction.%20%3CEM%3E%3CSTRONG%3EIIS%20logs%20Default%20Web%20Site%20(DWS)%3C%2FSTRONG%3E%3C%2FEM%3E%20%25SystemDrive%25%5Cinetpub%5Clogs%5CLogFiles%5CW3SVC1%20Example%3A%20C%3A%5Cinetpub%5Clogs%5CLogFiles%5CW3SVC1%20Example%20of%20Autodiscover%20and%20EWS%20entries%20with%20IOC%20Enabled%20in%20IIS%20W3SVC1%20logs%3A%20%3CEM%3E%3CSTRONG%3EAutodiscover%20%E2%80%93%20OAUTH%20(autodiscover.svc%20without%20%2FWSSecurity)%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%0A%3CP%20class%3D%22code%22%3E2016-01-06%2017%3A45%3A27%2010.0.0.5%20POST%20%2F%3CSTRONG%3Eautodiscover%2Fautodiscover.svc%3C%2FSTRONG%3E%20%26amp%3BCorrelationID%3D%3CEMPTY%3E%3B%26amp%3BClientId%3DQNFNHKEEKYENCJITQQ%26amp%3BcafeReqId%3D7972d1fc-a9d9-44c6-8851-480d3601cbd7%3B%20443%20S2S~00000002-0000-0ff1-ce00-000000000000%20132.245.65.28%20%3CSTRONG%3E%3CI%3EASAutoDiscover%3C%2FI%3E%2FCrossForest%2FEmailDomain%3C%2FSTRONG%3E%2F%2F15.01.0361.007%20%3CSTRONG%3E%3CSPAN%20style%3D%22color%3A%20%23008000%3B%22%3E200%3C%2FSPAN%3E%20%3C%2FSTRONG%3E0%200%20109%3C%2FEMPTY%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3E%3CSTRONG%3EEWS%20%E2%80%93%20OAUTH%20(exchange.asmx%20without%20%2FWSSecurity)%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%0A%3CP%20class%3D%22code%22%3E2016-01-06%2017%3A45%3A27%2010.0.0.5%20POST%20%3CSTRONG%3E%2Fews%2Fexchange.asmx%3C%2FSTRONG%3E%20%26amp%3BCorrelationID%3D%3CEMPTY%3E%3B%26amp%3BClientId%3DWSIVGUUAUWWRFACJBWDA%26amp%3BcafeReqId%3D6ce8864c-74a0-4ad2-a3dc-7b69e0415403%3B%20443%20%3CUNVERIFIED%3Eactas1(sip%3Ajoe%40contoso.com%7Csmtp%3Ajoe%40contoso.com%7Cupn%3Ajoe%40contoso.com)%20132.245.65.28%20%3CSTRONG%3E%3CI%3EASProxy%3C%2FI%3E%2FCrossForest%2FEmailDomain%3C%2FSTRONG%3E%2F%2F15.01.0361.007%20%3CSTRONG%3E%3CSPAN%20style%3D%22color%3A%20%23008000%3B%22%3E200%3C%2FSPAN%3E%20%3C%2FSTRONG%3E0%200%20703%3C%2FUNVERIFIED%3E%3C%2FEMPTY%3E%3C%2FP%3E%0A%3CP%3EExample%20of%20EWS%20entry%20with%20Organization%20Relationship%20Enabled%20in%20IIS%20W3SVC1%20logs%3A%20%3CEM%3E%3CSTRONG%3EEWS%20%E2%80%93%20DAUTH%20(exchange.asmx%20with%20%2FWSSecurity)%3C%2FSTRONG%3E%3C%2FEM%3E%3C%2FP%3E%0A%3CP%20class%3D%22code%22%3E2016-01-06%2018%3A04%3A41%2010.0.0.5%20POST%20%3CSTRONG%3E%2Fews%2Fexchange.asmx%2FWSSecurity%3C%2FSTRONG%3E%20%26amp%3BCorrelationID%3D%3CEMPTY%3E%3B%26amp%3BClientId%3DVOMGJKAWURSVKOXQLBVA%26amp%3BcafeReqId%3D18fd3a2e-7b1c-4828-8943-6b20912e2e44%3B%20443%20-%20132.245.65.28%20%3CSTRONG%3E%3CI%3EASProxy%3C%2FI%3E%2FCrossForest%2FEmailDomain%3C%2FSTRONG%3E%2F%2F15.01.0361.007%20%3CSPAN%20style%3D%22color%3A%20%23008000%3B%22%3E%3CSTRONG%3E200%3C%2FSTRONG%3E%20%3C%2FSPAN%3E0%200%20296%3C%2FEMPTY%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3E%3CSTRONG%3EIIS%20logs%20Exchange%20BackEnd%20(BE)%3C%2FSTRONG%3E%3C%2FEM%3E%20%25SystemDrive%25%5Cinetpub%5Clogs%5CLogFiles%5CW3SVC2%20Example%3A%20C%3A%5Cinetpub%5Clogs%5CLogFiles%5CW3SVC2%20Example%20of%20EWS%20entry%20with%20Organization%20Relationship%20Enabled%20(DAUTH)%20in%20IIS%20W3SVC2%20logs%3A%3C%2FP%3E%0A%3CP%20class%3D%22code%22%3E2016-01-06%2018%3A04%3A41%20fe80%3A%3Af17f%3Abeef%3Aa5e3%3A7d3c%2525%20POST%20%3CSTRONG%3E%2Fews%2Fexchange.asmx%2FWSSecurity%3C%2FSTRONG%3E%20-%20444%20-%20fe80%3A%3Af17f%3Abeef%3Aa5e3%3A7d3c%2525%20%3CSTRONG%3E%3CI%3EASProxy%3C%2FI%3E%2FCrossForest%2FEmailDomain%3C%2FSTRONG%3E%2F%2F15.01.0361.007%20%3CSPAN%20style%3D%22color%3A%20%23008000%3B%22%3E%3CSTRONG%3E200%3C%2FSTRONG%3E%20%3C%2FSPAN%3E0%200%2093%3C%2FP%3E%0A%3CP%3E%3CEM%3E%3CSTRONG%3EHTTPProxy%20logs%20for%20Autodiscover%3C%2FSTRONG%3E%3C%2FEM%3E%20%25ExchangeInstallPath%25Logging%5CHttpProxy%5CAutodiscover%20Example%3A%20C%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV15%5CLogging%5CHttpProxy%5CAutodiscover%20Example%20of%20Autodiscover%20entry%20with%20Organization%20Relationship%20Enabled%20(DAUTH)%3C%2FP%3E%0A%3CP%20class%3D%22code%22%3E2016-01-06T18%3A05%3A20.552Z%2Cbcdfbed5-f11f-4250-a616-e38cb475cd3f%2C15%2C0%2C1104%2C2%2C%2CAutodiscover%2Cautodiscover.contoso.com%2C%2F%3CSTRONG%3Eautodiscover%2Fautodiscover.svc%20%2FWSSecurity%3C%2FSTRONG%3E%2C%2C%2Cfalse%2C%2Ccontoso.com%2CSmtp~joe%40contoso.com%2CASAutoDiscover%2FCrossForest%2FEmailDomain%2F%20%2F15.01.0361.007%2C132.245.65.28%2Cexch-2013%2C200%2C200%2C%2CPOST%2CProxy%2Cexch-2013.contoso.com%2C15.00.1104.000%2CIntraForest%2CAnchorMailboxHeader-SMTP%2C%5B%E2%80%A6%5D%2CBeginRequest%3D2016-01-06T18%3A05%3A20.192Z%3BCorrelationID%3D%3CEMPTY%3E%3BProxyState-Run%3DNone%3BFEAuth%3DBEVersion-1941996624%3B%3CSPAN%20style%3D%22color%3A%20%23008000%3B%22%3E%3CSTRONG%3ENewConnection%3Dfe80%3A%3Af17f%3Abeef%3Aa5e3%3A7d3c%2525%3C%2FSTRONG%3E%3C%2FSPAN%3E%26amp%3B0%3B%3C%2FEMPTY%3E%3C%2FP%3E%0A%3CP%3E%3CEM%3E%3CSTRONG%3EHTTPProxy%20logs%20for%20EWS%3C%2FSTRONG%3E%3C%2FEM%3E%20%25ExchangeInstallPath%25Logging%5CHttpProxy%5CEws%20Example%3A%20C%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV15%5CLogging%5CHttpProxy%5CEws%20Example%20of%20EWS%20entry%20with%20Organization%20Relationship%20Enabled%20(DAUTH)%3A%3C%2FP%3E%0A%3CP%20class%3D%22code%22%3E2016-01-06T18%3A04%3A41.490Z%2C4757ab2c-8ccc-4d1a-ae39-0780ecc8eabb%2C15%2C0%2C1104%2C2%2C%7B02CD833F-18AB-413A-83CB-0E86F4DA5362%7D%2CEws%2Cmail.contoso.com%2C%3CSTRONG%3E%2Fews%2Fexchange.asmx%2FWSSecurity%3C%2FSTRONG%3E%2C%2C%2Cfalse%2C%2Ccontoso.com%2C%20Smtp~%3CSTRONG%3Ejoe%40contoso.com%2CASProxy%2FCrossForest%2FEmailDomain%3C%2FSTRONG%3E%2F%2F15.01.0361.007%2C132.245.65.28%2Cexch-2013%2C200%2C200%2C%2CPOST%2CProxy%2Cexch-2013.contoso.com%2C15.00.1104.000%2CIntraForest%2CAnchorMailboxHeader-SMTP%2C%5B%E2%80%A6%5D%2CBeginRequest%3D2016-01-06T18%3A04%3A41.380Z%3B%3C%2FP%3E%0A%3CP%3E%3CEM%3E%3CSTRONG%3EEWS%20logs%3C%2FSTRONG%3E%3C%2FEM%3E%20%25ExchangeInstallPath%25Logging%5CEws%20Example%3A%20C%3A%5CProgram%20Files%5CMicrosoft%5CExchange%20Server%5CV15%5CLogging%5CEws%20Example%20of%20EWS%20entry%20with%20Organization%20Relationship%20Enabled%20(DAUTH)%3A%3C%2FP%3E%0A%3CP%20class%3D%22code%22%3E2016-01-06T18%3A04%3A41.490Z%2C4757ab2c-8ccc-4d1a-ae39-0780ecc8eabb%2C15%2C0%2C1104%2C2%2C%7B02CD833F-18AB-413A-83CB-0E86F4DA5362%7D%2C%20External%2Ctrue%2C%3CSTRONG%3Ejane%40contoso.mail.onmicrosoft.com%2C%2C%20ASProxy%2FCrossForest%2FEmailDomain%3C%2FSTRONG%3E%2F%2F15.01.0361.007%2CTarget%3DNone%3BReq%3DExchange2012%2FExchange2013%3B%20%2C132.245.65.28%2Cexch-2013%2Cexch-2013.contoso.com%2C%3CSTRONG%3EGetUserAvailability%2C200%3C%2FSTRONG%3E%2C12150%2C%2C%2C%2C%2C%2Cebd34d71ac7342c19d947d881db4ad55%2Cf866c73e-6c91-475e-bdec-0428bdeaa423%2CPrimaryServer%3B%20%3CSTRONG%3ERequester%3Djane%40contoso.mail.onmicrosoft.com%3C%2FSTRONG%3E%3B%20Failures%3D0%3C%2FP%3E%0A%3CP%3E%3CEM%3E%3CSTRONG%3EEvent%20Viewer%20Application%20logs%20on%20Exchange%20Server%3C%2FSTRONG%3E%3C%2FEM%3E%20References%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Faa997769(v%3Dexchg.65).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E%20and%20%3CA%20href%3D%22https%3A%2F%2Ftechnet.microsoft.com%2Fen-us%2Flibrary%2Fdd335139(v%3Dexchg.141).aspx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%20Example%20of%20Event%20ID%204002%20for%20MSExchange%20Availability%3A%3C%2FP%3E%0A%3CP%20class%3D%22code%22%3ELog%20Name%3A%20Application%3CBR%20%2F%3ESource%3A%20MSExchange%20Availability%3CBR%20%2F%3EEvent%20ID%3A%204002%3CBR%20%2F%3ETask%20Category%3A%20Availability%20Service%3CBR%20%2F%3ELevel%3A%20Error%3CBR%20%2F%3EDescription%3A%3CBR%20%2F%3EProcess%204568%3A%20ProxyWebRequest%20CrossSite%20from%20S-1-5-21-391720751-1508397712-925700815-508779%20to%20%3CA%20href%3D%22https%3A%2F%2Fhybrid.contoso.com%2Fews%2Fexchange.asmx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fhybrid.contoso.com%2Fews%2Fexchange.asmx%3C%2FA%3E%20failed.%20Caller%20SIDs%3A%20NetworkCredentials.%20The%20exception%20returned%20is%20Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException%3A%20System.Web.Services.Protocols.SoapException%3A%20You%20have%20exceeded%20the%20available%20concurrent%20connections%20for%20your%20account.%20Try%20again%20once%20your%20other%20requests%20have%20completed.%3CBR%20%2F%3Eat%20System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage%20message%2C%20WebResponse%20response%2C%20Stream%20responseStream%2C%20Boolean%20asyncCall)%3C%2FP%3E%0A%3CP%3E%3CEM%3E%3CSTRONG%3EIIS%20tracing%20for%20the%20error%20code%20in%20the%20IIS%20logs%3C%2FSTRONG%3E%3C%2FEM%3E%20Reference%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fprevious-versions%2Fwindows%2Fit-pro%2Fwindows-server-2008-R2-and-2008%2Fcc725786(v%3Dws.10)%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E.%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--55148800%22%20id%3D%22toc-hId--1852309126%22%3EFree%2FBusy%20errors%20and%20fixes%3C%2FH3%3E%0A%3CP%3ERay%20Fong%20and%20I%20made%20a%20table%20(ATTACHED)%20with%20the%20Free%2FBusy%20errors%20encountered%20so%20far%20in%20Support%20and%20their%20possible%20resolutions.%20We%20cannot%20cover%20%3CI%3Eall%3C%2FI%3E%20possible%20scenarios%20and%20errors%20even%20though%20we%20have%20a%20good-sized%20list.%20This%20is%20meant%20to%20illustrate%20ways%20we%20can%20resolve%20specific%20errors%20and%20these%20suggestions%20might%20not%20work%20for%20you%20even%20if%20you%20have%20the%20same%20error.%20If%20you%20know%20the%20exact%20Free%2FBusy%20error%20that%20you%20get%20and%20checked%20configuration%20as%20discussed%20in%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fdemystifying-hybrid-free-busy-what-are-the-moving-parts%2Fba-p%2F607704%22%20target%3D%22_blank%22%3Epart%201%20of%20this%20series%3C%2FA%3E%2C%20this%20is%20already%20a%20tremendous%20progress%2C%20and%20this%20will%20help%20us%20resolve%20your%20issue%20faster.%20Of%20course%2C%20you%20can%20follow%20these%20suggestions%20on%20your%20own%20as%20most%20of%20the%20actions%20are%20harmless%20but%20if%20you%20don%E2%80%99t%20feel%20confident%20in%20troubleshooting%20on%20your%20own%20or%20you%20fear%20that%20actions%20are%20dangerous%20or%20irreversible%2C%20please%20contact%20us.%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-1687661535%22%20id%3D%22toc-hId-635203707%22%3E%3CSTRONG%3EFree%2FBusy%20Errors%20discussed%20in%20the%20attached%20table%3A%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F01%2FFB_Errors.FixesV6.pdf%22%20target%3D%22_blank%22%3EFB_Errors.FixesV6%3C%2FA%3E%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CAn%20internal%20server%20error%20occurred.%20The%20operation%20failed%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%22The%20remote%20user%20mailbox%20must%20specify%20the%20the%20explicit%20local%20mailbox%20in%20the%20header%22%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%22An%20error%20occurred%20when%20verifying%20security%20for%20the%20message%22%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%22Unable%20to%20connect%20to%20the%20remote%20server%22%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CAutodiscover%20failed%20for%20email%20address%20%26lt%3B%26gt%3B%20with%20error%20%E2%80%98The%20request%20failed%20with%20HTTP%20status%20404%3A%20Not%20Found%E2%80%99%20%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CThe%20request%20failed%20with%20HTTP%20status%20401%3A%20Unauthorized%20-%20The%20user%20specified%20by%20the%20user-context%20in%20the%20token%20is%20ambiguous%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%22An%20existing%20connection%20was%20forcibly%20closed%20by%20the%20remote%20host%20-%20An%20unexpected%20error%20occurred%20on%20a%20receive%20%22%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%22An%20existing%20connection%20was%20forcibly%20closed%20by%20the%20remote%20host%20-%20An%20unexpected%20error%20occurred%20on%20a%20send%20%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%22Configuration%20information%20for%20forest%2Fdomain%20could%20not%20be%20found%20in%20Active%20Directory%22%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%22Proxy%20web%20request%20failed.%2Cinner%20exception%3A%20The%20request%20failed%20with%20HTTP%20status%20401%3A%20Unauthorized.%22%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%22The%20response%20from%20the%20Autodiscover%20service%20at%20'https%3A%2F%2Fautodiscover%2Fautodiscover.svc%2FWSSecurity'%20failed%20due%20to%20an%20error%20in%20user%20setting%20'ExternalEwsUrl'.%20Error%20message%3A%20InvalidUser.%22%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CThe%20caller%20does%20not%20have%20access%20to%20free%2Fbusy%20data%22%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CThe%20request%20failed%20with%20HTTP%20status%20403%3A%20Forbidden%20(The%20server%20denied%20the%20specified%20Uniform%20Resource%20Locator%20(URL).%20%E2%80%9C%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CUnable%20to%20resolve%20e-mail%20address%20user%40notes.domain.com%20to%20an%20Active%20Directory%20object%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CAn%20error%20occurred%20when%20processing%20the%20security%20tokens%20in%20the%20message.%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CThe%20cross-organization%20request%20for%20mailbox%20yyy%40contoso.com%20is%20not%20allowed%20because%20the%20requester%20is%20from%20a%20different%20organization%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CThe%20request%20failed%20with%20HTTP%20status%20401%3A%20Unauthorized%20-%20Microsoft.Exchange.Security.OAuth.OAuth%20TokenRequestFailedException%3A%20Missing%20signing%20certificate%20%E2%80%9C%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CThe%20application%20is%20missing%20a%20linked%20account%20for%20RBAC%20roles%2C%20or%20the%20linked%20account%20has%20no%20RBAC%20role%20assignments%2C%20or%20the%20calling%20users%20account%20is%20logon%20disabled%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CThe%20entered%20and%20stored%20passwords%20do%20not%20match%E2%80%9C%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CThe%20password%20has%20to%20be%20changed.%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CThe%20password%20for%20the%20account%20has%20expired%E2%80%9D%20or%20%E2%80%9CProvision%20is%20needed%20before%20federated%20account%20can%20be%20logged%20in%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CThe%20request%20timed%20out%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CThe%20specified%20member%20name%20is%20either%20invalid%20or%20empty%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CThe%20result%20set%20contains%20too%20many%20calendar%20entries%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CThe%20request%20failed%20with%20HTTP%20status%20401%3A%20Unauthorized%20-%20The%20token%20has%20an%20invalid%20signature.%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CThe%20request%20failed%20with%20HTTP%20status%20401%3A%20Unauthorized%20-%20Client%20assertion%20contains%20an%20invalid%20signature.%20%5BReason%20-%20The%20key%20was%20not%20found.%2C%20Thumbprint%20of%20key%20used%20by%20client%3A%20'XXX%E2%80%99%20%E2%80%9C%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CProxy%20web%20request%20failed.%2C%20inner%20exception%3A%20Response%20is%20not%20well-formed%20XML%20%E2%80%9C%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CFailed%20to%20communicate%20with%20%3CA%20href%3D%22https%3A%2F%2Flogin.microsoftonline.com%2FextSTS.srf%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Flogin.microsoftonline.com%2FextSTS.srf%3C%2FA%3E.%2C%20inner%20exception%3A%20Unable%20to%20connect%20to%20the%20remote%20server%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CAutodiscover%20failed%20for%20E-Mail%20Address%20joe%40contoso.com%20with%20error%20System.Net.WebException%3A%20The%20remote%20name%20could%20not%20be%20resolved%3A%20'mail.contoso.com'%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CFailed%20to%20get%20ASURL.%20Error%208004010F%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CProxy%20web%20request%20failed.%20%2C%20inner%20exception%3A%20System.Net.WebException%3A%20The%20request%20failed%20with%20the%20error%20message%3A%20--%20%26amp%3Blt%3Bhead%26amp%3Bgt%3B%26amp%3Blt%3Btitle%26amp%3Bgt%3BObject%20moved%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%26nbsp%3B%E2%80%9CThe%20request%20was%20aborted%3A%20Could%20not%20create%20SSL%2FTLS%20secure%20channel.%E2%80%9D%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3E%E2%80%9CThe%20user%20specified%20by%20the%20user-context%20in%20the%20token%20does%20not%20exist.%22%3Berror_category%3D%22invalid_user%E2%80%9C%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%26nbsp%3B%3CSPAN%3E%E2%80%9CThe%20hostname%20component%20of%20the%20audience%20claim%20value%20'https%3A%2F%2F%3CHYBRID.DOMAIN.COM%3E%E2%80%99%20is%20invalid%22%3Berror_category%3D%22invalid_resource%E2%80%9C%3C%2FHYBRID.DOMAIN.COM%3E%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FOL%3E%0A%3CP%3EThanks%20to%20all%20that%20contributed%20to%20this%20content%3A%20Ray%20Fong%2C%20Nino%20Bilic%2C%20Tim%20Heeney%2C%20Greg%20Taylor%20and%20Brian%20Day.%20%3CSPAN%20class%3D%22author%22%3EMirela%20Buruiana%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-607727%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Edocumentation%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Eexchange%202010%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202013%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%202016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETips%20'n%20Tricks%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ETroubleshooting%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1482017%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1482017%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22ms-Stack%20css-100%22%3E%3CDIV%20class%3D%22ms-Stack%20css-204%22%3E%3CDIV%20class%3D%22ms-Stack%20css-226%22%3E%3CDIV%20class%3D%22ms-Stack%20css-232%22%3E%3CDIV%20class%3D%22ms-Stack%20css-248%22%3E%3CDIV%20class%3D%22ms-Stack%20css-64%22%3E%3CDIV%20class%3D%22ms-Stack%20css-250%22%3E%3CDIV%20class%3D%22ms-Stack%20root-253%22%3E%3CDIV%20class%3D%22ms-Stack%20root-260%22%3E%3CDIV%20class%3D%22ms-Stack%20css-64%22%3E%3CDIV%20class%3D%22ms-Stack%20css-250%22%3E%3CSPAN%20class%3D%22css-182%22%3EAny%20thoughts%20on%20what%20the%20issue%20is%3F%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22ms-Stack%20css-250%22%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%20class%3D%22ms-Stack%20css-250%22%3E%3CSPAN%20class%3D%22css-182%22%3EPerforming%20Free%2FBusy%20Lookup%3C%2FSPAN%3E%3CSPAN%20class%3D%22css-182%22%3EFree%2FBusy%20Lookup%20failed.%3C%2FSPAN%3E%3CDIV%20class%3D%22ms-Stack%20root-253%22%3E%3CDIV%20class%3D%22ms-Stack%20css-125%22%3E%3CSPAN%20class%3D%22ms-Button-flexContainer%20flexContainer-54%22%3E%3CI%3E%EE%9C%8E%3C%2FI%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22css-182%22%3EAdditional%20Details%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22ms-Stack%20root-260%22%3E%3CSPAN%20class%3D%22css-182%22%3E%3CU%3EFree%2FBusy%20Lookup%20failed%20with%20exception%3A%20Proxy%20web%20request%20failed.%20%2C%20inner%20exception%3A%20System.Net.WebException%3A%20The%20request%20failed%20with%20HTTP%20status%20504%3A%20Gateway%20Timeout.%3C%2FU%3E%20at%20System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage%20message%2C%20WebResponse%20response%2C%20Stream%20responseStream%2C%20Boolean%20asyncCall)%20at%20System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult%20asyncResult)%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult%20asyncResult)%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest%20proxyWebRequest%2C%20QueryList%20queryList%2C%20IService%20service%2C%20IAsyncResult%20asyncResult)%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult%20asyncResult)%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22ms-Stack%20css-110%22%3E%3CDIV%20class%3D%22ms-Stack%20css-112%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1482053%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1482053%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F707164%22%20target%3D%22_blank%22%3E%40chris280%3C%2FA%3E%26nbsp%3B%2C%20I%20assume%20it%20is%20from%20EXO%20to%20Exchange%20onpremises%3F%20it%20fails%20at%20ews%20request%20and%20usually%20network%20related%20issues.%20You%20need%20to%20check%20httpproxy%20logs%20%2F%20iis%20logs%20to%20see%20if%20the%20request%20reaches%20Exchange%20when%20you%20repro%20the%20issue%20or%20it%20is%20stuck%20at%20some%20network%20device%20in%20front.%20If%20you%20are%20in%20Modern%20Hybrid%20Topology%20and%20your%20Cloud%20IntraOrganizationConnector%20or%20OrganizationRelationship's%20TargetSharingEpr%20is%20pointing%20to%20the%20Hybrid%20Agent%2C%20you%20need%20to%20see%20if%20the%20agent%20is%20active%20%2Fstill%20installed%20and%20your%20firewall%2F%20proxy%20is%20allowing%20outbound%20traffic%20to%20EXO.%20You%20can%20check%20the%20troubleshooting%20suggestions%20from%20Scenario%201%20from%20my%20other%20blog%20on%20Hybrid%20Migration%20Endpoints%20(EWS)%2C%20these%20are%20applicable%20also%20here%20if%20f%2Fb%20direction%20is%20cloud%20-%26gt%3B%20onpremises%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Ftroubleshooting-hybrid-migration-endpoints-in-classic-and-modern%2Fba-p%2F953006%26nbsp%3B%26nbsp%3B%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Ftroubleshooting-hybrid-migration-endpoints-in-classic-and-modern%2Fba-p%2F953006%3C%2FA%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1750863%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1750863%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Mirela_Buru%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20an%20issue%20with%20not%20see%20free%2Fbusy%20from%20only%20online%20exchange%20to%20on-prem%20exchange.%20I%20have%20reviewed%20you%20post%20(great)%20and%20have%20a%20getuseravailabiltyinternal%20that%20is%20kind%20of%20like%20%233%20from%20your%20list%20but%20not%20quite.%20We%20suspect%20that%20something%20on%20our%20cloud%20configuration%20is%20not%20correct.%20Do%20you%20have%20any%20thoughts%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%7B%22Header%22%3A%7B%22ServerVersionInfo%22%3A%7B%22MajorVersion%22%3A15%2C%22MinorVersion%22%3A20%2C%22MajorBuildNumber%22%3A3433%2C%22MinorBuildNumber%22%3A45%2C%22Version%22%3A%22V2018_01_08%22%7D%7D%2C%22Body%22%3A%7B%22Responses%22%3A%5B%7B%22ResponseMessage%22%3A%7B%22__type%22%3A%22SingleResponseMessage%3A%23Exchange%22%2C%22MessageText%22%3A%22Proxy%20web%20request%20failed.%20%2C%20inner%20exception%3A%20System.Web.Services.Protocols.SoapHeaderException%3A%20An%20error%20occurred%20when%20verifying%20security%20for%20the%20message.%5Cr%5Cn%20at%20System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage%20message%2C%20WebResponse%20response%2C%20Stream%20responseStream%2C%20Boolean%20asyncCall)%5Cr%5Cn%20at%20System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult%20asyncResult)%5Cr%5Cn%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult%20asyncResult)%5Cr%5Cn%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest%20proxyWebRequest%2C%20QueryList%20queryList%2C%20IService%20service%2C%20IAsyncResult%20asyncResult)%5Cr%5Cn%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult%20asyncResult)%5Cr%5Cn%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()%22%2C%22ResponseCode%22%3A%22ErrorProxyRequestProcessingFailed%22%2C%22MessageXml%22%3A%22%5Cr%5Cn%3CXMLNODEARRAY%20t%3D%22%5C%26quot%3B%26lt%3BA%22%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ftypes%5C%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ftypes%5C%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ftypes%5C%3C%2FA%3E%22%20xmlns%3Am%3D%5C%22%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2F%22%20target%3D%22_blank%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Fmessages%5C%22%26gt%3B%5Cr%5Cn%3C%2FA%3E%20%3CEXCEPTIONTYPE%20xmlns%3D%22%5C%26quot%3B%26lt%3BA%22%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%26quot%3B%26gt%3BProxyWebRequestProcessingException%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%22%26gt%3BProxyWebRequestProcessingException%3C%2FA%3E%3C%2FEXCEPTIONTYPE%3E%5Cr%5Cn%20%3CEXCEPTIONCODE%20xmlns%3D%22%5C%26quot%3B%26lt%3BA%22%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%26quot%3B%26gt%3B5016%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%22%26gt%3B5016%3C%2FA%3E%3C%2FEXCEPTIONCODE%3E%5Cr%5Cn%20%3CEXCEPTIONSERVERNAME%20xmlns%3D%22%5C%26quot%3B%26lt%3BA%22%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%26quot%3B%26gt%3BCH2PR19MB3832%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%22%26gt%3BCH2PR19MB3832%3C%2FA%3E%3C%2FEXCEPTIONSERVERNAME%3E%5Cr%5Cn%20%3CEXCEPTIONMESSAGE%20xmlns%3D%22%5C%26quot%3B%26lt%3BA%22%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%26quot%3B%26gt%3BProxy%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%22%26gt%3BProxy%3C%2FA%3E%20web%20request%20failed.%20%2C%20inner%20exception%3A%20An%20error%20occurred%20when%20verifying%20security%20for%20the%20message.%20LID%3A%2059916%3C%2FEXCEPTIONMESSAGE%3E%5Cr%5Cn%3C%2FXMLNODEARRAY%3E%22%2C%22ResponseClass%22%3A%22Error%22%7D%2C%22CalendarView%22%3A%7B%22MergedFreeBusy%22%3Anull%2C%22Items%22%3Anull%2C%22WorkingHours%22%3Anull%2C%22FreeBusyViewType%22%3A%22None%22%7D%7D%5D%2C%22ResponseCode%22%3A%22NoError%22%2C%22ResponseClass%22%3A%22Success%22%7D%7D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks!%3C%2FP%3E%3CP%3EEric%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1750985%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1750985%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Mirela_Buru%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20an%20issue%20with%20not%20seeing%20free%2Fbusy%20from%20only%20online%20exchange%20to%20on-prem%20exchange%20(works%20in%20the%20other%20direction%20fine)%20I%20have%20reviewed%20you%20post%20(great)%20and%20have%20a%20getuseravailabiltyinternal%20that%20is%20kind%20of%20like%20%233%20from%20your%20list%20but%20not%20quite.%20We%20suspect%20that%20something%20on%20our%20cloud%20configuration%20is%20not%20correct.%20Do%20you%20have%20any%20thoughts%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%7B%22Header%22%3A%7B%22ServerVersionInfo%22%3A%7B%22MajorVersion%22%3A15%2C%22MinorVersion%22%3A20%2C%22MajorBuildNumber%22%3A3433%2C%22MinorBuildNumber%22%3A45%2C%22Version%22%3A%22V2018_01_08%22%7D%7D%2C%22Body%22%3A%7B%22Responses%22%3A%5B%7B%22ResponseMessage%22%3A%7B%22__type%22%3A%22SingleResponseMessage%3A%23Exchange%22%2C%22MessageText%22%3A%22Proxy%20web%20request%20failed.%20%2C%20inner%20exception%3A%20System.Web.Services.Protocols.SoapHeaderException%3A%20An%20error%20occurred%20when%20verifying%20security%20for%20the%20message.%5Cr%5Cn%20at%20System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage%20message%2C%20WebResponse%20response%2C%20Stream%20responseStream%2C%20Boolean%20asyncCall)%5Cr%5Cn%20at%20System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult%20asyncResult)%5Cr%5Cn%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult%20asyncResult)%5Cr%5Cn%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest%20proxyWebRequest%2C%20QueryList%20queryList%2C%20IService%20service%2C%20IAsyncResult%20asyncResult)%5Cr%5Cn%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult%20asyncResult)%5Cr%5Cn%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()%22%2C%22ResponseCode%22%3A%22ErrorProxyRequestProcessingFailed%22%2C%22MessageXml%22%3A%22%5Cr%5Cn%3CXMLNODEARRAY%20t%3D%22%5C%26quot%3B%26lt%3BA%22%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ftypes%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ftypes%5C%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ftypes%5C%3C%2FA%3E%22%20xmlns%3Am%3D%5C%22%3CA%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Fmessages%5C%22%26gt%3B%5Cr%5Cn%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEXCEPTIONTYPE%20xmlns%3D%22%5C%26quot%3B%26lt%3BA%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%26quot%3B%26gt%3BProxyWebRequestProcessingException%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%22%26gt%3BProxyWebRequestProcessingException%3C%2FA%3E%3C%2FEXCEPTIONTYPE%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEXCEPTIONCODE%20xmlns%3D%22%5C%26quot%3B%26lt%3BA%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%26quot%3B%26gt%3B5016%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%22%26gt%3B5016%3C%2FA%3E%3C%2FEXCEPTIONCODE%3E%5Cr%5Cn%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEXCEPTIONSERVERNAME%20xmlns%3D%22%5C%26quot%3B%26lt%3BA%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%26quot%3B%26gt%3BCH2PR19MB3832%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%22%26gt%3BCH2PR19MB3832%3C%2FA%3E%3C%2FEXCEPTIONSERVERNAME%3E%5Cr%5Cn%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEXCEPTIONMESSAGE%20xmlns%3D%22%5C%26quot%3B%26lt%3BA%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%26quot%3B%26gt%3BProxy%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%22%26gt%3BProxy%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eweb%20request%20failed.%20%2C%20inner%20exception%3A%20An%20error%20occurred%20when%20verifying%20security%20for%20the%20message.%20LID%3A%2059916%3C%2FEXCEPTIONMESSAGE%3E%5Cr%5Cn%3C%2FXMLNODEARRAY%3E%22%2C%22ResponseClass%22%3A%22Error%22%7D%2C%22CalendarView%22%3A%7B%22MergedFreeBusy%22%3Anull%2C%22Items%22%3Anull%2C%22WorkingHours%22%3Anull%2C%22FreeBusyViewType%22%3A%22None%22%7D%7D%5D%2C%22ResponseCode%22%3A%22NoError%22%2C%22ResponseClass%22%3A%22Success%22%7D%7D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20also%20ran%26nbsp%3B%3CSPAN%3EGet-IntraOrganizationConnector%26nbsp%3B%20on%20both%20on-prem%20and%20exch%20online%20and%20both%20do%20not%20show%20any%20output%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks!%3C%2FP%3E%3CP%3EEric%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1751366%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1751366%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Mirela_Buru%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20an%20issue%20with%20not%20seeing%20free%2Fbusy%20from%20only%20online%20exchange%20to%20on-prem%20exchange%20(works%20in%20the%20other%20direction%20fine)%20I%20have%20reviewed%20you%20post%20(great)%20and%20have%20a%20getuseravailabiltyinternal%20that%20is%20kind%20of%20like%20%233%20from%20your%20list%20but%20not%20quite.%20We%20suspect%20that%20something%20on%20our%20cloud%20configuration%20is%20not%20correct.%20Do%20you%20have%20any%20thoughts%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%7B%22Header%22%3A%7B%22ServerVersionInfo%22%3A%7B%22MajorVersion%22%3A15%2C%22MinorVersion%22%3A20%2C%22MajorBuildNumber%22%3A3433%2C%22MinorBuildNumber%22%3A45%2C%22Version%22%3A%22V2018_01_08%22%7D%7D%2C%22Body%22%3A%7B%22Responses%22%3A%5B%7B%22ResponseMessage%22%3A%7B%22__type%22%3A%22SingleResponseMessage%3A%23Exchange%22%2C%22MessageText%22%3A%22Proxy%20web%20request%20failed.%20%2C%20inner%20exception%3A%20System.Web.Services.Protocols.SoapHeaderException%3A%20An%20error%20occurred%20when%20verifying%20security%20for%20the%20message.%5Cr%5Cn%20at%20System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage%20message%2C%20WebResponse%20response%2C%20Stream%20responseStream%2C%20Boolean%20asyncCall)%5Cr%5Cn%20at%20System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult%20asyncResult)%5Cr%5Cn%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult%20asyncResult)%5Cr%5Cn%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest%20proxyWebRequest%2C%20QueryList%20queryList%2C%20IService%20service%2C%20IAsyncResult%20asyncResult)%5Cr%5Cn%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult%20asyncResult)%5Cr%5Cn%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()%22%2C%22ResponseCode%22%3A%22ErrorProxyRequestProcessingFailed%22%2C%22MessageXml%22%3A%22%5Cr%5Cn%3CXMLNODEARRAY%20t%3D%22%5C%26quot%3B%26lt%3BA%22%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ftypes%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ftypes%5C%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ftypes%5C%3C%2FA%3E%22%20xmlns%3Am%3D%5C%22%3CA%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Fmessages%5C%22%26gt%3B%5Cr%5Cn%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEXCEPTIONTYPE%20xmlns%3D%22%5C%26quot%3B%26lt%3BA%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%26quot%3B%26gt%3BProxyWebRequestProcessingException%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%22%26gt%3BProxyWebRequestProcessingException%3C%2FA%3E%3C%2FEXCEPTIONTYPE%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEXCEPTIONCODE%20xmlns%3D%22%5C%26quot%3B%26lt%3BA%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%26quot%3B%26gt%3B5016%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%22%26gt%3B5016%3C%2FA%3E%3C%2FEXCEPTIONCODE%3E%5Cr%5Cn%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEXCEPTIONSERVERNAME%20xmlns%3D%22%5C%26quot%3B%26lt%3BA%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%26quot%3B%26gt%3BCH2PR19MB3832%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%22%26gt%3BCH2PR19MB3832%3C%2FA%3E%3C%2FEXCEPTIONSERVERNAME%3E%5Cr%5Cn%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CEXCEPTIONMESSAGE%20xmlns%3D%22%5C%26quot%3B%26lt%3BA%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3E%3CA%20href%3D%22http%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%26quot%3B%26gt%3BProxy%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fschemas.microsoft.com%2Fexchange%2Fservices%2F2006%2Ferrors%5C%22%26gt%3BProxy%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Eweb%20request%20failed.%20%2C%20inner%20exception%3A%20An%20error%20occurred%20when%20verifying%20security%20for%20the%20message.%20LID%3A%2059916%3C%2FEXCEPTIONMESSAGE%3E%5Cr%5Cn%3C%2FXMLNODEARRAY%3E%22%2C%22ResponseClass%22%3A%22Error%22%7D%2C%22CalendarView%22%3A%7B%22MergedFreeBusy%22%3Anull%2C%22Items%22%3Anull%2C%22WorkingHours%22%3Anull%2C%22FreeBusyViewType%22%3A%22None%22%7D%7D%5D%2C%22ResponseCode%22%3A%22NoError%22%2C%22ResponseClass%22%3A%22Success%22%7D%7D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20also%20ran%26nbsp%3B%3CSPAN%3EGet-IntraOrganizationConnector%26nbsp%3B%20on%20both%20on-prem%20and%20exch%20online%20and%20both%20do%20not%20show%20any%20output%3F%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ethanks!%3C%2FP%3E%3CP%3EEric%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1764858%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1764858%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Eric%2C%20as%20mentioned%20in%20the%20first%20blog%20comment%2C%20make%20sure%20we%20are%20looking%20at%20the%20right%20Organization%20Relationship%20in%20Exchange%20Online%20(Office%20365%20%26gt%3B%20On-Premises%20)%20and%20that%20is%20configured%20properly.%20If%20indeed%20the%20request%20reaches%20on-premises%20servers%20and%20not%20EXO%20servers%2C%26nbsp%3B%20then%20please%20recycle%20EWS%20App%20Pool%20on-premises%20%2FIISreset%20like%20I%20mentioned%20in%20the%20PDF%20with%20errors.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1774886%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1774886%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F830463%22%20target%3D%22_blank%22%3E%40ADynes%3C%2FA%3E%26nbsp%3B%2C%20provide%20me%20with%20the%20case%20number%20(you%20can%20also%20send%20me%20a%20private%20message)%20so%20that%20I%20can%20check%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1774856%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1774856%22%20slang%3D%22en-US%22%3E%3CP%3E(deleted)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1795580%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1795580%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F395212%22%20target%3D%22_blank%22%3E%40Mirela_Buru%3C%2FA%3E%3C%2FSPAN%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYour%20help%20was%20great%20and%20helped%20me%20figure%20out%20our%20main%20problem.%20We%20used%20a%20service%20to%20help%20us%20with%20setting%20up%20hybrid%2C%20they%20had%20us%20change%20our%20on-prem%20autodiscover%20dns%20record%20to%20point%20to%20outlook.com%20before%20we%20ran%20the%20wizard.%20I%20changed%20it%20back%20to%20our%20on-prem%20ip%20address%20after%20the%20wizard%20was%20run%20initially.%26nbsp%3B%20After%20I%20ran%20the%20wizard%20again%20(with%20the%20correct%20autodiscover%20record)%26nbsp%3B%20we%20are%20now%20seeing%20on-prem%20free%2Fbusy%20for%20our%20exchange%202013%20users.%20We%20have%20exchange%202010%20and%202013%20on-prem%20and%20unfortunately%20we%20are%20unable%20to%20see%20the%20exchange%202010%20users%20free%2Fbusy.%20The%20free%2Fbusy%20troubleshooter%20comes%20up%20with%20the%20error%20message%20below%20when%20I%20point%20to%20an%20exchange%202010%20mailbox%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%20where%20I%20should%20look%20next%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22ms-Stack%20css-95%22%3E%3CDIV%20class%3D%22ms-Stack%20css-217%22%3E%3CDIV%20class%3D%22ms-Stack%20css-241%22%3E%3CDIV%20class%3D%22ms-Stack%20css-247%22%3E%3CDIV%20class%3D%22ms-Stack%20css-263%22%3E%3CDIV%20class%3D%22ms-Stack%20css-60%22%3E%3CDIV%20class%3D%22ms-Stack%20css-265%22%3E%3CSPAN%20class%3D%22css-194%22%3EPerforming%20Free%2FBusy%20Test.%20See%20guidance%20about%20the%20Hybrid%20Configuration%20Wizard%20at%20%3CA%20href%3D%22http%3A%2F%2Faka.ms%2FHCW%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2FHCW%3C%2FA%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22css-194%22%3EFree%2FBusy%20test%20failed%3C%2FSPAN%3E%3CDIV%20class%3D%22ms-Stack%20root-267%22%3E%3CDIV%20class%3D%22ms-Stack%20css-120%22%3E%3CSPAN%20class%3D%22ms-Button-flexContainer%20flexContainer-50%22%3E%3CI%3E%EE%9C%8E%3C%2FI%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22css-194%22%3ETest%20Steps%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22ms-Stack%20root-276%22%3E%3CDIV%20class%3D%22ms-Stack%20css-60%22%3E%3CI%3E%EE%B1%A1%3C%2FI%3E%3CDIV%20class%3D%22ms-Stack%20css-265%22%3E%3CSPAN%20class%3D%22css-194%22%3EDetermining%20where%20the%20source%20mailbox%20is%20hosted.%3C%2FSPAN%3E%3CSPAN%20class%3D%22css-194%22%3EThe%20check%20to%20determine%20if%20the%20source%20mailbox%20is%20hosted%20in%20Office%20365%20completed%20successfully.%3C%2FSPAN%3E%3CDIV%20class%3D%22ms-Stack%20root-267%22%3E%3CDIV%20class%3D%22ms-Stack%20css-120%22%3E%3CSPAN%20class%3D%22ms-Button-flexContainer%20flexContainer-50%22%3E%3CI%3E%EE%9C%8D%3C%2FI%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22css-194%22%3EAdditional%20Details%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22ms-Stack%20css-60%22%3E%3CI%3E%EE%B1%A1%3C%2FI%3E%3CDIV%20class%3D%22ms-Stack%20css-265%22%3E%3CSPAN%20class%3D%22css-194%22%3EDetermining%20where%20the%20target%20mailbox%20is%20hosted.%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%20class%3D%22css-194%22%3EThe%20check%20to%20determine%20if%20the%20target%20mailbox%20is%20hosted%20in%20Office%20365%20completed%20successfully.%3C%2FSPAN%3E%3CDIV%20class%3D%22ms-Stack%20root-267%22%3E%3CDIV%20class%3D%22ms-Stack%20css-120%22%3E%3CSPAN%20class%3D%22ms-Button-flexContainer%20flexContainer-50%22%3E%3CI%3E%EE%9C%8D%3C%2FI%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22css-194%22%3EAdditional%20Details%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22ms-Stack%20css-60%22%3E%3CI%3E%EF%9C%B6%3C%2FI%3E%3CDIV%20class%3D%22ms-Stack%20css-265%22%3E%3CSPAN%20class%3D%22css-194%22%3EThe%20Microsoft%20Connectivity%20Analyzer%20is%20attempting%20to%20test%20Autodiscover%20for%20xx%20.%3C%2FSPAN%3E%3CSPAN%20class%3D%22css-194%22%3EAutodiscover%20was%20tested%20successfully.%3C%2FSPAN%3E%3CDIV%20class%3D%22ms-Stack%20root-267%22%3E%3CDIV%20class%3D%22ms-Stack%20css-120%22%3E%3CSPAN%20class%3D%22ms-Button-flexContainer%20flexContainer-50%22%3E%3CI%3E%EE%9C%8D%3C%2FI%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22css-194%22%3ETest%20Steps%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22ms-Stack%20css-60%22%3E%3CI%3E%EE%B1%A1%3C%2FI%3E%3CDIV%20class%3D%22ms-Stack%20css-265%22%3E%3CSPAN%20class%3D%22css-194%22%3EVerifying%20connectivity%20to%20the%20specified%20endpoint%3C%2FSPAN%3E%3CSPAN%20class%3D%22css-194%22%3ESuccessfully%20verified%20pass-through%20connectivity.%3C%2FSPAN%3E%3CDIV%20class%3D%22ms-Stack%20root-267%22%3E%3CDIV%20class%3D%22ms-Stack%20css-120%22%3E%3CSPAN%20class%3D%22ms-Button-flexContainer%20flexContainer-50%22%3E%3CI%3E%EE%9C%8D%3C%2FI%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22css-194%22%3EAdditional%20Details%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22ms-Stack%20css-60%22%3E%3CI%3E%EE%B1%A1%3C%2FI%3E%3CDIV%20class%3D%22ms-Stack%20css-265%22%3E%3CSPAN%20class%3D%22css-194%22%3EVerifying%20connectivity%20to%20the%20specified%20endpoint%3C%2FSPAN%3E%3CSPAN%20class%3D%22css-194%22%3ESuccessfully%20verified%20pass-through%20connectivity.%3C%2FSPAN%3E%3CDIV%20class%3D%22ms-Stack%20root-267%22%3E%3CDIV%20class%3D%22ms-Stack%20css-120%22%3E%3CSPAN%20class%3D%22ms-Button-flexContainer%20flexContainer-50%22%3E%3CI%3E%EE%9C%8D%3C%2FI%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22css-194%22%3EAdditional%20Details%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22ms-Stack%20css-60%22%3E%3CI%3E%EE%AE%90%3C%2FI%3E%3CDIV%20class%3D%22ms-Stack%20css-265%22%3E%3CSPAN%20class%3D%22css-194%22%3EPerforming%20Free%2FBusy%20Lookup%3C%2FSPAN%3E%3CSPAN%20class%3D%22css-194%22%3EFree%2FBusy%20Lookup%20failed.%3C%2FSPAN%3E%3CDIV%20class%3D%22ms-Stack%20root-267%22%3E%3CDIV%20class%3D%22ms-Stack%20css-120%22%3E%3CSPAN%20class%3D%22ms-Button-flexContainer%20flexContainer-50%22%3E%3CI%3E%EE%9C%8E%3C%2FI%3E%3C%2FSPAN%3E%3CSPAN%20class%3D%22css-194%22%3EAdditional%20Details%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22ms-Stack%20root-276%22%3E%3CSPAN%20class%3D%22css-194%22%3EFree%2FBusy%20Lookup%20failed%20with%20exception%3A%20Proxy%20web%20request%20failed.%20%2C%20inner%20exception%3A%20System.Web.Services.Protocols.SoapHeaderException%3A%20An%20error%20occurred%20when%20verifying%20security%20for%20the%20message.%20at%20System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage%20message%2C%20WebResponse%20response%2C%20Stream%20responseStream%2C%20Boolean%20asyncCall)%20at%20System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult%20asyncResult)%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult%20asyncResult)%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest%20proxyWebRequest%2C%20QueryList%20queryList%2C%20IService%20service%2C%20IAsyncResult%20asyncResult)%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult%20asyncResult)%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1795671%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1795671%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%2F822422%22%20target%3D%22_blank%22%3E%40epeterson79%3C%2FA%3E%26nbsp%3B%2C%20for%20the%20security%20of%20the%20message%20error%2C%20just%20follow%20the%20previous%20suggestions%3A%26nbsp%3B%3CBR%20%2F%3Erecycle%20EWS%20App%20Pool%20on%20all%20Exchange%20servers%20%2F%20run%20IISreset%26nbsp%3B%20like%20I%20mentioned%20in%20the%20PDF%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F01%2FFB_Errors.FixesV6.pdf%22%20target%3D%22_blank%22%3EFB_Errors.FixesV6%3C%2FA%3E%20(error%20%233)%20%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F2752387%2Fusers-from-a-federated-organization-cannot-see-the-free-busy-informati%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F2752387%2Fusers-from-a-federated-organization-cannot-see-the-free-busy-informati%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1821570%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1821570%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F395212%22%20target%3D%22_blank%22%3E%40Mirela_Buru%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EFirst%20of%20all%2C%20Thanks%20a%20million%2C%20I've%20solved%20lots%20of%20Hybrid%20Free%20%2F%20Busy%20issues%20by%20taking%20help%20from%20this%20blog.%20However%2C%20currently%20I'm%20having%20an%20issue%2C%20I've%20spent%20a%20few%20hours%20on%20it%20but%20haven't%20been%20able%20to%20solve%20it.%20Our%20On-Premise%20Users%20can%20not%20see%20Cloud%20Users%20free%20%2F%20busy.%3C%2FP%3E%3CP%3E-%20First%20I%20found%20Federation%20Certificate%20was%20expired%2C%20I%20renewed%20it%20and%20recreated%20federation%2C%20Test-Federation%20is%20now%20all%20good.%3C%2FP%3E%3CP%3E-%20After%20that%20I%20found%20OAuth%20Certificate%20was%20expired%2C%20I%20was%20able%20to%20renew%20it%20and%20publish%20to%20all%20Exchange%20Servers%2C%20Test-OAuthConnectivity%20is%20all%20good.%3C%2FP%3E%3CP%3E-%20Test-OrganizationRelationship%20is%20all%20good.%3C%2FP%3E%3CP%3E-%20IntraOrganizationConnector%20is%20enabled.%3C%2FP%3E%3CP%3E-%20I%20checked%20your%20FB%20errors%20table%20but%20I%20couldn't%20found%20the%20error%20I'm%20facing.%3C%2FP%3E%3CP%3E-%20I've%20done%20tonnes%20of%20changes%20at%20On%20Premise%20OrganizationRelationship%20populating%20TargetSharingEPR%2C%20Testing%20with%20%2F%20without%20WSSecurity%2C%20Disabling%20IOC%20but%20no%20luck.%20I'm%20stuck%20on%20below%20error.%3C%2FP%3E%3CP%3E-%20In%20OWA%20Network%20Response%20for%20Get-Useravailablity%20as%20well%20as%20at%20MS%20RCA%20I%20get%20error%2C%20I%20suspect%20this%20is%20still%20related%20to%20OAuth%20between%20EXO%20and%20EX-On-Premise%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EFree%2FBusy%20Lookup%20failed%20with%20exception%3A%20Autodiscover%20failed%20for%20email%20address%20USER%40INITIALDOMAIN.mail.onmicrosoft.com%20with%20error%20System.Net.WebException%3A%20Unable%20to%20connect%20to%20the%20remote%20server%20---%26gt%3B%20System.Net.Sockets.SocketException%3A%20A%20connection%20attempt%20failed%20because%20the%20connected%20party%20did%20not%20properly%20respond%20after%20a%20period%20of%20time%2C%20or%20established%20connection%20failed%20because%20connected%20host%20has%20failed%20to%20respond%2052.98.32.2%3A443%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1822776%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1822776%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F846972%22%20target%3D%22_blank%22%3E%40Mashal_Khan%3C%2FA%3E%26nbsp%3B%2C%20this%20is%20a%20network%20issue%20between%20Exchange%20On-Premises%20Servers%20and%20Exchange%20Online%20Server%20IP%20Addresses%20(%3CSTRONG%3E52.98.32.2%20is%20EXO%20server%20%3C%2FSTRONG%3Ewhere%20probably%20your%20target%20cloud%20user%20USER%40INITIALDOMAIN.mail.onmicrosoft.comis%20hosted%3CSTRONG%3E)%3C%2FSTRONG%3E.%3C%2FP%3E%0A%3CP%3EHow%20are%20your%20Exchange%20On-premises%20servers%20going%20out%20on%20the%20internet%3F%20Proxy%20or%20Firewall%3F%20You%20seem%20to%20be%20blocking%20outbound%20connections%20to%26nbsp%3B%3CSTRONG%3E52.98.32.2.%3C%2FSTRONG%3E%20If%20using%20proxy%2C%20make%20sure%20this%20is%20set%20on%20the%20Exchange%20Servers%2C%20you%20can%20do%20Get-ExchangeServer%20%7CFL%20identity%2C%20internetwebproxy%20to%20check%20if%20there%20and%20Set-ExchangeServer%20to%20set%20one.%20Make%20sure%20you%20allow%20all%20your%20Exchange%20Servers%20to%20connect%20to%20all%20EXO%20IP%20addresses%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fenterprise%2Furls-and-ip-address-ranges%3Fview%3Do365-worldwide%23exchange-online%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fmicrosoft-365%2Fenterprise%2Furls-and-ip-address-ranges%3Fview%3Do365-worldwide%23exchange-online%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20should%20follow%20Suggestions%20from%20Error%2022%2C%20points%202%20and%203%20and%20make%20sure%20you%20can%20access%20from%20Exchange%20System%20Account%20(on%20each%20Exchange%20Server%20CAS%2FMBX)%20the%20following%20URLs%3A%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fautodiscover-s.outlook.com%2Fautodiscover%2Fautodiscover.svc%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fautodiscover-s.outlook.com%2Fautodiscover%2Fautodiscover.svc%3C%2FA%3E%26nbsp%3B(%20EXO%20Autodiscover%20Service)%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2F52.98.32.2%2Fautodiscover%2Fautodiscover.svc%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2F52.98.32.2%2Fautodiscover%2Fautodiscover.svc%3C%2FA%3E%26nbsp%3B%20(continue%20to%20certificate%20error%20because%20we%20put%20ip)%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22http%3A%2F%2Fautodiscover.miryMS.mail.onmicrosoft.com%2Fautodiscover%2Fautodiscover.svc%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttp%3A%2F%2Fautodiscover.%3CYOUR-INITIAL-DOMAIN.MAIL.ONMICROSOFT.COM%3E%26nbsp%3B%20(this%20should%20redirect%20to%20https%20EXO%20Autodiscover%20Service)%3C%2FYOUR-INITIAL-DOMAIN.MAIL.ONMICROSOFT.COM%3E%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Foutlook.office365.com%2Fews%2Fexchange.asmx%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Foutlook.office365.com%2Fews%2Fexchange.asmx%3C%2FA%3E%26nbsp%3B(%20EXO%20EWS%20Service%2C%20this%20can%20also%20be%20set%20on%20the%20TargetSharingEpr%20on%20the%20on-premises%20Organization%20Relationship%20when%20On-Premises%20IOC%20is%20disabled).%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1823139%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1823139%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F395212%22%20target%3D%22_blank%22%3E%40Mirela_Buru%3C%2FA%3E%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EThank%20You%2C%20Sorry%20I%20forgot%20to%20mention%2C%20I%20checked%20on%20all%20Exchange%20Servers%2C%20they're%20doing%20out%20to%20the%20Internet%20directly%20i.e.%20internetwebproxy%20is%20empty%20on%20all.%20We%20don't%20have%20internet%20access%20on%20any%20Exchange%20Server%20but%20Hybrid%20Server%20can%20make%20outbound%20requests%20to%20anywhere%20on%20port%2080%2C%20443.%20I%20checked%20all%20URLs%20are%20accessible%20on%20Hybrid%20Server.%20Free%20%2F%20Busy%20was%20fine%20previously%20with%20the%20same%20network%20access.%20Do%20I%20these%20URLs%20need%20to%20be%20accessible%20on%20all%20Exchange%20Servers%20or%20just%20Hybrid%20Server%20is%20enough%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20other%20thing%20you%20advised%20is%20that%20if%20I%20disable%20On%20Premise%20IOC%20and%20populate%20OrganizationRelationship%20with%20%3CA%20href%3D%22https%3A%2F%2Foutlook.office365.com%2Fews%2Fexchange.asmx%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Foutlook.office365.com%2Fews%2Fexchange.asmx%3C%2FA%3E%20Free%20%2F%20Busy%20look%20up%20will%20not%20use%20Autodiscover%20but%20it%20will%20use%20EWS%20and%20that%20may%20resolve%20my%20issue%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20I%20will%20have%20my%20network%20team%20allow%20outbound%20connections%20to%20anywhere%20on%20port%2080%2C%20443%20for%20a%20small%20duration%20to%20test%20and%20let%20you%20know%20if%20that%20worked.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1823339%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1823339%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3E1.%26nbsp%3B%26nbsp%3BDo%20I%20these%20URLs%20need%20to%20be%20accessible%20on%20all%20Exchange%20Servers%20or%20just%20Hybrid%20Server%20is%20enough%20%3F%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26gt%3B%26gt%3B%20ALL%20the%20Exchange%202010%20MBX%20%26amp%3B%20CAS%20or%202013%20MBX%20(backend)%20or%202016%20would%20need%20outbound%20Internet%20access%26nbsp%3Bto%20all%20these%3A%3CBR%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fenterprise%2Furls-and-ip-address-ranges%23exchange-online%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EOffice%20365%20URLs%20and%20IP%20address%20ranges%20%E2%80%93%20Exchange%20Online%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fenterprise%2Furls-and-ip-address-ranges%23microsoft-365-common-and-office-online%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EOffice%20365%20URLs%20and%20IP%20address%20ranges%20%E2%80%93%20Common%3C%2FA%3E%3C%2FLI%3E%0A%3CLI%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Foffice365%2Fenterprise%2Fadditional-office365-ip-addresses-and-urls%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EAdditional%20endpoints%3C%2FA%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EReference%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fprevious-versions%2Foffice%2Fexchange-server-2010%2Fdd638083(v%3Dexchg.141)%3Fredirectedfrom%3DMSDN%23firewall-considerations-for-federated-delegation%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fprevious-versions%2Foffice%2Fexchange-server-2010%2Fdd638083(v%3Dexchg.141)%3Fredirectedfrom%3DMSDN%23firewall-considerations-for-federated-delegation%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E2.%20The%20other%20thing%20you%20advised%20is%20that%20if%20I%20disable%20On%20Premise%20IOC%20and%20populate%20Organization%20Relationship%20with%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Foutlook.office365.com%2Fews%2Fexchange.asmx%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Foutlook.office365.com%2Fews%2Fexchange.asmx%3C%2FA%3E%3CSPAN%3E%26nbsp%3BFree%20%2F%20Busy%20look%20up%20will%20not%20use%20Autodiscover%20but%20it%20will%20use%20EWS%20and%20that%20may%20resolve%20my%20issue%20%3F%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26gt%3B%26gt%3BYes%2C%20correct%2C%20you%20can%20try%20to%20bypass%20AutoD%20query%20and%20see%20if%20it%20works%20by%20going%20directly%20to%20EWS%20but%20this%20can%20be%20any%20on-premises%20Exchange%20Server%20in%20your%20organization%2C%20so%20internet%20access%20is%20needed%20from%20each.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1823598%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1823598%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F395212%22%20target%3D%22_blank%22%3E%40Mirela_Buru%3C%2FA%3EThank%20you%20for%20great%20help%2C%20I%20was%20able%20to%20create%20a%20User%20on%20Hybrid%20Server%2C%20that%20User%20is%20able%20to%20see%20Cloud%20Users%20Free%20%2F%20Busy%20as%20Hybrid%20Server%20has%20required%20outbound%20access%20to%20anywhere%20on%20port%2080%2C443%2C%20We%20need%20to%20grant%20all%20Exchange%20Servers%20outbound%20access%20to%20the%20Office%20365%20IPs%2F%20Urls%20to%20solve%20this%2C%20THANKS%20A%20BILLION%20!!!!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1832659%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1832659%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20you%20confirm%20in%20section%2022%20%22%3CA%20href%3D%22https%3A%2F%2Flogin.microsoftonline.com%2FextSTS.srf%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Flogin.microsoftonline.com%2FextSTS.srf%3C%2FA%3E%20%5B%26lt%3B--%20You%20should%20be%20prompted%20to%3CBR%20%2F%3Edownload%20the%20file.%5D%22%20-%20that%20the%20file%20should%20be%20downloadable%3F%20(I've%20tried%20from%20a%20variety%20of%20different%20machines%20but%20get%20the%20same%20experience)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20i%20run%20the%20psexec%20test%20I%20get%20a%20webpage%20that%20says%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22Sorry%2C%20but%20we%E2%80%99re%20having%20trouble%20with%20signing%20you%20in.%3C%2FP%3E%3CP%3EAADSTS900561%3A%20The%20endpoint%20only%20accepts%20POST%20requests.%20Received%20a%20GET%20request.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20seeing%20errors%20in%20outlook%20(onprem)%20to%20365%20mailbox%20f%2Fb%20lookups%20that%20state%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22%3CMESSAGETEXT%3EFailed%20to%20communicate%20with%20%3CA%20href%3D%22https%3A%2F%2Flogin.microsoftonline.com%2FextSTS.srf.%26quot%3B%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Flogin.microsoftonline.com%2FextSTS.srf.%22%3C%2FA%3E%3C%2FMESSAGETEXT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eso%20it%20seems%20a%20very%20similar%20error%20but%20i'm%20struggling%20to%20troubleshoot%20further.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20any%20pointers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1832729%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1832729%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%2F216834%22%20target%3D%22_blank%22%3E%40David%20Hood%3C%2FA%3E%26nbsp%3B%2C%20you%20are%20correct%2C%20the%20PDF%20is%20outdated.%20I%20will%20try%20to%20update%20it%20soon.%3C%2FP%3E%0A%3CP%3EThe%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fnam06.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Flogin.microsoftonline.com%252FextSTS.srf%26amp%3Bdata%3D02%257C01%257Cmirela.buruiana%2540microsoft.com%257C3cd98ace628143ec03ec08d824d3d27f%257C72f988bf86f141af91ab2d7cd011db47%257C1%257C0%257C637299839468119999%26amp%3Bsdata%3DVdKsoyp5CJmQCia2YtWxFk%252FxrNDqr6cXD9AU57uAFew%253D%26amp%3Breserved%3D0%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Flogin.microsoftonline.com%2FextSTS.srf%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%20%26nbsp%3Bshould%20give%20%5B%26lt%3B--%20You%20should%20see%20%E2%80%9CSorry%2C%20but%20we%E2%80%99re%20having%20trouble%20signing%20you%20in%E2%80%9D.%5D%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20MFG%20URLs%20issues%2C%20you%20can%20also%20check%20my%20other%20blog%20on%20Federation%20Trust%2C%20especially%20error%203%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fhow-to-address-federation-trust-issues-in-hybrid-configuration%2Fba-p%2F1144285%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fhow-to-address-federation-trust-issues-in-hybrid-configuration%2Fba-p%2F1144285%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1863992%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1863992%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20to%20find%20out%20a%20problem%20with%20F%2FB%20-%26nbsp%3B%3CSPAN%3EExchange%202016%20on-premises%20users%26nbsp%3B%20are%20not%20able%20to%20view%20the%20free%2Fbusy%20information%20of%20the%20office%20365%20users.%20They%20have%20in%20Outlook%202016%20(could%20not%20be%20updated)%2C%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20check%20OWA%20F12%20and%20error%20is%3A%26nbsp%3B%3CSTRONG%3ESystem.Net.WebException%3A%20The%20request%20failed%20with%20HTTP%20status%20401%3A%20Unauthorized.%3C%2FSTRONG%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20was%20able%20to%20find%20almost%20same%20error%20in%20the%20Microsoft%20free%2Fbusy%20troubleshooting%20guide%20(Index%2026)%20attached%20below%20as%20well%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fanishjohnes.files.wordpress.com%2F2019%2F10%2Ffb_errors.fixesv6.pdf%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fanishjohnes.files.wordpress.com%2F2019%2F10%2Ffb_errors.fixesv6.pdf%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Ebut%20when%20i%20test%26nbsp%3BTest-OAuthConnectivity%20-Service%20EWS%20-TargetUri%20%3CA%20href%3D%22https%3A%2F%2Foutlook.office365.com%2Fews%2Fexchange.asmx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Foutlook.office365.com%2Fews%2Fexchange.asmx%3C%2FA%3E%20-Mailbox%20OnPremises%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FSPAN%3E%3CSPAN%3Emy%20exception%20are%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3ESystem.Net.WebException%3A%20The%20request%20was%20aborted%3A%20The%20request%20was%20canceled.%20---%26gt%3B%20Microsoft.Exchange.Security.OAuth.OAuthTokenRequestFailedException%3A%20The%20trusted%20issuers%20contained%20the%20followi%3CBR%20%2F%3Eng%20entries%20'00000001-0000-0000-c000-000000000000%40*'.%20None%20of%20them%20are%20configured%20locally.%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20I%20check%20following%20guide%20(index%2026)%26nbsp%3Bcheck%20certificate%20mismatch%20but%20i%20have%20the%20same%20on%20perm%20and%20Azure.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20found%20solution%2C%20I%20explaind%20what%20I%20did%20on%20the%20forum%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2Fa0bb1d0a-6639-4fdf-92e1-7fa350e47057%2Fexchange-2016-onpremises-users-are-not-able-to-view-calendar-information-of-the-office-365-users%3Fforum%3Dexchangesvrdevelopment%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2Fa0bb1d0a-6639-4fdf-92e1-7fa350e47057%2Fexchange-2016-onpremises-users-are-not-able-to-view-calendar-information-of-the-office-365-users%3Fforum%3Dexchangesvrdevelopment%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3ERafal%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1866740%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1866740%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20your%20feedback%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F850221%22%20target%3D%22_blank%22%3E%40rchmielarski%3C%2FA%3E%26nbsp%3B%2C%20for%20such%20error%20we%20would%20normally%20need%20more%20outputs%20on%20how%20the%20OAuth%20is%20configured%20and%20it's%20interesting%20that%20apparently%20IISreset%20did%20the%20trick%20here.%20Would%20have%20been%20good%20to%20know%20your%20CU%20for%20Exchange%202016%20and%20if%20by%20any%20chance%20Get-AuthServer%26nbsp%3B%20had%20previously%20or%20maybe%20it%20still%20has%20the%26nbsp%3B%20-DomainName%20populated%20with%20an%20SMTP%20domain%20and%20if%20the%20user%20used%20in%20Test-OauthConnectivity%20had%20that%20domain%20in%20primary%20SMTP%20address.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1880856%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1880856%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22lia-note-subject%22%3EIssue%20exchange%202013%20cannot%20see%20free%20busy%20information%202007%3C%2FDIV%3E%3CDIV%20class%3D%22lia-note-description%22%3E%3CDIV%20class%3D%22lia-note-body%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F395212%22%20target%3D%22_blank%22%3E%40Mirela_Buru%3C%2FA%3E%2C%26nbsp%3BI%20have%20enviroment%20with%20exchange%202007%20and%20exchange%202013.%20I%20Have%20a%20event%20id%20in%20my%20exchange%202013%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EProcess%2015040%3A%20ProxyWebRequest%20CrossSite%20from%20S-1-5-21-190996285-3174742192-1521001504-11052%20to%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fmail.ceee.com.br%2FEWS%2FExchange.asmx%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmail.teste.com.br%3A443%2FEWS%2FExchange.asmx%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Efailed.%20Caller%20SIDs%3A%20NetworkCredentials.%20The%20exception%20returned%20is%20Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException%3A%20Proxy%20web%20request%20failed.%20---%26gt%3B%20System.Net.WebException%3A%20The%20request%20failed%20with%20HTTP%20status%20401%3A%20Unauthorized.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20there%20is%20a%20problem%20%22exchange%202013%20cannot%20see%20free%20busy%20information%202007%22%20.%20The%26nbsp%3Bo%20rest%20all%20work%20fine%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20i%20don't%20have%20in%20my%20enviroment%20exchange%20online.%3C%2FP%3E%3CP%3EThis%20solutions%20cab%20se%20aply%20in%20my%20enviroment%3F%20(%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F01%2FFB_Errors.FixesV6.pdf%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F01%2FFB_Errors.FixesV6.pdf%3C%2FA%3E%26nbsp%3B%20index%2010%3A%20Proxy%20web%20request%20failed.%2Cinner%20exception%3A%20The%3CBR%20%2F%3Erequest%20failed%20with%20HTTP%20status%20401%3A%3CBR%20%2F%3EUnauthorized.)%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20your%20help%3C%2FP%3E%3CP%3Ebest%20regards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAgostinho%20Martini%3C%2FP%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1880891%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1880891%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22lia-note-subject%22%3EIssue%20exchange%202013%20cannot%20see%20free%20busy%20information%202007%3C%2FDIV%3E%3CDIV%20class%3D%22lia-note-description%22%3E%3CDIV%20class%3D%22lia-note-body%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F395212%22%20target%3D%22_blank%22%3E%40Mirela_Buru%3C%2FA%3E%2C%26nbsp%3BI%20have%20enviroment%20with%20exchange%202007%20and%20exchange%202013.%20I%20Have%20a%20event%20id%20in%20my%20exchange%202013%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EProcess%2015040%3A%20ProxyWebRequest%20CrossSite%20from%20S-1-5-21-190996285-3174742192-1521001504-11052%20to%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fmail.ceee.com.br%2FEWS%2FExchange.asmx%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmail.teste.com.br%3A443%2FEWS%2FExchange.asmx%3C%2FA%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3Efailed.%20Caller%20SIDs%3A%20NetworkCredentials.%20The%20exception%20returned%20is%20Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException%3A%20Proxy%20web%20request%20failed.%20---%26gt%3B%20System.Net.WebException%3A%20The%20request%20failed%20with%20HTTP%20status%20401%3A%20Unauthorized.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20there%20is%20a%20problem%20%22exchange%202013%20cannot%20see%20free%20busy%20information%202007%22%20.%20The%26nbsp%3Bo%20rest%20all%20work%20fine%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20i%20don't%20have%20in%20my%20enviroment%20exchange%20online.%3C%2FP%3E%3CP%3EThis%20solutions%20cab%20se%20aply%20in%20my%20enviroment%3F%20%26nbsp%3B%3C%2FP%3E%3CP%3Eindex%2010%3A%20Proxy%20web%20request%20failed.%2Cinner%20exception%3A%20The%3CBR%20%2F%3Erequest%20failed%20with%20HTTP%20status%20401%3A%3CBR%20%2F%3EUnauthorized.)%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20for%20your%20help%3C%2FP%3E%3CP%3Ebest%20regards%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAgostinho%20Martini%3C%2FP%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1881706%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1881706%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F866853%22%20target%3D%22_blank%22%3E%40Agostinho_Martini%3C%2FA%3E%26nbsp%3B%2C%20the%20solutions%20from%20this%20PDF%20don't%20apply%20to%20this%20scenario.%3C%2FP%3E%0A%3CP%3EI%20would%20suggest%20to%20check%20HTTPProxy%20EWS%20logs%20on%20the%20Ex2013%20and%20IIS%20logs%20on%20Ex2007%2C%20eventually%20FREB%20logs%20for%20401%20sub%20code.%3C%2FP%3E%0A%3CP%3ECheck%20Authentication%20Methods%20in%20EWS%20on%20Ex2007%20server.%20Make%20sure%20Default%20user%20doesn't%20have%20NONE%20in%20the%20Get-MailboxFolderPermission%20TargetUser%3A%5CCalendar.%26nbsp%3B%20Exchange%202007%20users%20can%20see%20Free%2FBusy%20between%20them%20and%20set%20OOF%20replies%20successfully%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1881861%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1881861%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F395212%22%20target%3D%22_blank%22%3E%40Mirela_Buru%3C%2FA%3E%26nbsp%3B%26nbsp%3BThank%20you%20very%20much!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUsers%20in%20exchange%202007%20can%20see%20free%20busy%20information%20amoung%20user%20in%20exchange%202007.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUser%20in%20exchange%202007%20can%20see%20free%20busy%20information%20users%20exchange%202013.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOnly%20users%20exchange%202013%20cant%20seee%20frre%20busy%20information%20user%20exchange%202007.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EEWS%20autentication%20exchange%202013%3A%20Default%20and%20Back%20End%20site%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%5BPS%5D%20C%3A%5CWindows%5Csystem32%26gt%3BGet-WebServicesVirtualDirectory%20-server%20smxpoa05%20%7C%20fl%20InternalUrl%2CExternalUrl%2CIdentity%2CName%2C*au%3CBR%20%2F%3Eth*%20%7C%20fl%3CBR%20%2F%3ECreating%20a%20new%20session%20for%20implicit%20remoting%20of%20%22Get-WebServicesVirtualDirectory%22%20command...%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EInternalUrl%20%3A%20%3CA%20href%3D%22https%3A%2F%2Fmail.teste1.com.br%2Fews%2Fexchange.asmx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fmail.teste1.com.br%2Fews%2Fexchange.asmx%3C%2FA%3E%3CBR%20%2F%3EExternalUrl%20%3A%20%3CA%20href%3D%22https%3A%2F%2Fmail.teste1.com.br%2Fews%2Fexchange.asmx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fmail.teste1.com.br%2Fews%2Fexchange.asmx%3C%2FA%3E%3CBR%20%2F%3EIdentity%20%3A%20servidor1%5CEWS%20(Default%20Web%20Site)%3CBR%20%2F%3EName%20%3A%20EWS%20(Default%20Web%20Site)%3CBR%20%2F%3ECertificateAuthentication%20%3A%3CBR%20%2F%3EInternalAuthenticationMethods%20%3A%20%7BNtlm%2C%20WindowsIntegrated%2C%20WSSecurity%2C%20OAuth%7D%3CBR%20%2F%3EExternalAuthenticationMethods%20%3A%20%7BNtlm%2C%20WindowsIntegrated%2C%20WSSecurity%2C%20OAuth%7D%3CBR%20%2F%3ELiveIdNegotiateAuthentication%20%3A%3CBR%20%2F%3EWSSecurityAuthentication%20%3A%20True%3CBR%20%2F%3ELiveIdBasicAuthentication%20%3A%20False%3CBR%20%2F%3EBasicAuthentication%20%3A%20False%3CBR%20%2F%3EDigestAuthentication%20%3A%20False%3CBR%20%2F%3EWindowsAuthentication%20%3A%20True%3CBR%20%2F%3EOAuthAuthentication%20%3A%20True%3CBR%20%2F%3EAdfsAuthentication%20%3A%20False%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%5BPS%5D%20C%3A%5CWindows%5Csystem32%26gt%3BGet-WebServicesVirtualDirectory%20-ShowMailboxVirtualDirectories%20-Server%20smxpoa05%20%7C%20fl%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ERunspaceId%20%3A%20ca5a7de9-75a2-4fdb-97f2-284da2ac5af2%3CBR%20%2F%3ECertificateAuthentication%20%3A%3CBR%20%2F%3EInternalNLBBypassUrl%20%3A%20%3CA%20href%3D%22https%3A%2F%2Fmail.teste1.local%3A444%2Fews%2Fexchange.asmx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fmail.teste1.local%3A444%2Fews%2Fexchange.asmx%3C%2FA%3E%3CBR%20%2F%3EGzipLevel%20%3A%20High%3CBR%20%2F%3EMRSProxyEnabled%20%3A%20False%3CBR%20%2F%3EName%20%3A%20EWS%20(Exchange%20Back%20End)%3CBR%20%2F%3EInternalAuthenticationMethods%20%3A%20%7BNtlm%2C%20WindowsIntegrated%2C%20WSSecurity%7D%3CBR%20%2F%3EExternalAuthenticationMethods%20%3A%20%7BNtlm%2C%20WindowsIntegrated%2C%20WSSecurity%7D%3CBR%20%2F%3ELiveIdNegotiateAuthentication%20%3A%3CBR%20%2F%3EWSSecurityAuthentication%20%3A%20True%3CBR%20%2F%3ELiveIdBasicAuthentication%20%3A%20False%3CBR%20%2F%3EBasicAuthentication%20%3A%20False%3CBR%20%2F%3EDigestAuthentication%20%3A%20False%3CBR%20%2F%3EWindowsAuthentication%20%3A%20True%3CBR%20%2F%3EOAuthAuthentication%20%3A%20False%3CBR%20%2F%3EAdfsAuthentication%20%3A%20False%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CSTRONG%3EEWS%20autentication%20exchange%202007%3A%20Default%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EGet-WebServicesVirtualDirectory%3CBR%20%2F%3E-server%20smxpoa01%20%7C%20fl%20InternalUrl%2CExternalUrl%2CIdentity%2CName%2C*auth*%20%7C%20fl%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EInternalUrl%20%3A%20%3CA%20href%3D%22https%3A%2F%2Flegacy.teste1.com.br%2FEWS%2FExchange.asmx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Flegacy.teste1.com.br%2FEWS%2FExchange.asmx%3C%2FA%3E%3CBR%20%2F%3EExternalUrl%20%3A%20%3CA%20href%3D%22https%3A%2F%2Flegacy.teste1.com.br%2FEWS%2FExchange.asmx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Flegacy.teste1.com.br%2FEWS%2FExchange.asmx%3C%2FA%3E%3CBR%20%2F%3EIdentity%20%3A%20SMXPOA01%5CEWS%20(Default%20Web%20Site)%3CBR%20%2F%3EName%20%3A%20EWS%20(Default%20Web%20Site)%3CBR%20%2F%3EInternalAuthenticationMethods%20%3A%20%7BBasic%2C%20Ntlm%2C%20WindowsIntegrated%7D%3CBR%20%2F%3EExternalAuthenticationMethods%20%3A%20%7BBasic%2C%20Ntlm%2C%20WindowsIntegrated%7D%3CBR%20%2F%3EBasicAuthentication%20%3A%20True%3CBR%20%2F%3EDigestAuthentication%20%3A%20False%3CBR%20%2F%3EWindowsAuthentication%20%3A%20True%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EIn%20my%20logs%20iis%202007%20and%202013%20i%20found%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3ELog%20IIS%202007%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EC%3A%5CWINDOWS%5Csystem32%5CLogFiles%5CHTTPERR%3C%2FP%3E%3CP%3E2020-11-09%2019%3A42%3A28%2010.63.78.187%2053295%2010.63.70.231%20443%20HTTP%2F1.1%20RPC_IN_DATA%20%2Frpc%2Frpcproxy.dll%3FSMXPOA04.teste1.local%3A6001%20%3CSTRONG%3E400%201%20BadRequest%20DefaultAppPool%3C%2FSTRONG%3E%3CBR%20%2F%3E2020-11-09%2019%3A42%3A28%20170.233.237.115%2016855%2010.63.70.231%20443%20-%20-%20-%20-%20-%20Timer_ConnectionIdle%20-%3CBR%20%2F%3E2020-11-09%2019%3A42%3A32%2010.63.51.188%2059668%2010.63.70.231%20443%20-%20-%20-%20-%20-%20Timer_ConnectionIdle%20-%3CBR%20%2F%3E2020-11-09%2019%3A42%3A34%2010.63.78.185%2056960%2010.63.70.231%20443%20HTTP%2F1.1%20RPC_IN_DATA%20%2Frpc%2Frpcproxy.dll%3FSMXPOA03.teste1.local%3A6001%20%3CSTRONG%3E400%201%20BadRequest%20DefaultAppPool%3C%2FSTRONG%3E%3CBR%20%2F%3E2020-11-09%2019%3A42%3A34%2010.63.78.186%2022997%2010.63.70.231%20443%20HTTP%2F1.1%20RPC_IN_DATA%20%2Frpc%2Frpcproxy.dll%3FSMXPOA03%3A6001%20400%201%20%3CSTRONG%3EBadRequest%20DefaultAppPool%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CSTRONG%3ELog%20IIS%202013%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EC%3A%5CWindows%5CSystem32%5CLogFiles%5CHTTPERR%3C%2FP%3E%3CP%3E2020-11-09%2020%3A52%3A43%2010.63.78.185%2019986%2010.63.78.185%20444%20HTTP%2F1.1%20RPC_IN_DATA%20%2Frpc%2Frpcproxy.dll%3Fsmxpoa05.teste1.local%3A6001%20400%202%20Connection_Dropped%20MSExchangeRpcProxyAppPool%3CBR%20%2F%3E2020-11-09%2020%3A52%3A43%2010.63.75.43%2050880%2010.63.78.185%20443%20HTTP%2F1.1%20POST%20%2FMicrosoft-Server-ActiveSync%3FUser%3Dabiliolima%26amp%3BDeviceId%3D7QULD3E1SP1FR5ERG8Q5IHK68G%26amp%3BDeviceType%3DiPhone%26amp%3BCmd%3DPing%20-%201%20%3CSTRONG%3EConnection_Dropped%20MSExchangeSyncAppPool%3C%2FSTRONG%3E%3CBR%20%2F%3E2020-11-09%2020%3A52%3A43%2010.63.75.43%2050908%2010.63.78.185%20443%20HTTP%2F1.1%20POST%20%2FMicrosoft-Server-ActiveSync%3FeQAWBBAl2wZcQIhAIrRyDVtNyO9ABOj7SokLV2luZG93c01haWw%3D%20-%201%20Connection_Dropped%20MSExchangeSyncAppPool%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EFor%20me%20i%20am%20very%20confused%20because%20i%20found%20only%20event%20id%20exchange%202013%3A%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EProcess%2015040%3A%20ProxyWebRequest%20CrossSite%20from%20S-1-5-21-190996285-3174742192-1521001504-11052%20to%20%3CA%20href%3D%22https%3A%2F%2Fmail.teste1.com.br%3A443%2FEWS%2FExchange.asmx%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3Ehttps%3A%2F%2Fmail.teste1.com.br%3A443%2FEWS%2FExchange.asmx%3C%2FA%3E%20failed.%20Caller%20SIDs%3A%20NetworkCredentials.%20The%20exception%20returned%20is%20Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException%3A%20Proxy%20web%20request%20failed.%20---%26gt%3B%20System.Net.WebException%3A%20The%20request%20failed%20with%20HTTP%20status%20401%3A%20Unauthorized.%3C%2FP%3E%3CDIV%20class%3D%22FFpbKc%22%3E%26nbsp%3B%3C%2FDIV%3E%3CP%3E%3CSPAN%3EAny%20idea%3F%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-1882032%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1882032%22%20slang%3D%22en-US%22%3E%3CP%3EI%20would%20say%20to%20make%20sure%20that%20is%20indeed%20the%20error%20(401%20Unauthorized)%20for%20this%20free%2Fbusy%20direction%20ex2013%20-%26gt%3B%20ex2007%20.%3C%2FP%3E%0A%3CP%3EYou%20can%20try%20free%2FBusy%20test%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftestconnectivity.microsoft.com%2Ftests%2FFreeBusy%2Finput%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftestconnectivity.microsoft.com%2Ftests%2FFreeBusy%2Finput%3C%2FA%3E%26nbsp%3Bor%20OWA%20F12%20Network%20tab%20GetUserAvailability%20call%20and%20check%20Response%20body.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EAnd%20in%20logs%2C%20you%20would%20look%20at%20EWS%2FExchange.asmx%20or%20WebServicesAppPool%20stuff.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1930732%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1930732%22%20slang%3D%22en-US%22%3E%3CP%3EHello%20Mirela%2C%20amazing%20article.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20story%20where%202%20onprem%20exchange%20Organizations%20(org1%20and%20orerg2)%20share%20an%20smtp%20address%20space%20(%40company.com).%201%20org%20is%20already%20hybrid%20with%20O365.%20All%20works%20there%2C%20including%20mail%20routing%20via%20EOP%20and%20transport%20rules%20to%20decide%20left%20or%20right.%3C%2FP%3E%3CP%3ENow%20the%20second%20org%20wants%20their%20mailboxes%20also%20moved%20to%20Exchange%20Online.%20Both%20Orgs%20have%20company.com%20as%20primary%20SMTP%20for%20all%20users.%20We%20will%20be%20able%20to%20setup%20a%20second%20hybrid%20(minimal%20hybrid%20with%20manual%20corrections)%20to%20support%20migration%20and%20some%20level%20of%20co-existence.%20We%20expect%20F%2FB%20onprem%20(org2%20user)%20to%20cloud%20will%20work.%20However%20Cloud%20to%20Org2%20user%20onpremise%20is%20likely%20to%20fail.%20What%20would%20be%20required%2C%20if%20at%20all%20possible%2C%20to%20make%20this%20scenario%20work%20%3F%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EThanks%20a%20lot%2C%3CBR%20%2F%3EToni%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1930847%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1930847%22%20slang%3D%22en-US%22%3E%3CP%3EUnless%20it's%20a%20new%20feature%2C%20you'll%20not%20be%20able%20to%20assign%20the%20primary%20SMTP%20to%20two%20different%20tenants.%20I%20have%20used%20hybrid%20to%20migrate%207%20different%20schools%20into%20their%20own%20tenant%2C%20one%20at%20a%20time.%20We%20connected%20the%20Hybrid%20to%20the%20first%20domain%20and%20migrated%2C%20then%20move%20it%20to%20the%20second%20domain%20and%20repeat%20down%20the%20line.%20The%20assumption%20is%20that%20the%20'hybrid'%20is%20only%20needed%20for%20free%2Fbusy%20during%20the%20migration.%20Once%20everyone%20is%20moved%20up%2C%20you%20can%20still%20maintain%20SMTP%20connectivity%20for%20remaining%20mail%20flow.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1930921%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1930921%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F305937%22%20target%3D%22_blank%22%3E%40tonivervloet%3C%2FA%3E%26nbsp%3B%2C%20So%20the%20first%20question%20is%20related%20to%20tenants%2C%20is%20it%20Org1%20and%20Org2%20to%20same%20Tenant1%20or%20different%20tenant%2C%20Tenant2%3F%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThen%20yes%2C%20like%20Robert%20said%20above%2C%20you%20won't%20be%20able%20to%20migrate%20if%20the%20SMTP%20domain%20is%20shared%20between%202%20tenants%2C%20you%20need%20to%20have%20an%20accepted%20domain%20verified%2C%20unique%20in%20Tenant%202.%26nbsp%3B%3CBR%20%2F%3EIf%20same%20tenant%20and%202%20on-premises%20organizations%2C%20then%20I%20also%20don't%20see%20how%20to%20work-around%20the%20free%2Fbusy%20part%20if%20the%20on-premises%20users%20will%20have%20same%20SMTP.%20The%20Target%20Address%20Domain%20is%20the%20cloud%20organization%20relationships%20or%20cloud%20intra-organization%20connectors%20must%20be%20unique%20(even%20if%20you%20can%20set%20targetSharingEpr%20to%20point%20to%20EWS%20of%20each%20on-premises%20organization).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1945412%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1945412%22%20slang%3D%22en-US%22%3E%3CP%3Ehello%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F395212%22%20target%3D%22_blank%22%3E%40Mirela_Buru%3C%2FA%3E%26nbsp%3B%2C%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F73611%22%20target%3D%22_blank%22%3E%40Robert%20Styles%3C%2FA%3E%26nbsp%3B%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIndeed%20the%20address%20spaces%20is%20only%20assigned%20to%201%20tenant%20of%20course%2C%20but%20shared%20between%20a%20tenant%20(onprem%20%2B%20hybrid)%20and%20an%20onprem%20org%20that%20soon%20will%20be%20hybrid%20(to%20the%20same%20tenant)%20as%20well.%20But%20environments%20have%20company.com%20users%20(primary)%20and%20that%20works%20fine.%20Ideally%20that%20would%20have%20the%20shared%20as%20secondary%2C%20then%20we%20could%20uniquely%20identify%20both%20orgs.%3C%2FP%3E%3CP%3EWe%20can%20get%20an%20accepted%20domain%20verified%20for%20org%202%20no%20problem%2C%20but%20that%20domain%20is%20only%20used%20as%20a%20proxy.%20Its%20the%20old%20name%20space.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESeems%20we%20are%20stuck%20%3F%3C%2FP%3E%3CP%3E%3CBR%20%2F%3Ethanks%20already%20for%20your%20time%2Cboth.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EToni%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2101710%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2101710%22%20slang%3D%22en-US%22%3E%3CP%3EI%20didnt%20see%20this%20error%20on%20your%20list.%26nbsp%3B%20The%20issue%20we%20are%20having%20is%20an%20O365%20user%20can%20not%20see%20the%20free%2Fbusy%20calendar%20for%20an%20Exchange%202010%20user.%26nbsp%3B%20The%20Exchange%20user%20can%20see%20the%20Free%2FBusy%20of%20the%20O365%20user.%26nbsp%3B%20When%20this%20issue%20happened%20in%20the%20past%2C%20I%20would%20run%20IISREST%20on%20the%20Exchange%202010%20CAS%20servers%20and%20the%20problem%20would%20be%20fixed.%26nbsp%3B%20This%20time%2C%20its%20not%20working.%26nbsp%3B%20Any%20ideas%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22css-195%22%3EPerforming%20Free%2FBusy%20Lookup%3C%2FSPAN%3E%3CSPAN%20class%3D%22css-195%22%3EFree%2FBusy%20Lookup%20failed.%3C%2FSPAN%3E%3C%2FP%3E%3CDIV%20class%3D%22ms-Stack%20root-284%22%3E%3CDIV%20class%3D%22ms-Stack%20css-121%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22ms-Stack%20css-121%22%3E%3CSPAN%20class%3D%22css-195%22%3EAdditional%20Details%3C%2FSPAN%3E%3C%2FDIV%3E%3CDIV%20class%3D%22ms-Stack%20root-290%22%3E%3CSPAN%20class%3D%22css-195%22%3EFree%2FBusy%20Lookup%20failed%20with%20exception%3A%20Proxy%20web%20request%20failed.%20%2C%20inner%20exception%3A%20System.Web.Services.Protocols.SoapHeaderException%3A%20An%20error%20occurred%20when%20processing%20the%20security%20tokens%20in%20the%20message.%20at%20System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage%20message%2C%20WebResponse%20response%2C%20Stream%20responseStream%2C%20Boolean%20asyncCall)%20at%20System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult%20asyncResult)%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult%20asyncResult)%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest%20proxyWebRequest%2C%20QueryList%20queryList%2C%20IService%20service%2C%20IAsyncResult%20asyncResult)%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult%20asyncResult)%20at%20Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2101988%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2101988%22%20slang%3D%22en-US%22%3E%3CP%3EFound%20the%20solution%20to%20my%20problem.%26nbsp%3B%20I%20ran%20IISRESET%20again%2C%20waited%20for%20a%20bit%20and%20no%20change.%26nbsp%3B%20Then%20I%20ran%20this%20command%20on%20both%20Exchange%202010%20CAS%20server%20and%20now%20the%20Free%2FBusy%20is%20showing.%3C%2FP%3E%3CPRE%3E%3CSPAN%3E%3CSPAN%20class%3D%22hljs-pscommand%22%3EGet-FederationTrust%3C%2FSPAN%3E%20%7C%20%3CSPAN%20class%3D%22hljs-pscommand%22%3ESet-FederationTrust%3C%2FSPAN%3E%3CSPAN%20class%3D%22hljs-parameter%22%3E%20-RefreshMetadata%3C%2FSPAN%3E%0A%3C%2FSPAN%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2105789%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2105789%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F944499%22%20target%3D%22_blank%22%3E%40JeffP2021%3C%2FA%3E%26nbsp%3B%2C%20glad%20you%20managed%20to%20fix%20it.%20%3CBR%20%2F%3EThis%20is%26nbsp%3B%20similar%20to%20error%20%233%20from%20the%20PDF%20%3A%26nbsp%3B%3CSPAN%3E%22An%20error%20occurred%20when%20verifying%20security%20for%20the%20message%22%20so%20you%20would%20follow%20the%20exact%20steps%20%2F%20resolution%3C%2FSPAN%3E%26nbsp%3B%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Mirela_Buru_0-1611835955607.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F250239iBBBF3BFB858E6DE9%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22Mirela_Buru_0-1611835955607.png%22%20alt%3D%22Mirela_Buru_0-1611835955607.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3EYou%20might%20want%20to%20create%20a%20scheduled%20task%20for%20this%20as%20mentioned%20here%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fkeep-your-federation-trust-up-to-date%2Fbc-p%2F2097936%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fkeep-your-federation-trust-up-to-date%2Fbc-p%2F2097936%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2105804%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2105804%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20for%20the%20reply.%26nbsp%3B%20Im%20not%20sure%20how%20I%20missed%20number%203.%26nbsp%3B%20My%20problem%20is%20partially%20solved.%26nbsp%3B%20It%20worked%20for%20the%20calendar%20I%20had%20previously%20added.%26nbsp%3B%20I%20am%20still%20having%20the%20trouble%20adding%20new%20calendars.%26nbsp%3B%20I%20will%20look%20at%20number%203%20again%20and%20follow%20the%20suggested%20steps.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20call%20scheduled%20with%20MS%20Support%20today.%26nbsp%3B%20Hopefully%20it%20will%20be%20fixed%20by%20then.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2106515%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2106515%22%20slang%3D%22en-US%22%3E%3CP%3EMirela%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhy%20can%20I%20see%20one%20on-premise%20account%20(the%20original%20one%20that%20was%20working)%20an%20no%20other%20on-premise%20account%3F%26nbsp%3B%20The%20free%2Fbusy%20connectivity%20test%20passes%20for%20this%20user%2C%20but%20the%20others%20get%20the%20error%20in%20number%203.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20now%20working%20with%20MS%20Support.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2108496%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2108496%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20exchange%202010%20Sp3%20environment%20coexistence%20with%202016%20exchange%20server%20as%20hybrid.%20We%20have%20recently%20configured%20hybrid%20and%20migrated%20successfully%20migrated%20user%20to%20office%20365.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20noticed%20that%20free%20busy%20is%20not%20working%20from%20office%20365%20to%20On-prem%20users%20and%20vice%20versa.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20checked%20the%20Autodiscover%20endpoint%20from%20outside%20the%20network%20it%20is%20giving%20authentication%20prompt%20same%20for%20EWS%20gives%20the%20authentication%20prompt%20however%20free%20busy%20not%20working.%20As%20per%20the%20article%20I%20have%20set%20the%20target%20sharingepr%20but%20still%20we%20have%20issues.%20Also%20we%20have%20toggled%20wssauthentication%20for%20exchange%202010%20and%202016%20and%20restarted%20the%20app%20pool%20but%20no%20luck.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20please%20suggest%20us%20we%20are%20kind%20of%20stuck%20and%20not%20migrating%20any%20mailboxes%20to%20cloud.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2108807%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2108807%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F948030%22%20target%3D%22_blank%22%3E%40Shady111%3C%2FA%3E%26nbsp%3B%2C%20you%20should%20first%20check%20this%20blog%20announcement%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fkeep-your-federation-trust-up-to-date%2Fbc-p%2F2108225%22%20target%3D%22_blank%22%3EKeep%20your%20Federation%20Trust%20up-to-date%20-%20Microsoft%20Tech%20Community%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3Band%20make%20sure%20you%20performed%20RefreshMetadata%20(recommended%20it%20to%20run%20it%20twice).%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3ESecond%2C%20run%20the%20Free%2FBusy%20test%20on%20exrca.com%20here%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftestconnectivity.microsoft.com%2Ftests%2FFreeBusy%2Finput%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EMicrosoft%20Remote%20Connectivity%20Analyzer%3C%2FA%3E%20and%20see%20what%20is%20the%20error%20message%20for%20free%2Fbusy%20lookup%20from%20Cloud%20Source%20User%20to%20On-Premises%20Target%20User(s).%26nbsp%3B%20You%20might%20get%20different%20errors.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EOnce%20you%20know%20the%20free%2Fbusy%20error%20message%2C%20you%20can%20lookup%20the%20list%20with%2034%20errors%20from%20above%20and%20see%20if%20you%20find%20your%20error%20or%20similar%20one%20in%20the%20list.%20And%20in%20the%20PDF%20you%20have%20some%20suggestions%20to%20fix%20%2F%20troubleshoot%20this%3A%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-1686916665%22%20id%3D%22toc-hId-1563544452%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--864495426%22%20id%3D%22toc-hId--1172250756%22%3E%3CSTRONG%3EFree%2FBusy%20Errors%20discussed%20in%20the%20attached%20table%3A%3C%2FSTRONG%3E%3C%2FH3%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Flegacyfs%2Fonline%2Fmedia%2F2019%2F01%2FFB_Errors.FixesV6.pdf%22%20target%3D%22_blank%22%3EFB_Errors.FixesV6%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2108808%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2108808%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F944499%22%20target%3D%22_blank%22%3E%40JeffP2021%3C%2FA%3E%26nbsp%3B%2C%20might%20be%20needed%20to%20run%20RefreshMetadata%20twice%20and%20possibly%20iisreset%20on%20each%20server%3F%20Can%20you%20provide%20me%20with%20the%20case%20number%20(private%20message)%2C%20I%20can%20maybe%20take%20a%20look%20there%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2109906%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2109906%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20Mirela_Buru.%26nbsp%3B%20I%20have%20ran%20RefreshMetadata%20twice%20and%20ran%20IISRESET%20on%20both%20servers%2C%20no%20change.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20will%20send%20PM%20with%20MS%20case%20%23.%26nbsp%3B%20He%20could%20use%20all%20the%20help%20he%20can%20get.%26nbsp%3B%20Thank%20you!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2114357%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2114357%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3Emy%20free%20busy%20is%20failing%20with%20this%20error%20on%20both%20sides%20%2C%20Any%20thoughts%20inputs%20appreciated%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22ManjunBN_0-1612463716420.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F252352iB62C6BC8700DBBBF%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20role%3D%22button%22%20title%3D%22ManjunBN_0-1612463716420.png%22%20alt%3D%22ManjunBN_0-1612463716420.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2114887%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2114887%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F955591%22%20target%3D%22_blank%22%3E%40ManjunBN%3C%2FA%3E%26nbsp%3B%2C%20I%20would%20need%20a%20Test-FederationTrust%20-Verbose%20output%20from%20onpremises%20organization%20executed%20in%20Exchange%20Management%20Shell%20if%20Exchange%202010%20server%2C%20if%20Ex2013%2F2016%2F2019%2C%20then%20you%20would%20do%20it%20like%20this%3A%3C%2FP%3E%0A%3CP%3EOpen%20Windows%20PowerShell%20(blue)%3C%2FP%3E%0A%3CP%3Eadd-pssnapin%20*exchange*%3C%2FP%3E%0A%3CP%3Estart-transcript%3C%2FP%3E%0A%3CP%3ETest-FederationTrust%20-Verbose%20%7C%20fl%3C%2FP%3E%0A%3CP%3EGet-FederationTrust%20%7C%20fl%3C%2FP%3E%0A%3CP%3EGet-FederatedOrganizationIdentifier%20%7C%20fl%3C%2FP%3E%0A%3CP%3Estop-transcript%3C%2FP%3E%0A%3CP%3EYou%20can%20open%20a%20case%20and%20upload%20transcript%20there%20and%20send%20me%20the%20case%20number%20or%20you%20can%20send%20me%20a%20private%20message%20with%20the%20output.%3C%2FP%3E%0A%3CP%3EAlso%2C%20did%20Free%2FBusy%20work%20so%20far%3F%3C%2FP%3E%0A%3CP%3EDid%20you%20do%20any%20modification%20to%20the%20federation%20trust%20recently%3F%20like%20Set-FederatedOrganizationIdentifier%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2115510%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2115510%22%20slang%3D%22en-US%22%3E%3CP%3EThere%20are%20no%20changes%20made%2C%20its%20a%20new%20setup%26nbsp%3B%20front%20end%20with%202016%20and%20backend%20server%20with%202010%3C%2FP%3E%3CP%3EI%20have%20sent%20you%20the%20output%20in%20PVT%20messages.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2115950%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2115950%22%20slang%3D%22en-US%22%3E%3CP%3E%3CFONT%3EHello%2C%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20point%2010%20of%20the%20PDF%2C%20where%20%3CFONT%3EReverse%20Proxy%20%2FFirewall%20logs%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2116834%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2116834%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F955777%22%20target%3D%22_blank%22%3E%40JimmyP1000%3C%2FA%3E%26nbsp%3B%2C%20this%20is%20specific%20to%20the%20appliance%20you%20would%20be%20using.%20Best%20to%20ask%20the%20vendor%20if%20logging%20can%20be%20enabled%20and%20how%20the%20logs%20can%20be%20retrieved.%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOn%20the%20Exchange%20Server%20side%2C%20you%20would%20be%20checking%20these%20logs%20to%20see%20if%20the%20request%20from%20Exchange%20Online%20reached%20Exchange%20%2F%20IIS%20server%3A%3C%2FP%3E%0A%3CP%3E-%20IIS%20logs%20%2F%20HTTPProxy%20logs%20%2F%20HTTPerr%20logs%26nbsp%3Bwhen%20reproducing%20the%20Free%2FBusy%20issue%20from%20EXO%20User%20to%20On-Premises%20user(s).%3C%2FP%3E%0A%3CP%3E-%20Network%20trace%20(like%20Netmon)%20when%20reproducing%20the%20Free%2FBusy%20issue%20from%20EXO%20User%20to%20On-Premises%20user(s).%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20can%20use%20Free%2FBusy%20Test%20on%20Remote%20Connectivity%20Analyzer%3A%20%3CA%20href%3D%22https%3A%2F%2Ftestconnectivity.microsoft.com%2Ftests%2FFreeBusy%2Finput%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftestconnectivity.microsoft.com%2Ftests%2FFreeBusy%2Finput%3C%2FA%3E%20%2C%20this%20way%20you%20see%20the%20Free%2FBusy%20error%2C%20if%20DNS%20part%20is%20fine%2C%20ports%20unblocked%2C%20certificate%20and%20SSL%2FTLS%20connections%20ok.%26nbsp%3B%20The%20Free%2FBusy%20connection%3CSPAN%20style%3D%22font-family%3A%20inherit%3B%22%3E%26nbsp%3Bwill%20be%20coming%20from%20an%20Exchange%20Online%20IP%20Address%20(if%20cloud%20side%20is%20configured%20ok)%20but%20Autodiscover%20call%20will%20be%20coming%20from%20an%20the%20tool%20IP%20addresses%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftestconnectivity.microsoft.com%2FPages%2FChangeList.htm%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3ERemote%20Connectivity%20Analyzer%20Change%20List%20(microsoft.com)%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2116861%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2116861%22%20slang%3D%22en-US%22%3E%3CP%3EMirela%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20the%20info.%20The%20logs%20on%20the%20Exchange%20server%20are%20clear%20of%20errors.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20trying%20to%20use%20EXRCA%2C%20it%20never%20completes.%20It%20always%20times%20out.%20So%20I%20cannot%20get%20any%20further%20information%20from%20there.%3C%2FP%3E%3CP%3EThis%20is%20what%20we%20are%20trying%20to%20accomplish.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELet%20me%20explain%20our%20situation.%20We%20have%20joined%20two%20different%20organizations%20with%20a%20federation%20trust.%3C%2FP%3E%3CP%3E-%20CompanyA%20(EXO)%20and%20CompanyB%20(Exchange%202016%20on-prem).%3C%2FP%3E%3CP%3E-%20CompanyB%20(Ex2016)%20has%20no%20problem%20viewing%20calendar%20entries%20from%20CompanyA%20(EXO)%20(both%20from%20the%20Calendar%20and%20the%20Scheduler%20Assistant).%3C%2FP%3E%3CP%3E-%26nbsp%3B%3CFONT%3ECompanyA%20(EXO)%20is%20%3CU%3Eonly%3C%2FU%3E%20able%20to%20see%20calendar%20entries%20from%20CompanyB.%20%3CU%3EBut%20not%20in%20the%20Scheduler%20Assistant%3C%2FU%3E.%20This%20is%20the%20problem.%26nbsp%3B%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20found%20these%20two%20errors%3A%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%20-%3CSPAN%3Ewhen%20doing%20a%20network%20trace%20(F12)%20from%20EXO%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CFONT%3E%26nbsp%3B%20%26nbsp%3B%26nbsp%3B%201.%20Proxy%20web%20request%20failed.%20%2C%20inner%20exception%3A%20The%20request%20failed%20with%20HTTP%20status%20401%3A%20Unauthorized%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%3E%26nbsp%3B%26nbsp%3B%20-when%20I%20run%20this%20command%20on%20CompanyB%20(Exch2016%20on-prem)%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%202.%20%26nbsp%3B%26nbsp%3B%20Error%3A%5BOAuthTokenBuilder%3AGetAppToken%5D%20unable%20to%20continue%20building%20token%2C%20given%20that%20both%20trusted_issuer%20and%20realm%20from%20the%3CBR%20%2F%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20challenge%20are%20empty%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%3CFONT%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%26nbsp%3B%20Error%3AThe%20challenge%20value%20returned%20from%20'%3CEM%3Email.domain%3C%2FEM%3E.com'%20is%20not%20valid.%3CBR%20%2F%3E%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3ENot%20sure%20if%20they%20are%20related%2C%20but%20any%20help%20would%20be%20appreciated.%20Thanks.%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%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-2116883%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2116883%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F955777%22%20target%3D%22_blank%22%3E%40JimmyP1000%3C%2FA%3E%26nbsp%3B%2C%20this%20would%20require%20a%20support%20case%20to%20investigate.%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAre%20Company%20A%20and%20Company%20B%20in%20hybrid%20organization%20or%20they%20are%20separate%3F%26nbsp%3B%20or%20is%20company%20B%20in%20hybrid%20(some%20users%20in%20onprem%20and%20some%20in%20exo)%20%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20A%20and%20B%20are%20not%20in%20Hybrid%2C%20then%20they%20are%20probably%20using%20Organization%20Relationships%20for%20Free%2FBusy%20and%20Sharing%20Policies%20for%20Calendar%20Sharing%201%3A1.%20So%20you%20would%20need%20to%20check%20Get-OrganizationRelationship%20both%20sides%20and%20make%20sure%20they%20are%20configured%20right.%20You%20can%20send%20me%20the%20outputs%20in%20a%20private%20message%20so%20that%20I%20can%20double%20check%20or%20upload%20them%20in%20the%20support%20case.%20You%20would%20look%20at%20Target%20Address%20Domains%20(From%20and%20To%20SMTP%20domains)%2C%20if%20org%20relationship%20is%20enabled%20both%20sides%2C%20if%20targetautodiscoverepr%20or%20targetsharingepr%20are%20correct%20set%2C%20if%20free%2Fbusy%20access%20specified%20on%20the%20org%20rel%20is%20not%20restricted.%20You%20can%20check%20config%20part%20in%20first%20part%20of%20this%20blog.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThen%2C%20not%20sure%20what%20is%20the%20command%20you%20ran%20for%20Oauth%20token%2C%20I%20assume%20Test-OauthConnectivity.%20This%20is%20not%20needed%20if%20the%20organizations%20are%20not%20in%20Hybrid%20deployment%20with%20each%20other.%20Only%20in%20Hybrid%20we%20use%20Get-IntraOrganizationConnector%20for%20Free%2FBusy.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2116929%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2116929%22%20slang%3D%22en-US%22%3E%3CP%3EBoth%20companies%20are%20separate.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20will%20send%20you%20the%20outputs%20privately.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnd%20yes%2C%20I%20did%20use%20the%20Test-OauthConnectivity%20command.%20Since%20we%20are%20not%20hybrid%2C%20you%20can%20disregard%20this%20error%20message.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2116940%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2116940%22%20slang%3D%22en-US%22%3E%3CP%3EMirela%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETried%20sending%20you%20a%20private%20message%20but%20keep%20getting%20this%20%3A%26nbsp%3B%22Private%20message%20reached%20limit%2C%20try%20again%20later...%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271038%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271038%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20a%20unique%20situation%20I%20guess.%20I%20have%20a%20EXCH2016%20hybrid%20with%20a%20few%20mailboxes%20on%20premises%20and%20most%20in%20O365.%20Free%2Fbusy%20works%20fine%20both%20directions.%20but%20now%20we%20acquired%20multiple%20companies%2C%20each%20in%20O365%20(no%20hybrid).%20We%20configured%20org%20relationsships%20and%20they%20can%20see%20on%20prem%20free%2Fbusy%20ok%2C%20but%20can't%20see%20hybrid%20cloud%20user's%20availability.%20If%20they%20manually%20test%20using%20the%20onmicrosoft.com%2C%20it%20also%20works.%26nbsp%3B%20OWA%20logs%20from%20external%20party%20show%3A%3C%2FP%3E%3CP%3E%22Autodiscover%20failed%20for%20email%20address%20jdoe%40xxxcorp.mail.onmicrosoft.com%20with%20error%20System.Web.Services.Protocols.SoapHeaderException%3A%20An%20error%20occurred%20when%20verifying%20security%20for%20the%20message.%22%3C%2FP%3E%3CP%3ESo%2C%20on%20prem%20is%20redirecting%20autodiscover%20as%20expected.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20tested%20ok%20a%20year%20ago.%20The%20only%20change%20was%20we%20got%20rid%20of%20EXCH2010%20and%20reran%20the%20HCW%20to%20enable%20OAuth.%20It%20has%20been%20suggested%20to%20disable%20oauth%20again%2C%20but%20I%20don't%20want%20to.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271819%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271819%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F666084%22%20target%3D%22_blank%22%3E%40wayne_hetrich%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20need%20to%20look%20into%20Hybrid%20Mesh%20scenario%3A%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fthe-hybrid-mesh%2Fba-p%2F605910%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fexchange-team-blog%2Fthe-hybrid-mesh%2Fba-p%2F605910%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECloud%20organization%20(let's%20call%20it%20EXO%20Org%20B)%20needs%20to%20have%202%20organization%20relationships%3A%20one%20for%20your%20on-premises%20Exchange%20xxxcorp.com%20and%20one%20for%20your%20Cloud%20Exchange%20Online%20Organization%3A%3C%2FP%3E%0A%3CP%3ENew-OrganizationRelationship%20-Name%20Hybrid_CloudSide%20-TargetApplicationUri%20outlook.com%20-TargetAutodiscoverEpr%20%3CA%20href%3D%22https%3A%2F%2Fautodiscover-s.outlook.com%2Fautodiscover%2Fautodiscover.svc%2FWSSecurity%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fautodiscover-s.outlook.com%2Fautodiscover%2Fautodiscover.svc%2FWSSecurity%3C%2FA%3E%26nbsp%3B-FreeBusyAccessEnabled%20%24true%20-FreeBusyAccessLevel%20AvailabilityOnly%20-DomainNames%20xxxcorp.mail.onmicrosoft.com%2Cxxxcorp.onmicrosoft.com%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3EI%20imagine%20Org%20B%20only%20has%201%20Org%20Relationship%20for%20your%20custom%20domain%20(whose%20autodiscover%20points%20to%20exchange%20on-premise%20hybrid)%3C%2FP%3E%0A%3CP%3EGet-FederationInformation%20-DomainName%20xxxcorp.com%20-BypassAdditionalDomainValidation%7C%20New-OrganizationRelationship%20-Name%20Hybrid_OnPremSide%20-FreeBusyAccessEnabled%20%24true%20-FreeBusyAccessLevel%20AvailabilityOnly%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3EAnd%20then%20Org%20B%20needs%20to%20have%20a%20mail%20user%20created%20for%20jdoe%40xxxcorp.com%20(cloud%20target%20user%20primary%20smtp%20address)%20with%20external%20email%20address%20set%20to%20jdoe%40xxxcorp.mail.onmicrosoft.com%20(that%20resolves%20to%20the%20organization%20relationship%20with%20xxxcorp.mail.onmicrosoft.com%20target%20domain).%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EOr%20the%20end%20users%20in%20Org%20B%20would%20put%20directly%20in%20Scheduling%20Assistant%20jdoe%40xxxcorp.mail.onmicrosoft.com%20and%20not%20jdoe%40xxxcorp.com%20(which%20is%20pointing%20to%20your%20on-premises%20org).%20Org%20B%20can%20test%20this%20(put%20jdoe%40xxxcorp.mail.onmicrosoft.com%20in%20Target%20Mailbox%20Email%20Address)%20in%20%3CA%20href%3D%22https%3A%2F%2Ftestconnectivity.microsoft.com%2Ftests%2FFreeBusy%2Finput%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Ftestconnectivity.microsoft.com%2Ftests%2FFreeBusy%2Finput%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2271862%22%20slang%3D%22en-US%22%3ERe%3A%20Demystifying%20Hybrid%20Free%2FBusy%3A%20Finding%20errors%20and%20troubleshooting%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2271862%22%20slang%3D%22en-US%22%3E%3CP%3EOr%2C%20if%20you%20move%20all%20mailboxes%20to%20cloud%2C%20then%20you%20can%20switch%20Autodiscover%20for%20xxxcorp.com%20to%20point%20to%20Office%20365.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Version history
Last update:
‎May 15 2020 05:20 PM
Updated by: