If you try to add organization at Veeam Backup for Microsoft 365, it happens Connect to PowerShell: Connecting to remote server outlook.office365.com failed with the following error message: Access is denied error, that’s because Microsoft begin disabling Basic authentication for Outlook, EWS, RPS, POP, IMAP, and EAS protocols in Exchange Online.
You are required to provide a username and password to authenticate to your Microsoft 365 organization if you add an organization using the basic authentication method.
I won’t recommend adding organization with basic authentication, Microsoft announced that effective October 1, 2022, we will begin disabling Basic authentication for Outlook, EWS, RPS, POP, IMAP, and EAS protocols in Exchange Online. SMTP Auth will also be disabled if it is not being used.
You will use both Veeam Backup account and Azure AD application for authentication if you add an organization using the modern authentication method with legacy protocols allowed. Veeam Backup for Microsoft 365 uses Veeam Backup account and an application to establish a connection to your Microsoft 365 organizations with disabled security defaults and maintain data transfer during backup and restore sessions.
If your organization currently has subscriptions to Office 365 Enterprise E3 or E5, the default mailbox storage limit is supported 100GB. You can check it from the account information of outlook.
Unfortunately, there are many people noticed the default size is still showing 50GB, today, I am going to show you how to increase it to 100GB.
Veeam released Veeam Backup for Microsoft Office 365 on June 4, but the GA build of Veeam Backup for Microsoft Office 365 version 4c (build 126.96.36.1999) was recalled due to a backup sync issue identified by Veeam quality assurance.
If you are running build 188.8.131.529 please refer to the KB3194 and install the corresponding patch.
Veeam released Veeam Backup for Microsoft Office 365 V3 on November 26 2019, there are lots of function be increased and improved, including Object storage support, Increased Information security, Faster backup performance, Exclude retention for contacts and calendars, Group-based targeting, Enhanced reporting…etc.
You have to very carefully about users License before run Veeam Backup for Microsoft Office 365 backup job, because once a license has been given over to a user/site/item, it will aspirate (fall off) 31 days after the last backup. so, you will got the warning message even you removed the user from the backup job settings.
Fortunately, you don’t need to remove backup job or backup repository now because Veeam Backup for Microsoft Office 365 V3.0 added the feature to remove licensed users, but you must remove those unwanted licensed users from backup repository’s database and then remove the license.
Have you been follow my previously post steps to add your domain to Office 365? if not please check my previously post and do it. If you did and then it’s time to deploy Azure AD connect to sync your on-premises AD to Azure AD (Office 365).
You can download and install Azure AD Connect to your ADFS server or you also can install it at your domain server if you won’t use ADFS server for your infrastructure. you can install Azure Ad Connect with Express settings but I recommend install it with Customized settings, because you can adjust settings to match your requirements.
The process described mainly focuses on a typical transition of Exchange services to Office 365 environment, converting the Exchange servers to Office 365 CAS role, HUB role and MBX role. Additional role options such as the Unified Messaging Server role and Edge Transport role, are out-of-scope within this document.