This was available with Lync 2010/OWA integration, but Lync 2013 integration requires manually editing the web.config in Exchange.
The ability to save signatures centrally (in the users mailbox) and not in the local profile. Saves a configuration step for users/admins and makes it possible for the user to use the exact same signatures in OWA, EAS, etc. etc..
An app like the OWA App for iPhone/iPad, but now for Android devices. No need for ActiveSync and all it's troubles that come with it (for instance: SD encryption sometimes formats the SD with loss of data) and no worries about a complete remote wipe (potentially wiping personal data).
An app like the OWA App for iPhone/iPad, but now for Windows Phone devices. No need for ActiveSync and no worries about a complete remote wipe (potentially wiping personal data).
It also allows for a more Premium experience on WP, compared to the native ActiveSync implementation.
Pre-filled FROM: dropdown listbox in mail composition form (also OWA), using info from delegated / shared mailboxes a.o. (Send-As) to populate. More end-user friendly than typing in the 'from' address (once) or picking entry from GAL (when shown).
Right now, if you enable the client side auto archiving in Outlook, and have multiple accounts configured in Outlook, all messages from all accounts are archived into the same .pst file. This should not be the case.
Each email account configured in Outlook should have separate S/MIME configuration. Right now, if you configure Outlook with an S/MIME cert on one account, and set it auto encrypt, it applies those settings to all email accounts, even those you don't have an S/MIME cert for.
You can set the AutoMapping feature when adding individual users to Shared Mailboxes.
However, this facility is not available for Security Groups.
A lot of organisations tend to link Security Groups to Shared Mailboxes as part of their designs, which is frustrating when AutoMapping doesn't work.
Would be good to solve this MS.
Request to have public folders automatically displayed in OWA based on user's permission settings instead of manually having to add as favorites.
When a cloud user logs into the on-premise OWA URL in a hybrid deployment, the user is prompted with the "Use the following link to open this mailbox..." prompt and a link to the Office 365 OWA interface. In the interest of providing the most seamless integration for hybrid organizations, it would be nice for the option exist to make this a silent redirection so both on-premise and cloud users can utilize the same URL.... more »
I doubt you'll find an organization that has intentionally chosen to force their users to go to "https://mail.company.com/owa"; nearly everyone wants the "simple URL" of "http://mail.company.com". Instead of publishing a lengthy process for simplifying the URL (http://technet.microsoft.com/en-us/library/aa998359(v=exchg.150).aspx) or having consultants simplify it their own way through one of the many other methods,... more »
Message Recall almost never works and the recall and replace works ok. Anything to improve these features would be welcomed by end users.
We would like more of our users to be using OWA instead of the full Outlook client but there are a few things missing in OWA. Setting OWA as the default mail client is one of them so that when a user clicks on a mailto: link on a webpage it will allow them to sign in to their OWA account and send the email instead of giving them the "there is no default mail client configured".
The ability to recall messages (which doesn't always work but at least they could try).