Recently, one of my customer is having issue on the Exchange Online.
The case is that the company is using a 3rd-party notification system to send out alerts to internal staffs everyday, somehow, he found that the messages are displayed to be blocked in the 3rd-party reporting system.
We have double checked the allow-and-block in Mail Flow, and even set the domain of the system to bypass the spam filtering, however, it does not help.
Finally, I came up with a solution.
When you send an email through a 3rd-party system (it depends), the email is transmitted through the 3rd-party servers instead of Office 365 server. Email can be easy to forge, so the system will automatically authenticates all emails sent through its system using multiple authentication methods to help improve deliverability.
In order to let it authorized in Office 365, what you need is adding the DNS record to allow the 3rd-party domain in SPF record.
v=spf1 include:spf.protection.outlook.com include:3rd-party.domain.com -all
That did the trick!
With the new launch of Office 365, the entire platform is consolidated with Exchange 2013, SharePoint 2013 and Lync 2013. However, when working with a customer to connect Outlook 2010 to Exchange Online in new Office 365, it prompts for password again and again and it cannot connect while saying the Exchange Server is offline.
In this situation, the SMTP address is displayed incorrectly. For example, the address is displayed as GUID@DOMAIN.COM.
Here comes to the solution.
It is simple to share a calendar in Office 365 – Exchange Online. However, you may find it difficult to share with advanced feature – permission for creating, editing and deleting of Calendar Items. You can do it directly in Outlook 2010 , but some may be only using Outlook Web App (OWA). Here comes to the solution. Continue reading
For Exchange Online administrators, managing the hosted Exchange (by Microsoft) may be both easy and difficult. Easy because of the Online Administration Panel provided by Microsoft located at https://portal.microsoftonline.com/. Difficult since some advanced setup is not entertained in the portal.
It will not be the case for some large enterprises since they usually deploy as hybrid mode, existence of both cloud and on-premises Exchange Server. Therefore, the Exchange Management Console can be used to manage both cloud and on-premises server.
Up to this, I have the initiative to create the Online Management Console for those who have only used the Cloud Service and are headache about using PowerShell.
Here is the screenshots, give me some advice if you have any about the tool.
I think most of the customer migrating from on-premise to cloud will have a question. How can I limit the POP3/IMAP access of the employees.
To do this in on-premise is as easy as stopping the IMAP4 service or stop the IMAP4 in Exchange Server Management Application.
However, they may wonder, I do not have the tool in Office 365. How can I be able to achieve.
To do this, you need PowerShell to help you. Continue reading