Check this out for how to use https://mspoweruser.com/schedule-an-email-send-later-outlook-web/
Also, borrowing one of these images without permission. Thank you.
OWA is…well, to be frank, garbage, for those of us forced to use it because…well…whatever, but let’s say that your IT overlords have seen fit to NOT BOTHER fixing the problems with your tenancy, even if it were a simple call to THEIR overlords at Mickeysoft preventing an actual Outlook client from working in many of your workday scenarios. Among the mind-bogglingly idiotic discrepancies is the aggregated “Unread Items”. If you’re of a certain age, certainly, but even if not, you probably sort your email into folders for ease of finding later, etc. You probably have rules for helping with that, especially if you get auto-generated services messages that you want to have/keep/read when pertinent, but that do NOT need to be in your Inbox. How can you see these in OWA? Go digging. And good luck. And I’m sorry, Microsoft, but “conversations” is unwieldy at best, and search/filter from the inbox is equally useless. Seriously. Searching for an email that I have pulled up in one client, on another computer sitting on the same tabletop in OWA and it can’t be found. WTF?!?
Wait. Why were we here again?
Oh yeah. Another exploitable bug feature of Desktop Lookout that until June 2020 or so was not available in OWA is delayed send. In a rare move, though, M$ actually made this one BETTER because it’s server-side. That means you can set the send time to a point in the future, and walk away, and the server will send your message at the appointed time (y’know, assuming everything works as-planned – a stretch, I know). On the desktop version, this is still client-side, meaning you have to have your computer turned on and the Outlook client has to be loaded. Otherwise, the server will simply ignore the future-send request once it becomes current, because it knows nothing about it. Very frustrating for those of us who became accustomed to building time-sensitive emails over a period of time, expecting the “send at” to trigger that send at the appointed time regardless of our being logged into a computer at all, because SOME vendors had the sense to make this server-side, as it should be and always have been, unlike M$ who, bafflingly, decided this needed to be client dependent. So what’s to know? Why am I here, instead of just pointing you to Pradeep’s post about Mike’s post? Here is the interface for the new bug feature:
Why did I feel the need to make a post, to remind myself sometime in the future about something I probably already know (but perhaps can’t remember just this moment)?
Here’s my screen:
So…where IS my pulldown? I can see it in the “Attach” button, but nada on the “Send” button… I guess my tenancy has not, five months hither, been granted this glorious functionality…
Of course there’s a “gotcha”. And in a way that only Microsoft seems capable of doing, they exploit what is obviously a failure on my part, but in the most irritating way. I have NEVER used the OTHER send button. In fact, I did not even realize until today that there are multiple send buttons. I just use the one that is obvious. As encircled above. It turns out, if you look carefully, there is another at the bottom of the window.
Here, you will find the pulldown arrow, and can then schedule your email to send at some point in the future, whether your computer is on or not; whether you are logged in or not; whether your Lookout client is running or not. Ah. A small bit of relief in the sea of suck that is using OWA.
Thank you, Microsoft, for finally adding this feature to your bugfeature list.
This is pretty funny, and warrants more research. I cannot save this post to WordPress using a category of Microsoft with subcategory of Lookout.
sypak 