Site mailboxes with Exchange Online?

Hi All,
We would like to use Site Mailboxes with our On-Prem 2013 Ent deployment. In addition to our On-prem deployement, we also have the full O365 suite including Exchange, SharePoint, Lync, etc.
Question: Can we use Site Mailboxes in our On-prem environment, connected to Exchange online?
The tables at the bottom of the following article indicates that SharePoint Online must be included in the O365 subscription, but the notes are not clear as to whether it is a requirement to use the SharePoint Online instance of SharePoint or if we could
use our On-Prem instance.
http://technet.microsoft.com/en-us/library/exchange-online-sharing-and-collaboration.aspx

Hi,
According to your post, my understanding is that you wanted to use SharePoint 2013 on-prem and Exchange online for Site mailbox feature.
I’d like to briefly introduce the Site mailbox creation in SharePoint online at first. The Site mailbox is enabled by the site collection admin and the whole creation process is finished from the background. For the users who want to access the Site mailbox,
it requires the SharePoint online users to also have the Exchange online licenses.
In SharePoint on-premise, the Site Mailbox requires Exchange Server 2013 is mentioned in this SharePoint Server 2013 instruction:
Configure site mailboxes in SharePoint Server 2013.
Since Exchange on-premise includes more features and capabilities than Exchange online, I’ think it’s not feasible to integrate the SharePoint on-premise to the Exchange online service for setting up the Site Mailbox feature.
Best Regards,
Linda Li
Linda Li
TechNet Community Support

Similar Messages

Cutover onprem mailbox to exchange online without Hybrid configuration wizard.

HI!
We have on premise exchange server 2010 sp2 deployed with domain1.com. We have registered our tenant and verified the ownership of domain1.com on our office365 tenant. We have successfully deployed EOP and configured inbound and outbound connectors
and all the mailflow is working fine. We havenot deployed directory sync server and ADFS for the deployment of EOP. Our Mx is pointed to domain1-com.mail.protection.outlook.com and all the mails are sent and received through EOP. I
want to move a user mailbox such as [email protected] to Exchange Online from on-premise exchange without configuring Dirsync and Exchange Hybrid configuration wizard. I already know the some of the limitations.
If I create a user account [email protected] on the tenant and activate the Exchange License on office365 to create the Mailbox on Exchange online.
I want to know that if I have to create any other send and receive connector or any other configuration either on office365 or exchange online if I cutover one user from our on-premise to exchange online without configuring Exchange Hybrid configuration
wizard on our on premise exchange server??
Will this effect the mailflow between onpremise and exchange online users?
Regards,
Abdullah Salam

It's not clear to me what type of migration you're trying to do. A cutover migration would be an option as long as you understand the limitations of that process. Otherwise are you looking to use a third-party migration tool or some other
mechanism?
The reason you would end up with two mailboxes is if when you assign an Exchange license to a user in the cloud without DirSync, a mailbox is provisioned for that user. You can assign a license after the mailbox is moved assuming you have a mail-enabled
user in the cloud and can do a remote move to it.
Once you manage to get the mailbox to the cloud, now you have to deal with routing which means you'll need a mail-enabled user on-premises for every mailbox in the cloud and will need to have a target address with a coexistence domain such as "@tenant.mail.onmicrosoft.com".
Likewise, Exchange Online will need a mail-enabled user for every on-premises mailbox in order to have a populated GAL and route in that direction.
For security reasons we don't to setup Dirsync and hybrid.
I hear this occasionally and remind organizations that you're putting the actual data (the stuff the credentials protect) in Microsoft's datacenters. If it's a question of trust, cloud services might not be the most appropriate solution for the
organization. The Office 365 Trust Center (http://trust.office365.com/) can provide some insight into the controls that Microsoft has in place to protect your data.
DirSync or the new AADSync can be scoped such that they only sync limited objects. From there, you have the options of Password (Hash) Sync with DirSync (not yet with AADSync) or using AD FS which leaves the authentication with your on-premises
directory.
Joseph Palarchio http://www.itworkedinthelab.com

Lync 2013 On Premises integration with Exchange Online Unified Messaging

I am working on deploying Lync 2013 Server on premises and integrating it with Exchange Online. We do not use Exchange on premises.
My question is how to integrate with Unified Messaging specifically. Other functions like Calendar, call logs seem to be working fine.
There are many guides online on how to do this, and I have read many and attempted to follow with no luck. All seem to assume that UM has already been deployed on prem which I don't have. Is this possible to integrate Lync with Exchange Online without having
and Exchange deployment on premises first.
Another source of confusion is the Office Voice Access number and how Lync clients dial voicemail. Where does this go if somebody dials internally (from Lync) and externally (from PSTN)? Exchange online or Lync on prem? And if Lync, then my guess would be
Lync forwards on to Exchange Online UM somehow. Do I have to purchase a number from somewhere because of it being on 365 or can I use a spare DID?
From my tests so far, when I call voicemail as any user, it seems to dial that same user and then the call fails.
Hopefully someone can shed some light on this for me.

You can integrate Exchange UM with Lync Server 2013.
Please check the deployment process at http://technet.microsoft.com/en-us/library/gg398968.aspx
Lisa Zheng
TechNet Community Support

Lync 2010 Integration with Exchange Online UM

Hi All,
Recently I have got the project to integrate Lync 2010 with Exchange Online UM, I have gone through the TechNet article but it seems very confusing and things are not very clear, can some please please help me out in this that how to setup this, what ports
do I need to allow from on premises to Exchange online UM.
There are some other questions as well which is not clear from TechNet.
1. Create SRV record, when I create the SRV record in external dns then in the host providing this service will be access edge fqdn is this correct.
2. Configure Edge Server for federation (do I need to run this on Edge server or on Lync FE Servers, I believe on FE SErvers is this correct, if yes then do I need to run the setup again on Edge server by exporting Topology or the replication will
do the needful)
3. To Create a hosting provider do I need to run this command on Edge or on Lync FE Servers.
4. To create a hosting provider you need to run the command
New-CsHostingProvider -Identity Fabrikam.com -Enabled $True -EnabledSharedAddressSpace $True -HostsOCSUsers $False -ProxyFQDN "proxyserver.fabrikam.com" -IsLocal $False -VerficationLevel UseSourceVerification
now from the above command -Identity what will be the Identity name it can be any thing or it should be some thing related to exchange online um.
for -proxyfqdn what will be the FQDN name here, from where I can get this name
5. Do I need to add or remove any domain names in office 365 if yes then what domain names it will be
6. If my sip address is abc.com then do I have to add this domain name in exchange online or do I need to add another domain name how this setup will be
7. if I will create any new domain in the dns in office 365 then do I need to add this domain name in my external dns if yes then which ip it will be pointed to.
Please guys help me out as I m new to exchange um online and I have never integrated it before.
Appreciate your help
If answer is helpful, please hit the green arrow on the left, or mark as answer. Salahuddin | Blogs:http://salahuddinkhatri.wordpress.com | MCITP Microsoft Lync

1. Yes, create an SRV as per Lync documentation for external access to Edge.
2. Correct, all config is done on
Front End and will be replicated to the Edge servers. As long as your Edge servers are replicating successfully theere is no need to do a manual import.
3. Run this PowerShell on the Front End
4. Identity is a name to identify the hosting provider such as "Exchange Online". See http://technet.microsoft.com/en-us/library/gg398490.aspx
proxyfqdn for Exchange Online is exap.um.outlook.com
5. Your SIP domain will need to be added a a vanity domain in Office 365
6. Same as above, just add as vanity domain
7. Any added domains need to be setup as per Office 365 documentation, nothing special needs to be done for UM integration.
Check this out for more info - http://lyncinsider.com/instant-messaging/how-to-connect-lync-server-to-exchange-online-part-1/
Andrew Morpeth
Lync Server Specialist - Auckland, NZ
Check out my blog

Lync on premises with Exchange online UM SRV record

Hi,
We have Lync 2013 on premises and we have Hybrid exchange deployment, recently we have integrated Lync on premises with Exchange online UM, we have configured subscriber access and I have done all configuration, created hosted voice mail policy, created
Subscriber access UM contact.
Problem is that if a user dials from Lync client to voice mail (Exchange online UM Subscriber Access number) the call successfully establish, if the same user is outside the organization and wants to call the Exchange online UM Subscriber
Access number from his mobile or from his home phone number the call doesn't connect, this problem is not from the same user any one from outside the organization can not call to subscriber access number from his mobile or from his landline (outside the organization
numbers)
I have done some logging on Lync Edge server and found two things:
When a user calls from Lync client to O365 UM Subscriber access the call establish successfully and when I see the call logs I am seeing the
[email protected] and SRV record for the domain.com is verified
When a user calls from outside the organization (Landline or mobile) to O365 UM subscriber access the call doesn't establish and when I see the call logs I am seeing
[email protected] and subscriber access number as
[email protected] and the error says Unable to resolve DNS SRV record for domain it.domain.com.
Please note our internal domain is it.domain.com and our external or smtp domain is domain.com
In Lync 2013 the default sip domain is also it.domain.com and additional sip domain is domain.com
Pleasae help me to resolve the issue.
If answer is helpful, please hit the green arrow on the left, or mark as answer. Salahuddin | Blogs:http://salahuddinkhatri.wordpress.com | MCITP Microsoft Lync

The issue is that your default domain is it.domain.com. I suspect that even if your Edge server is able to route this call back to Exchange online, that tenant will reject this call as it will not be able to find it.domain.com or federation SRV record associated
with it.
You will need to change your default SIP domain to your public SIP domain. If you decide to do this, please note that you will also need to review any impact on the simple URLs (and certificates if applicable).
It is also recommended to perform an export-csconfiguration command to backup the topology before making these changes.
Hope this helps.
SinghP80

Outlook 2013 with exchange online account disconnected, tryin to connect for hours or indefinitely

I posted this in another forum (office 365) and was told to copy it here as it wasn't an office 365 issue so here is what I posted there:
===================================
Let me see if I can clarify better. This issue has been ongoing as long as I have worked for this client (I started in January but have been told the issue has been going on since before November of last year). The client has multiple construction sites
and its headquarters. There is a remote desktop server setup with a public IP address for the users "in the field" for accessing network resources at headquarters. At major construction sites (currently 3) they have high speed internet service installed
since the projects typically are 1+ years to complete. So at current times we have the following:
Main office:
Remote Desktop Server with logins for all employees
Main 2012R2 server
50MB/s internet connection via CenturyLink ISP
Site 1:
3 main users of computers. 1 constant user, 2 minimal use users. All 3 have experience the issue 3+ times a week
Comcast 50MB/S ISP
Site 2:
3 Main users of computers. 1 constant, 2 medium use users. All 3 experience the issue 3+ times a week
Comcast 50MB/s ISP
Site 3:
4+ computer users. 1 constant, 2 medium use users and the rest check email couple times a day. They also experience the disconnect issue 3+ times a week
15 MB/S DSL from CenturyLink ISP
There have been instances where (as examples) user 1a called me to tell me it was happening. Users 1b and 1c were not experiencing the issue. I was able to use a remote tool called Teamviewer to connect to her computer. Once connected I tried to open OWA
but it would not connect. I tried to ping the site and could not get a response. To verify I remoted into user 1b computer and his outlook was still connected and pinged fine. Both users being at the same site are on the same network. Had user 1a remote desktop
into the RDserver at the main office. Remoted into the server at the office her outlook on that machine connected no issues (in my mind rules out account issue?).
I don't believe it is network related due to the other computers working fine and being able to connect to her computer indicated to me that her NIC was fine. I don't think it was her account because it worked fine from the RD Server plus email service to
iPads/iPhones continue to work without issue. Once the computer is rebooted everything works fine for a while (could be hours, could be days).
Now to answer the questions for you:
1. it happens to all computers not at the main office but happens at random times to them. It also does not affect every computer at a remote location. It could be 1 or it could be multiple computers at the same time.
2. Affected users iPhones, iPads and outlook 2013 pro session on the RD Server at the main office continue to work no issues.
3. They cannot get to OWA on their machines when in that state, however can log into OWA on another machine plus the answer to #2 above.
4. It is all users at those locations, however I have experienced it myself at my house 1 time since January (I have a different exchange online plan/company than the one I am discussing in this post). The issue is random and it is uncertain if it will correct
itself if left sitting long enough (longest time it has been left is about 20 minutes or so) however even 20 minutes is a long time to wait for the service to return so users just reboot.
Please let me know If you have any solutions/ideas.
Thanks,
Brandon Smith
Cadence Communications
====================================
Hi Branon,
Thanks for your detailed information.
After going your post carefully, I am impressed by your strong technical skills. Regarding “I don't believe it is network related due to the other computers working fine and being able to connect to her computer indicated to me that her NIC was
fine. I don't think it was her account because it worked fine from the RD Server plus email service to iPads/iPhones continue to work without issue. Once the computer is rebooted everything works fine for a while (could be hours, could be days)” ,
I go along with you. Since the affected account could connect to other clients without issue , it indicates Office 365 account is no problem. And other computer were working fine and can connect to her computer, it shows the network environment does not cause
the issue. In this situation, the issue should relate to the specific Outlook Client. However this forum mainly focuses on Office 365 online services, to get more accurate responses, it’s suggested that you raise the problem in the Outlook forum. If they got
any result and you need further assistance from Office 365 side, please feel free to let us know.
In addition, about “I have had the users try to use OWA when it gets disconnected but they cannot get to that URL either. IE comes up with page not found”, I’d like to collect some information:
1. Does the issue only happen to IE? Have you tried logging in other browsers using the OWA address (like Chrome or Firefox)? Does it work?
2. Does only this user have the issue? Does it happen to other users?
3. Which version of Internet Explorer browser does the user use?
4. Could you provide us with the whole screenshot of the error message? You can post screenshots in our forum by clicking Use rich formatting and selecting the Insert Image icon.
Also, please try the following steps for troubleshooting:
a. Clear the IE caches and cookies when you log into Office 365 again.
b. Use the InPrivate Browsing of Internet Explorer to login.
c. Reset Internet Explorer’s settings, and try again.
d. Try to login in another network environment.
If there is any update, please let us know. I ’ll keep on monitoring this thread.
Best regards,
Jamie
===============================
As of today we still randomly experience this disconnect issue. Just today I had my test user call me to say she was disconnected. She is in location 2 where I have a test laptop also setup with her logged in. When she called I had her check the test laptop
and the outlook profile on that machine (same network) was still connected while her computer was not connected. I had her run the online analyzer tool on her machine (the one that would not connect) which ran for almost 2 hours. The tool finished right at
the same time that her outlook finally connected back to the server.
If anyone has any ideas/solutions please let me know.
Thanks in advance,
Brandon Smith
Cadence Communications Inc.

Oddly enough my computer is right at this moment in this same disconnected state. Outlook shows an exclamation point in a yellow triangle. Its state is disconnected. If I go to portal.office.com I get to the login page but get page can't be displayed after
entering my credentials. I tried using google and found this for login
https://outlook.office365.com/owa/ it too times out and can't be displayed.
if I try and ping these sites I get:
====================================================================
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\brandon.CAD1>ping portal.office.com
Pinging us.portal.office.akadns.net [2a01:111:f100:4001::4625:61ea] with 32 byte
s of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 2a01:111:f100:4001::4625:61ea:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
C:\Users\brandon.CAD1>ping login.microsoftonline.com
Pinging aadg.windows.net.nsatc.net [168.62.24.150] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 168.62.24.150:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
===============================================================================
If I remote into another machine at a client site I can log into portal.office.com using my email account.
I ran the outlook connectivity analyzer tool and got this if it helps:
===============================================================
Testing Outlook connectivity.
The Outlook connectivity test completed successfully.
Additional Details
Elapsed Time: 41017 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for
[email protected].
Autodiscover was tested successfully.
Additional Details
Elapsed Time: 12161 ms.
Test Steps
Attempting each method of contacting the Autodiscover service.
The Autodiscover service was tested successfully.
Additional Details
Elapsed Time: 12161 ms.
Test Steps
Attempting to test potential Autodiscover URL
https://cadcom.us:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 475 ms.
Test Steps
Attempting to resolve the host name cadcom.us in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 184.168.55.1
Elapsed Time: 173 ms.
Testing TCP port 443 on host cadcom.us to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 149 ms.
Testing the SSL certificate to make sure it's valid.
The SSL certificate failed one or more certificate validation checks.
Additional Details
Elapsed Time: 152 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server cadcom.us on port 443.
The Microsoft Connectivity Analyzer wasn't able to obtain the remote SSL certificate.
Additional Details
The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.
Elapsed Time: 91 ms.
Attempting to test potential Autodiscover URL
https://autodiscover.cadcom.us:443/Autodiscover/Autodiscover.xml
Testing of this potential Autodiscover URL failed.
Additional Details
Elapsed Time: 9000 ms.
Test Steps
Attempting to resolve the host name autodiscover.cadcom.us in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 132.245.92.232, 132.245.58.104, 132.245.3.136, 132.245.64.248, 132.245.82.56, 132.245.88.200, 132.245.81.200, 132.245.81.136, 2a01:111:f400:2c84::8, 2a01:111:f400:1014::8, 2a01:111:f400:2c61::8, 2a01:111:f400:2c5d::8, 2a01:111:f400:142a::8,
2a01:111:f400:5242::8, 2a01:111:f400:2414::8, 2a01:111:f400:4c0b::8
Elapsed Time: 304 ms.
Testing TCP port 443 on host autodiscover.cadcom.us to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
Tell me more about this issue and how to resolve it
Additional Details
A network error occurred while communicating with the remote host.
Elapsed Time: 8696 ms.
Attempting to contact the Autodiscover service using the HTTP redirect method.
The Autodiscover service was successfully contacted using the HTTP redirect method.
Additional Details
Elapsed Time: 2684 ms.
Test Steps
Attempting to resolve the host name autodiscover.cadcom.us in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 132.245.92.232, 132.245.58.104, 132.245.3.136, 132.245.64.248, 132.245.82.56, 132.245.88.200, 132.245.81.200, 132.245.81.136, 2a01:111:f400:2c84::8, 2a01:111:f400:1014::8, 2a01:111:f400:2c61::8, 2a01:111:f400:2c5d::8, 2a01:111:f400:142a::8,
2a01:111:f400:5242::8, 2a01:111:f400:2414::8, 2a01:111:f400:4c0b::8
Elapsed Time: 39 ms.
Testing TCP port 80 on host autodiscover.cadcom.us to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 57 ms.
The Microsoft Connectivity Analyzer is checking the host autodiscover.cadcom.us for an HTTP redirect to the Autodiscover service.
The redirect (HTTP 301/302) response was received successfully.
Additional Details
Redirect URL:
https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml
HTTP Response Headers:
Pragma: no-cache
X-FEServer: BY2PR07CA071
Connection: close
Content-Length: 0
Cache-Control: no-cache
Date: Tue, 21 Apr 2015 04:40:05 GMT
Location:
https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml
Server: Microsoft-IIS/8.0
X-Powered-By: ASP.NET
Elapsed Time: 47 ms.
Attempting to test potential Autodiscover URL
https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml
Testing of the Autodiscover URL was successful.
Additional Details
Elapsed Time: 2540 ms.
Test Steps
Attempting to resolve the host name autodiscover-s.outlook.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 132.245.24.82, 132.245.92.34, 132.245.92.194, 132.245.80.146, 157.56.239.194, 132.245.64.146, 2a01:111:f400:1414::2, 2a01:111:f400:2c2c::2, 2a01:111:f400:1428::2, 2a01:111:f400:4c32::2, 2a01:111:f400:2c40::2, 2a01:111:f400:5000::2
Elapsed Time: 345 ms.
Testing TCP port 443 on host autodiscover-s.outlook.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 44 ms.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Additional Details
Elapsed Time: 177 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover-s.outlook.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US, Issuer: CN=Microsoft IT SSL SHA1, OU=Microsoft IT, O=Microsoft Corporation, L=Redmond, S=Washington, C=US.
Elapsed Time: 119 ms.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name autodiscover-s.outlook.com was found in the Certificate Subject Alternative Name entry.
Elapsed Time: 0 ms.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US.
One or more certificate chains were constructed successfully.
Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE.
Elapsed Time: 18 ms.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Elapsed Time: 3 ms.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 2/13/2015 12:38:15 AM, NotAfter = 2/13/2016 12:38:15 AM
Elapsed Time: 0 ms.
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details
Accept/Require Client Certificates isn't configured.
Elapsed Time: 146 ms.
Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
The Microsoft Connectivity Analyzer successfully retrieved Autodiscover settings by sending an Autodiscover POST.
Additional Details
Elapsed Time: 1827 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL
https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml for user
[email protected].
The Autodiscover XML response was successfully retrieved.
Additional Details
Autodiscover Account Settings
XML response:
<?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>Brandon Smith</DisplayName>
<LegacyDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon</LegacyDN>
<DeploymentId>5135be05-06e4-4e3b-9cbd-f39b6108647f</DeploymentId>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol Type="mapiHttp">
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<MailStore>
<ExternalUrl>https://outlook.office365.com/mapi/emsmdb/[email protected]</ExternalUrl>
</MailStore>
<AddressBook>
<ExternalUrl>https://outlook.office365.com/mapi/nspi/[email protected]</ExternalUrl>
</AddressBook>
</Protocol>
<Protocol>
<Type>WEB</Type>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<Internal>
<OWAUrl AuthenticationMethod="LiveIdFba, OAuth">https://outlook.office365.com/owa/</OWAUrl>
<Protocol>
<Type>EXCH</Type>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
</Protocol>
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba">https://outlook.office365.com/owa/cadcom.us/</OWAUrl>
<Protocol>
<Type>EXPR</Type>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
</Protocol>
</External>
</Protocol>
<Protocol>
<Type>EXHTTP</Type>
<Server>outlook.office365.com</Server>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
<OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>
<OABUrl>https://outlook.office365.com/OAB/fb606d0b-79d8-4255-9c7b-552a0fccb72f/</OABUrl>
<UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>On</SSL>
<AuthPackage>Basic</AuthPackage>
<EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>
<EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>
<SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>
<EcpUrl>https://outlook.office365.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=cadcom.us</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=cadcom.us</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=cadcom.us</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=cadcom.us</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=cadcom.us</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=cadcom.us</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=cadcom.us</EcpUrl-photo>
<EcpUrl-connect>Connect/Main.aspx?rfr=olk&exsvurl=1&Provider=<Provider>&Action=<Action>&realm=cadcom.us</EcpUrl-connect>
<EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=cadcom.us</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=cadcom.us</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=cadcom.us</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=cadcom.us</EcpUrl-extinstall>
<ServerExclusiveConnect>On</ServerExclusiveConnect>
</Protocol>
</Account>
</Response>
</Autodiscover>
HTTP Response Headers:
request-id: 443c7500-1216-4307-b195-8d742873d0f0
X-CalculatedBETarget: co1pr04mb474.namprd04.prod.outlook.com
X-DiagInfo: CO1PR04MB474
X-BEServer: CO1PR04MB474
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Set-Cookie: ClientId=JYEVNJSG0UERWBME1PF2A; expires=Wed, 20-Apr-2016 04:40:07 GMT; path=/; secure; HttpOnly,EXOBasicAuth=compactTicket=&key=brandon%40cadcom.us+microsoft.exchange.autodiscover+157.56.138.143+&signature=QJdNVZ9GjQrYkxZg4iXgN8XbU7ZlhTifQyXVjqCwqbBgJL14yiG8oVRxKprB6LXqEBx90YDherBvRURQmGweF+XHW5Eg4gKIhRhSgy6XhMdQslO+PSV1TuZJIHB0g8KcM1MDr4LEuS19bT1HFPpLEUf7A+tmrfTQyy6l21zaUohb/Z0XZUn1o/pkbIcBBSb+tOVAemIsTyHN/p0VbbkA2AeMdVVJIz1wHLW7s9o7fCtJ7cM33Wzz9M6g5k/bNv/NAe9a2nbCZjpyqdmDkKrdmalekhBVkusIskPX5p8aVU8CuiTRtyIcRq8IWxvDhwyH3RiFnyVd5ytNy42M0r7+gQ==&puid=100300008CF2A4C2&expireTime=635651446880000000&membername=brandon%40cadcom.us&flags=False&userType=ManagedBusiness;
expires=Mon, 20-Apr-2015 16:38:08 GMT; path=/Autodiscover; secure; HttpOnly,[email protected]=u56Lnp2ejJqBzc6Znc7OmcjSnpnJzdLLx8qa0sfOyM/Sms7OyMzLyJmbms/HgZyem5yQktGKjIHNz87K0s/K0s3Oq8/LxcvPxc/HgZGeko+Nm8/L0Y+NkJvRkIqLk5CQlNGckJI=;
expires=Thu, 21-May-2015 04:40:08 GMT; path=/Autodiscover; secure; HttpOnly,[email protected]=u56Lnp2ejJqBzc6Znc7OmcjSnpnJzdLLx8qa0sfOyM/Sms7OyMzLyJmbms/HgZyem5yQktGKjIHNz87K0s/K0s3Oq8/LxcvPxc/H; expires=Thu, 21-May-2015 04:40:08 GMT; path=/Autodiscover;
secure; HttpOnly
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
X-FEServer: BY1PR10CA0031
Date: Tue, 21 Apr 2015 04:40:08 GMT
Content-Length: 4345
Elapsed Time: 1525 ms.
The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL
https://autodiscover-s.outlook.com/Autodiscover/Autodiscover.xml for user
[email protected].
The Autodiscover XML response was successfully retrieved.
Additional Details
Autodiscover Account Settings
XML response:
<?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>Brandon Smith</DisplayName>
<LegacyDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon</LegacyDN>
<DeploymentId>5135be05-06e4-4e3b-9cbd-f39b6108647f</DeploymentId>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol>
<Type>EXCH</Type>
<Server>[email protected]</Server>
<ServerDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]</ServerDN>
<ServerVersion>73C18088</ServerVersion>
<MdbDN>/o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/[email protected]/cn=Microsoft Private MDB</MdbDN>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
<OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>
<OABUrl>https://outlook.office365.com/OAB/fb606d0b-79d8-4255-9c7b-552a0fccb72f/</OABUrl>
<UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<AuthPackage>Anonymous</AuthPackage>
<PublicFolderServer>outlook.office365.com</PublicFolderServer>
<EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>
<EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>
<SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>
<EcpUrl>https://outlook.office365.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=cadcom.us</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=cadcom.us</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=cadcom.us</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=cadcom.us</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=cadcom.us</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=cadcom.us</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=cadcom.us</EcpUrl-photo>
<EcpUrl-connect>Connect/Main.aspx?rfr=olk&exsvurl=1&Provider=<Provider>&Action=<Action>&realm=cadcom.us</EcpUrl-connect>
<EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=cadcom.us</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=cadcom.us</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=cadcom.us</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=cadcom.us</EcpUrl-extinstall>
<ServerExclusiveConnect>off</ServerExclusiveConnect>
</Protocol>
<Protocol>
<Type>EXPR</Type>
<Server>outlook.office365.com</Server>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
<OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>
<OABUrl>https://outlook.office365.com/OAB/fb606d0b-79d8-4255-9c7b-552a0fccb72f/</OABUrl>
<UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>On</SSL>
<AuthPackage>Basic</AuthPackage>
<CertPrincipalName>msstd:outlook.com</CertPrincipalName>
<EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>
<EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>
<SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>
<EcpUrl>https://outlook.office365.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=cadcom.us</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=cadcom.us</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=cadcom.us</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=cadcom.us</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=cadcom.us</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=cadcom.us</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=cadcom.us</EcpUrl-photo>
<EcpUrl-connect>Connect/Main.aspx?rfr=olk&exsvurl=1&Provider=<Provider>&Action=<Action>&realm=cadcom.us</EcpUrl-connect>
<EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=cadcom.us</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=cadcom.us</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=cadcom.us</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=cadcom.us</EcpUrl-extinstall>
<ServerExclusiveConnect>on</ServerExclusiveConnect>
<EwsPartnerUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsPartnerUrl>
<GroupingInformation>CO1PR04</GroupingInformation>
</Protocol>
<Protocol>
<Type>WEB</Type>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<Internal>
<OWAUrl AuthenticationMethod="LiveIdFba, OAuth">https://outlook.office365.com/owa/</OWAUrl>
<Protocol>
<Type>EXCH</Type>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
</Protocol>
</Internal>
<External>
<OWAUrl AuthenticationMethod="Fba">https://outlook.office365.com/owa/cadcom.us/</OWAUrl>
<Protocol>
<Type>EXPR</Type>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
</Protocol>
</External>
</Protocol>
<Protocol>
<Type>EXHTTP</Type>
<Server>outlook.office365.com</Server>
<ASUrl>https://outlook.office365.com/EWS/Exchange.asmx</ASUrl>
<OOFUrl>https://outlook.office365.com/EWS/Exchange.asmx</OOFUrl>
<OABUrl>https://outlook.office365.com/OAB/fb606d0b-79d8-4255-9c7b-552a0fccb72f/</OABUrl>
<UMUrl>https://outlook.office365.com/EWS/UM2007Legacy.asmx</UMUrl>
<Port>0</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>On</SSL>
<AuthPackage>Basic</AuthPackage>
<CertPrincipalName>msstd:outlook.com</CertPrincipalName>
<EwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EwsUrl>
<EmwsUrl>https://outlook.office365.com/EWS/Exchange.asmx</EmwsUrl>
<SharingUrl>https://outlook.office365.com/EWS/Exchange.asmx</SharingUrl>
<EcpUrl>https://outlook.office365.com/ecp/</EcpUrl>
<EcpUrl-um>?rfr=olk&p=customize/voicemail.aspx&exsvurl=1&realm=cadcom.us</EcpUrl-um>
<EcpUrl-aggr>?rfr=olk&p=personalsettings/EmailSubscriptions.slab&exsvurl=1&realm=cadcom.us</EcpUrl-aggr>
<EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?rfr=olk&exsvurl=1&IsOWA=<IsOWA>&MsgID=<MsgID>&Mbx=<Mbx>&realm=cadcom.us</EcpUrl-mt>
<EcpUrl-ret>?rfr=olk&p=organize/retentionpolicytags.slab&exsvurl=1&realm=cadcom.us</EcpUrl-ret>
<EcpUrl-sms>?rfr=olk&p=sms/textmessaging.slab&exsvurl=1&realm=cadcom.us</EcpUrl-sms>
<EcpUrl-publish>customize/calendarpublishing.slab?rfr=olk&exsvurl=1&FldID=<FldID>&realm=cadcom.us</EcpUrl-publish>
<EcpUrl-photo>PersonalSettings/EditAccount.aspx?rfr=olk&chgPhoto=1&exsvurl=1&realm=cadcom.us</EcpUrl-photo>
<EcpUrl-connect>Connect/Main.aspx?rfr=olk&exsvurl=1&Provider=<Provider>&Action=<Action>&realm=cadcom.us</EcpUrl-connect>
<EcpUrl-tm>?rfr=olk&ftr=TeamMailbox&exsvurl=1&realm=cadcom.us</EcpUrl-tm>
<EcpUrl-tmCreating>?rfr=olk&ftr=TeamMailboxCreating&SPUrl=<SPUrl>&Title=<Title>&SPTMAppUrl=<SPTMAppUrl>&exsvurl=1&realm=cadcom.us</EcpUrl-tmCreating>
<EcpUrl-tmEditing>?rfr=olk&ftr=TeamMailboxEditing&Id=<Id>&exsvurl=1&realm=cadcom.us</EcpUrl-tmEditing>
<EcpUrl-extinstall>Extension/InstalledExtensions.slab?rfr=olk&exsvurl=1&realm=cadcom.us</EcpUrl-extinstall>
<ServerExclusiveConnect>On</ServerExclusiveConnect>
</Protocol>
</Account>
</Response>
</Autodiscover>
HTTP Response Headers:
request-id: 4412d758-013f-4700-bde1-06dc5e66bf6d
X-CalculatedBETarget: co1pr04mb474.namprd04.prod.outlook.com
X-DiagInfo: CO1PR04MB474
X-BEServer: CO1PR04MB474
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Set-Cookie: ClientId=YVWYC2UW3EAOSJXJYJDCDW; expires=Wed, 20-Apr-2016 04:40:08 GMT; path=/; secure; HttpOnly,[email protected]=u56Lnp2ejJqBzc6Znc7OmcjSnpnJzdLLx8qa0sfOyM/Sms7OyMzLyJmbms/HgZyem5yQktGKjIHNz87K0s/K0s3Oq8/LxcvPxc/HgZGeko+Nm8/L0Y+NkJvRkIqLk5CQlNGckJI=;
expires=Thu, 21-May-2015 04:40:08 GMT; path=/Autodiscover; secure; HttpOnly,[email protected]=u56Lnp2ejJqBzc6Znc7OmcjSnpnJzdLLx8qa0sfOyM/Sms7OyMzLyJmbms/HgZyem5yQktGKjIHNz87K0s/K0s3Oq8/LxcvPxc/H; expires=Thu, 21-May-2015 04:40:08 GMT; path=/Autodiscover;
secure; HttpOnly
Server: Microsoft-IIS/8.0
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
X-FEServer: BY1PR10CA0031
Date: Tue, 21 Apr 2015 04:40:08 GMT
Content-Length: 9631
Elapsed Time: 301 ms.
Autodiscover settings for Outlook connectivity are being validated.
The Microsoft Connectivity Analyzer validated the Outlook Autodiscover settings.
Additional Details
Elapsed Time: 0 ms.
Testing MAPI over HTTP connectivity to server outlook.office365.com
MAPI over HTTP connectivity was verified successfully.
Additional Details
HTTP Response Headers:
request-id: 2931fc03-73eb-4bb0-8ffc-34b9445369ed
X-FEServer: BY2PR09CA0048
Content-Length: 0
Date: Tue, 21 Apr 2015 04:40:08 GMT
Set-Cookie: ClientId=ZZCG7DWJLKIDNUIKMHP0Q; expires=Wed, 20-Apr-2016 04:40:09 GMT; path=/; secure; HttpOnly
Server: Microsoft-IIS/8.0
WWW-Authenticate: Basic Realm=""
X-Powered-By: ASP.NET
Elapsed Time: 3246 ms.
Test Steps
Attempting to resolve the host name outlook.office365.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 132.245.24.82, 132.245.92.34, 132.245.92.194, 132.245.80.146, 157.56.239.194, 132.245.64.146, 2a01:111:f400:2c40::2, 2a01:111:f400:5000::2, 2a01:111:f400:1414::2, 2a01:111:f400:2c2c::2, 2a01:111:f400:1428::2, 2a01:111:f400:4c32::2
Elapsed Time: 152 ms.
Testing TCP port 443 on host outlook.office365.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 70 ms.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Additional Details
Elapsed Time: 251 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server outlook.office365.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US, Issuer: CN=Microsoft IT SSL SHA1, OU=Microsoft IT, O=Microsoft Corporation, L=Redmond, S=Washington, C=US.
Elapsed Time: 141 ms.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name outlook.office365.com was found in the Certificate Subject Alternative Name entry.
Elapsed Time: 3 ms.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US.
One or more certificate chains were constructed successfully.
Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE.
Elapsed Time: 34 ms.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Elapsed Time: 6 ms.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 2/13/2015 12:38:15 AM, NotAfter = 2/13/2016 12:38:15 AM
Elapsed Time: 0 ms.
Testing HTTP Authentication Methods for URL
https://outlook.office365.com/mapi/emsmdb/[email protected].
The HTTP authentication methods are correct.
Additional Details
The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Basic
HTTP Response Headers:
request-id: 2931fc03-73eb-4bb0-8ffc-34b9445369ed
X-FEServer: BY2PR09CA0048
Content-Length: 0
Date: Tue, 21 Apr 2015 04:40:08 GMT
Set-Cookie: ClientId=ZZCG7DWJLKIDNUIKMHP0Q; expires=Wed, 20-Apr-2016 04:40:09 GMT; path=/; secure; HttpOnly
Server: Microsoft-IIS/8.0
WWW-Authenticate: Basic Realm=""
X-Powered-By: ASP.NET
Elapsed Time: 190 ms.
Testing the MAPI Address Book endpoint on the Exchange server.
The address book endpoint was tested successfully.
Additional Details
Elapsed Time: 1987 ms.
Test Steps
Testing the address book "Check Name" operation for user
[email protected] against server outlook.office365.com.
Check Name succeeded.
Additional Details
DisplayName: Brandon Smith, LegDN: /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon
Elapsed Time: 1987 ms.
Testing the MAPI Mail Store endpoint on the Exchange server.
We successfully tested the Mail Store endpoint.
Additional Details
Elapsed Time: 594 ms.
Test Steps
Attempting to log on to the Mailbox.
We were able to log on to the Mailbox.
Additional Details
Elapsed Time: 594 ms.
Testing RPC over HTTP connectivity to server outlook.office365.com
RPC over HTTP connectivity was verified successfully.
Additional Details
HTTP Response Headers:
request-id: 64e2bf62-0b20-4e36-912d-005c7a017fb4
X-DiagInfo: BY2PR09CA0048
X-FEServer: BY2PR09CA0048
Content-Length: 0
Date: Tue, 21 Apr 2015 04:40:11 GMT
Set-Cookie: ClientId=SKGVNJCDX0OA7M7QPJFWLA; expires=Wed, 20-Apr-2016 04:40:12 GMT; path=/; secure; HttpOnly
Server: Microsoft-IIS/8.0
WWW-Authenticate: Basic Realm=""
X-Powered-By: ASP.NET
Elapsed Time: 25606 ms.
Test Steps
Attempting to resolve the host name outlook.office365.com in DNS.
The host name resolved successfully.
Additional Details
IP addresses returned: 132.245.24.82, 132.245.92.34, 132.245.92.194, 132.245.80.146, 157.56.239.194, 132.245.64.146, 2a01:111:f400:2c40::2, 2a01:111:f400:5000::2, 2a01:111:f400:1414::2, 2a01:111:f400:2c2c::2, 2a01:111:f400:1428::2, 2a01:111:f400:4c32::2
Elapsed Time: 42 ms.
Testing TCP port 443 on host outlook.office365.com to ensure it's listening and open.
The port was opened successfully.
Additional Details
Elapsed Time: 61 ms.
Testing the SSL certificate to make sure it's valid.
The certificate passed all validation requirements.
Additional Details
Elapsed Time: 223 ms.
Test Steps
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server outlook.office365.com on port 443.
The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
Additional Details
Remote Certificate Subject: CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US, Issuer: CN=Microsoft IT SSL SHA1, OU=Microsoft IT, O=Microsoft Corporation, L=Redmond, S=Washington, C=US.
Elapsed Time: 121 ms.
Validating the certificate name.
The certificate name was validated successfully.
Additional Details
Host name outlook.office365.com was found in the Certificate Subject Alternative Name entry.
Elapsed Time: 1 ms.
Certificate trust is being validated.
The certificate is trusted and all certificates are present in the chain.
Test Steps
The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=outlook.com, OU=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=WA, C=US.
One or more certificate chains were constructed successfully.
Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate CN=Baltimore CyberTrust Root, OU=CyberTrust, O=Baltimore, C=IE.
Elapsed Time: 36 ms.
Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Elapsed Time: 5 ms.
Testing the certificate date to confirm the certificate is valid.
Date validation passed. The certificate hasn't expired.
Additional Details
The certificate is valid. NotBefore = 2/13/2015 12:38:15 AM, NotAfter = 2/13/2016 12:38:15 AM
Elapsed Time: 0 ms.
Checking the IIS configuration for client certificate authentication.
Client certificate authentication wasn't detected.
Additional Details
Accept/Require Client Certificates isn't configured.
Elapsed Time: 173 ms.
Testing HTTP Authentication Methods for URL
https://outlook.office365.com/rpc/[email protected]:6002.
The HTTP authentication methods are correct.
Additional Details
The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Basic
HTTP Response Headers:
request-id: 64e2bf62-0b20-4e36-912d-005c7a017fb4
X-DiagInfo: BY2PR09CA0048
X-FEServer: BY2PR09CA0048
Content-Length: 0
Date: Tue, 21 Apr 2015 04:40:11 GMT
Set-Cookie: ClientId=SKGVNJCDX0OA7M7QPJFWLA; expires=Wed, 20-Apr-2016 04:40:12 GMT; path=/; secure; HttpOnly
Server: Microsoft-IIS/8.0
WWW-Authenticate: Basic Realm=""
X-Powered-By: ASP.NET
Elapsed Time: 27 ms.
Attempting to ping RPC proxy outlook.office365.com.
RPC Proxy was pinged successfully.
Additional Details
Elapsed Time: 2099 ms.
Attempting to ping the MAPI Mail Store endpoint with identity:
[email protected]:6001.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 47 ms.
Elapsed Time: 5049 ms.
Testing the MAPI Address Book endpoint on the Exchange server.
The address book endpoint was tested successfully.
Additional Details
Elapsed Time: 6447 ms.
Test Steps
Attempting to ping the MAPI Address Book endpoint with identity:
[email protected]:6004.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 218 ms.
Elapsed Time: 4230 ms.
Testing the address book "Check Name" operation for user
[email protected] against server
[email protected].
Check Name succeeded.
Additional Details
DisplayName: Brandon Smith, LegDN: /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon
Elapsed Time: 2216 ms.
Testing the MAPI Referral service on the Exchange Server.
The Referral service was tested successfully.
Additional Details
Elapsed Time: 6271 ms.
Test Steps
Attempting to ping the MAPI Referral Service endpoint with identity:
[email protected]:6002.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 640 ms.
Elapsed Time: 4630 ms.
Attempting to perform referral for user /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon on server
[email protected].
We got the address book server successfully.
Additional Details
The server returned by the Referral service:
[email protected]
Elapsed Time: 1640 ms.
Testing the MAPI Address Book endpoint on the Exchange server.
The address book endpoint was tested successfully.
Additional Details
Elapsed Time: 923 ms.
Test Steps
Attempting to ping the MAPI Address Book endpoint with identity:
[email protected]:6004.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 62 ms.
Elapsed Time: 72 ms.
Testing the address book "Check Name" operation for user
[email protected] against server
[email protected].
Check Name succeeded.
Additional Details
DisplayName: Brandon Smith, LegDN: /o=ExchangeLabs/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=eec65d660c084484bbca3f80e1a10e9a-brandon
Elapsed Time: 851 ms.
Testing the MAPI Mail Store endpoint on the Exchange server.
We successfully tested the Mail Store endpoint.
Additional Details
Elapsed Time: 4286 ms.
Test Steps
Attempting to ping the MAPI Mail Store endpoint with identity:
[email protected]:6001.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 656 ms.
Elapsed Time: 3656 ms.
Attempting to log on to the Mailbox.
We were able to log on to the Mailbox.
Additional Details
Elapsed Time: 628 ms.
=============================================================================

Project Online Task Sync with Exchange Online

We have Project Online and Exchange Online subscriptions both part of same tenant.
When we go to Tasks in Project Online and try to set up a syn with outlook, we get below error:
Status:
We weren't able to sync your tasks. This could be because your mailbox is on an Exchange server that isn't supported for syncing tasks. Please contact your administrator for more help.
TECHNICAL
DETAILS
Troubleshoot issues with Microsoft SharePoint Foundation.
Correlation ID: 2213909c-7d3d-f01c-8181-67dfe90b5007
Date and Time: 5/11/2014 11:01:14 PM
Can someone please help as there is very little room for troubleshooting as mentioned this feature should work out of box.
Abhijeet, MCTS | [email protected]

What version of Outlook do you use? I don't think this works for Outlook 2010, I believe it needs to be Outlook 2013.
Paul
Paul Mather | Twitter |
http://pwmather.wordpress.com | CPS

Migrating 122GB mailbox to Exchange Online

Hi all,
I'm attempting to migrate a 122GB journal from a decommissioned on premise exchange (SBS2008 - Exchange 2007)
Using a 32 bit Windows 7 machine with Outlook 2007
So far, I've attempted to use Export-Mailbox -Identity journal -PSTFolderPath
E:\drive\journal.pst
After a week of it sat exporting, it eventually failed with an error regarding too many corrupt messages
On my second attempt, I added the flag of -BadItemLimited 1000 and it sat for a week
Approving Object
I think next I will, create a new mailstore and move it across and try and export from that..
Failing that, specify export by date?
Does anybody have any suggestions/tips/instructions on how to move a mailbox of that size?
Thanks

Hi,
As far as I know, Resource Mailboxes (Room, Shared, Equipment) is moved between on-premise Exchange servers in the exact same way as User Mailboxes:
http://social.technet.microsoft.com/Forums/exchange/en-US/f60d736d-0d45-4c27-adc8-a7e04afdb6e3/resource-mailboxes-and-contacts-move-during-transition-to-exchange-2013?forum=exchangesvrdeploy
Based on my research, there is nothing special for resource mailboxes in the transition from on-premise to Exchange online:
http://technet.microsoft.com/en-us/library/jj898486(v=exchg.150).aspx
And you’re welcomed to confirm it on our Exchange online forum:
http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Problem in configuring my mobile device with exchange online account

I am facing problem in mobile configuration. I have Iphone 5 mobile device and i am going to configure exchange online account to this device .
when i am putting my email id and password ,the error message comes "cannot verify your account information".
so help me to configure my mobile .
Even i am trying to configure my android device with exchange account .
In that also is not going to be configure.

Hi,
Please check this link and follow the guide to configure exchange online account to your IPhone:
https://support.office.com/en-SG/Article/Set-up-email-on-Apple-iPhone-iPad-and-iPod-Touch-b2de2161-cc1d-49ef-9ef9-81acd1c8e234
Since this forum is for general questions and feedback related to Office for windows, if you need further assistance on this issue, you can post in the following forum:
https://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
The reason why we recommend posting appropriately is you will get the most
qualified pool
of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Monitoring many mailboxes in Exchange OnLine

Hi
I'm developing a large-scaled Exchange calendar synchronization application using EWS Managed API 2.1.
When Microsoft upgraded the Exchange OnLine platform to Exchange 2013 I had to re-write some of the code in order to adapt to the new behavior of the CAS (e.g. subscription groups and GroupingInformation).
Typically our customers have 4000-5000 mailboxes that we have to monitor but some of them have 20.0000 or more. As the trend is that also large companies are moving their Exchange to the cloud I often get questions from sales about how many calendars
we can monitor for changes.
So, now to my question;
Is there any absolute limit for how many mailboxes that can be monitored in Exchange OnLine?
I'm using EWS Managed API 2.1, utilizing Autodiscover, Impersonation, Streaming Notifications and subscription groups (200 subscriptions each). I'm aware of that throttling limits will be reached from time to time and that I have to handle them as they occur.
Best Regards
Jens
Jens Eriksson TalkIT Communication AB

Hi CCStefanonni,
If you delete a user account or remove a license from a user, mailbox will be permanently deleted after 30days. Since you are in Midsize Business plan you don't have in-place hold to keep inactive user data for more than 60 days. As I see, you have two options,
Convert the user mailbox to a Shared Mailbox. Keep in mind shared mailboxes are only 5GB in size.
Download the PST and keep it somewhere safe (ex: one drive). You can upload the PST through the shell or though Outlook later if needed.
Thanks

Outlook 2011 with Exchange Online

I have just subscribed to Exchange Online, and use Outlook 2011 for Mac as client. Email send/receive is working. However, Contacts and Notes on my Outlook don't sync with Exchange.

Hi,
Since Exchange Online is different from Exchange 2013, I suggest asking Exchange Online Forum for help so that we can get more professional suggestions.
For your convenience:
http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
Also post a thread on Outlook 2011 for Mac Forum:
http://answers.microsoft.com/en-us/mac/forum/macoutlook?tab=Threads
However I also found a KB for your reference:
How to sync calendars in Outlook for Mac 2011
http://support.microsoft.com/kb/2452489/en-us
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

TLS with Exchange Online

If we enable Forced TLS with a business partner and TLS connection fails, will the sender of emails get a NDR in Exchange Online?
MP

Thanks.
MP

Script Powershell In Place Hold Mailbox with Exchange 2010

Hello,
I have a script that allows me to make a InPlaceHold newly created mailboxes via Exchange 2010.
But every time I run, he released me an error message: See attached picture.
Here is the script in question:
#Initialize variables
$policyname = "In Place - Hold"
$members = Import-CSV "C:\migration\Script\New_User\New_User_List.csv" -delimiter ";"
$Result = "C:\migration\Script\New_User\New_User_Result.log"
$powerUser = "******"
$powerPass = "******"
$password = ConvertTo-SecureString $powerPass -AsPlainText -Force
$adminCredential = New-Object -TypeName System.Management.Automation.PSCredential -argumentlist $powerUser,$password
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://outlook.office365.com/powershell-liveid/ -Credential $adminCredential -Authentication Basic -AllowRedirection
Import-PSSession $Session
#Get current mailboxes in our mailbox search
$InPlaceHoldMailboxes = (Get-MailboxSearch $policyname).sourceMailboxes
#Add another user to the array, the line bellow can be a loop of more than one user.
foreach ( $member in $members)
if ($InPlaceHoldMailboxes -contains($member.name))
Write-Host $("User " + $member.name + " already present") -ForegroundColor:yellow
Out-File -FilePath $Result -InputObject $("IN-PLACE HOLD - WARNING, User " + $member.name + " already present in members") -Encoding UTF8 -append
else
$InPlaceHoldMailboxes += $member.upn
Write-Host $("User " + $member.name + " added") -ForegroundColor:green
Out-File -FilePath $Result -InputObject $("IN-PLACE HOLD - SUCCESS, User " + $member.name + " added to members") -Encoding UTF8 -append
#Add them to the MailboxSearch
Try
Set-MailboxSearch $policyname -SourceMailboxes $InPlaceHoldMailboxes -Force -ErrorAction 'Stop'
Write-Host $("SUCCESS, " + $policyname + " updated") -ForegroundColor:green
Out-File -FilePath $Result -InputObject $("IN-PLACE HOLD - SUCCESS, " + $policyname + " updated") -Encoding UTF8 -append
Catch
Write-Host $("ERROR, policie " + $policyname + " NOT updated") -ForegroundColor:red
Out-File -FilePath $Result -InputObject $("IN-PLACE HOLD - ERROR, " + $policyname + " NOT updated") -Encoding UTF8 -append
Write-Error $_.Exception.ToString() > $Result
Exit
#start the mailboxsearch
Start-MailboxSearch -Identity $policyname -Force
Remove-PSSession $Session
I use Powershell 4.0
Thank you for your help.

Please read the error message carefully as it tells you what is wrong. "You cannot update multiple mailboxes". You must do one at a time.
¯\_(ツ)_/¯

Connect to Exchange 2007 Mailboxes with Exchange 2013 Management shell

Hello,
I was wondering if it is possible to use the Exchange 2013 Management Shell with the older version of Exchange 2007. When I run the console now it give me an error saying no exchange servers are available in the Active Directory site. When I use Exchange
management shell for 2007 the errors do not appear. Wondering if the management shell is backwards compatible.
Thanks,

No. your management shell MUST be the same roll-up version of exchange. I have applied updates and learned the hard way to block all updates that go beyond the server version you are
running.
http://social.technet.microsoft.com/wiki/contents/articles/240.exchange-server-and-update-rollup-bui...
To this end, you can use the same installation media that was used to install your Exchange server "Provided you are hosting your own", just install the management console instead of the whole thing,

Decomission Exchange Server in Hybrid Deployment with Exchange online

Referencing tech net article titled: Decommissioning your Exchange 2010 servers in a Hybrid Deployment ( I am not able to link to it due for some reason)
I was also not able to comment directly on the article, would appreciate if the author or someone in the know could kindly review my comment/question below and provide feedback:
So as I understand it if we used Hybrid mode as our method to migrate to O365 we must now keep an aging onPremise exchange server for time eternal? This is not practical or sustainable as the whole point of going to O365 was to get rid of our old Exchange
server. Now we have to keep and maintain expensive hardware and keep windows patched and maintained etc, all the tasks we thought we were moving away from with this migration. What happens when Exchange 2010 reaches EOL? Do we then have to
upgrade a server we are not really using?
Please tell me there is an update to this article or an update in the works with a more sustainable solution to cut ties with old on-prem Exchange servers after migrating to O365. Is there an update or something in the works? Is there anyway
I can speak to someone on this in more detail to better understand the details to the downsides listed in this article? We very much want to shutdown our on prem server ASAP as we are shutting down our datacenter since moving to O365 and this is the
only kink hold us back.
Thanks.

If you have the infrastructure, you could move to a virtual server, and upgrade to Exchange 2013. There is a free license for Exchange 2013 when used hybrid server.
https://support.microsoft.com/kb/2939261?wa=wsignin1.0
I have to admit to being slightly confused about the conditions for obtaining the hybrid license as it says you can't already have a licensed Exchange server. So what do you do if you had Exchange and then migrated to Office 365 rather than created
the hybrid initially?
CRM Advisor

Site mailboxes with Exchange Online?

Similar Messages

Maybe you are looking for