Microsoft Exchange Online

Main articles:

• E-mail (e-mail)
• SaaS - History. Philosophy. Drivers of development

2020: Adding of function of the disposable e-mail addresses

Microsoft implemented function of the disposable e-mail addresses in Exchange Online. It became known on October 28, 2020.

Users of Microsoft Office 365 can use without restrictions the disposable e-mail addresses of receivers in service of e-mail Exchange Online now.

The Plus Addressing function (also known as subaddressing or detailed addressing) allows to create an unlimited number of the unique e-mail addresses by adding to the normal e-mail address of a suffix using a divider "+" (a user name + suffiks@domen).

The Microsoft company announced this function in 2019, and its deployment began in September, 2020. According to the website Microsoft UserVoice before becoming function by default in Exchange Online, Plus Addressing was one of the most required functions.

All letters coming to dynamically created e-mail address will be automatically readdressed on the main mailbox. It will simplify process of filtering of letters and tracking of senders.

Gives the following scenario as an example of Microsoft: using this function the employee of Northwind company Kim Eykers can create the address kimakers+northwind@contoso.com and subscribe to newsletter of corporate news. When Northwind sends the letter to this address, it will be automatically readdressed on the key address of kimakers@contoso.com. Kim can create the rule for entering that all letters coming to this address went to the Northwind folder.

The Plus Addressing function in Exchange Online is by default turned off. In order that to activate it, it is necessary to be connected to Exchange Online PowerShell and to start the Set-OrganizationConfig PowerShell-command - AllowPlusAddressInRecipients of $true.

For October, 2020 support of function extends only to mailboxes, and support of mailing lists and groups is expected in December, 2020^[1].

2019: Global failure

On January 24, 2019 there was a failure in work of Microsoft Exchange Online as a result of which this service of e-mail stopped being is available to users.

We found out that a part of infrastructure of the controller of domains does not answer that it leads users to connection waiting. We optimize communication with operable infrastructure, repairing the non-working domain controller, says which Microsoft sent to the clients.

The message of Microsoft about failure of Exchange Online which was received by the Russian corporate clients

Added to the companies that the problem concerns not all users, and those which are serviced through the damaged infrastructure.

The Computer Business Review edition writes that problems with access to Exchange Online are observed in several countries, including in Britain and Holland.

Among those who announced malfunctions 50% told that the problem was connected with connection to the server while 25% had problems with access to Outlook, and 25% — to Exchange.

Judging by messages on the website Reddit, there was a global failure in work of Microsoft Office 365 which is observed in the Republic of South Africa, Iceland, Sweden, Switzerland, South America and other regions.

According to TAdviser, corporate users had no opportunity to use a mail service for all day on January 24. By 6:20 p.m. Moscow time the website outlook.office365.com in Russia is started normally.

The stop of e-mail should not be new regulation — the expert in resistance to threats of cyber security in Mimecast company of Pitas comments on Banham (Pete Banham). — It is finally a human error, but not technical failure. IT heads should realize the responsibility here. It is clear, that use only of one cloud provider will break further work of the companies every time when there is a failure.

The mail service of Microsoft Exchange Online endured global failure on January 24, 2019

Azure and Office 365 services failed more than once. For example, failure was observed at the end of November, 2018 and then was connected with an overload of a cache of the resident Redis database management system.^[2]

Notes