How can I set up my mail app to connect with Exchange.

Does not work for me. I cannot get the Outlook to connect to the Exchange Server. Any ideas?

Split from this thread.

I am having the same problem. I have tried to remove the profiles and enter the corrected profiles.

That did not work for me. So, I went the Microsoft store and no one there could get it to work either. (Their suggestion was to use on the Mail app, forget about Outlook - some help that was! I have connected to the Exchange on my Kindle, so I know it should work.

Hello, RobertHedrick

     Many of us tend to forget the widely-disparate audiences that tablets and Exchange Server are targeted towards.  Exchange Server is first and foremost a product for enterprise applications, where implementation is geared towards the secure storage and manipulation of data for companies with legal

and/or fiduciary responsibilities to ensure such security in their business practives; like all NT Kernel-derived systems, Exchange is designed to comply with the parameters of the C2 Security model

• which originated in a Department of Defense requirement for secure battlefield communication in the event of nuclear war.  Security, in the form of client/object authentication as a prerequisite to the server delivering requested data in the form of information or services or whatever, is the prime consideration for such a system.  ARM-based (reduced instruction set computing) systems such as most tablet computers (the Surface Pro being amongst the notable exceptions) are largely intended for consumer use in viewing online-published content (The relative merits of Mark Penn's marketing approach may be debated, but there's actually a quite good reason those Surface tv commercials featured folks dancing around with their tablets, to all appearances more appropo of a Busby Berkely musical of yore or some other light-hearted endeavor unlikely to be found in a modern business - the implied office environment notwithstanding.)  The two technologies do not therefore share a common underpinning in a concurrent embrace of security best practices - in fact, the latter is distinctly inimicable to such, for the reasons you and so many other posters to this and similar Community threads point out: security compliance is simply not easy to effect, or convenient, and convenience/ease of use is of course a prime consideration for folks investing in tablet computers.  Nevertheless, getting to such a state of convenience in the interaction between a consumer-oriented tablet computer and a business-oriented Exchange server frequently requires that some inconvenient work be performed as a first prerequisite.

     The relative merits of the current embrace of BYOD policies (with their obvious implications of accessibility to a company's secure data) may be debated, but there's no denying the advance of such an embrace, and Microsoft has provided the capabilities to implement these policies in their server products for some time now (for instance, in each of the last four versions of Exchange Server: 2003, 2007, 2010, and 2013) - but they don't neccessarily make such capability easy to implement, certainly not by default configurations, in the interests of the prime consideration of C2-compliant servers: security.  Manufacturers of mobile devices - Microsoft included - have not always helped in virtue of the underlying design of their products; some are provisionable (i.e., as far as this discussion is concerned, capable of enforcing the security policies used by EAS/OWA/etc.), and some are not.  However, once the due consideration of security-compromising implications has been reviewed and a policy approach formulated to address such concerns implemented, proper configurations may be put in place and users allocated the proper credentialing mechanisms to allow trouble-free access.

     The apparent intermittent nature of your ability to connect would seem to belie the possibility that your particular problem is due to improper/insufficient configuration, but I've seen many similar instances where more-or-less superficial information concerning an actual configuration scenario implied the same, only to have further, more in-depth examination of the case's parameters (these are many, and complex; an oft-overlooked problem I see is incorrect or ill-deployed Client Access Licensing, for instance) reveal that such was indeed the case.  In the light of this, might I suggest it might be a good idea to have your IT support personnel review the appropriate documentation for your Exchange Server installation and verify there's nothing amiss in terms of accessibility configuration or the like?  The TechNet articles "Client Access Role" (for Exchange Server 2007), "Understanding Client Access" (for 2010), or "Clients and Mobile" (for 2013) are guidelines I'd probably start with in such a situation.  As I stated in my reply to an earlier poster to this thread, I find there's good "overview" information, quite applicable in many ways to Surface RT, in the Microsoft Exchange Team Blog "Supporting Windows 8 Mail in your organization".

     I hope this information helps you get the enjoyment of your product's features and capabilities that all purchasers deserve.  Good Luck!

Hi Steve,

I am able to use my corporate email (Exchange Active Sync) on my Windows Phone (NL 920) but I cannot get it to work on my Surface 2. I have installed the same certificates (Root certificate provided by work and Personal certificate which is self generated) on my Surface but it keeps telling me: To connect to this account you need a valid certificate on this PC. I have browsed the internet for hours and tried several suggestions but it just does not work.

Any idea's?

Regards,

Sander

Hello, Sander Verbrugge 

    The Microsoft KB2784275 article "How to configure an Exchange account and how to troubleshoot Exchange account connectivity issues in the Mail app in Windows 8 and Windows RT" clearly explains why administrative privileges are required to install a Self-signed certificate, but is perhaps somewhat ambiguous on how to actually effect this for the average user - who may or may not be aware of how to actually perform this on a Surface running Windows 8, or even how to elevate a standard user profile's via the "Run as Administrator" option.  The Lone C++ Coder's Blog post "How to make a self-signed SSL certificate work with Windows RT's Mail App on a Microsoft Surface RT" may prove useful in both respects.

     Additional info can be found in the Exchange Team Blog "Supporting Windows 8 Mail in your organization".