Veeam Backup for Microsoft 365 extends data protection and follows the same methodology as Veeam Backup and Replication. This 3-2-1-1-0 rule can also be applied to backup repositories in cloud-based object storage using Backup Copy Jobs: Azure Blob Storage Archive access tier, Amazon S3 Glacier storage class, or Amazon S3 Glacier Deep Archive storage class.
The procedure creates a backup job to backup the organization objects to Azure Blob Cool Tier repositories.
Backup Jobs in Veeam Backup for Microsoft 365 can be configured to specify object types and their processing and exclusion options when creating and configuring backup jobs.
You can also configure notification settings in Microsoft 365 with an MFA-enabled account. This can be used to send email notifications about the results of backup jobs.
You can also configure Microsoft 365 for notification settings using a non-MFA account. This can be used to send email notifications about the results of backup jobs.
When adding Microsoft Azure Blob storage, different storage account types can be used for Veeam Backup for Microsoft 365.
Network Attached Storage can also be a backup repository with Veeam Backup for Microsoft 365. These Network Attached Storage devices can be accessed and configured through a shared folder on your computer or through any other physical device that supports the SMB protocol.
The following backup repositories can be added to the infrastructure with Veeam Backup for Microsoft 365:
Backup proxy server’s local directory.
Direct Attached Storage is connected to the backup proxy server.
Storage Area Network.
Network Attached Storage (SMB shares version 3.0 or later)
This procedure upgrades a Windows Server 2012 R2 generation Hyper-V virtual machine to Windows Server 2019 (2022) generation 2 Hyper-V virtual machine.
You can configure the SendGrid account as an SMTP relay for notification settings if you want Veeam Backup for Microsoft 365 to send email notifications about backup job results.
If you are going to use Microsoft 365 email account for Veeam Notifications, it happened that SmtpClientAuthentication is disabled for the Tenant error. Today I will show you how to fix it.
The Azure archiver appliance is a small auxiliary machine in Microsoft Azure that is deployed and configured automatically by Veeam Backup for Microsoft 365. Veeam services that Veeam Backup for Microsoft 365 installs on the Azure archiver appliance compress data passed through. This helps reduce network traffic and increase the speed of backup copy.
Veeam Backup for Microsoft 365 supports different Azure storage account types for standard and premium performance tiers. Tables in this section list the supported storage account types.
Microsoft is ending support for the Azure Active Directory Graph API. To allow for continued service, if your application providers migrate all Azure Active Directory Synchronization integrations to the MS Graph API, you need to change your API permissions.
If you try to add an organization with modern authentication and legacy protocols or basic authentication at Veeam Backup for Microsoft 365 but failed, the error message is ” Connect to PowerShell: Connecting to remote server outlook.office365.com failed with the following error message: Access is denied”.
If you create a new Citrix license server and would like to move the existing licenses to the new server, please follow the below steps to reallocate it.
Veeam Backup for Microsoft 365 v6 cumulative patches P20220413 Released on May 5, 2022. This cumulative patch includes the new features, enhancements, and fixes for the original V6 builds.
Veeam Backup for Microsoft 365 use backup proxy servers to leverage network when backup or restore data. The Veeam Backup for Microsoft 365 manager server is the default local backup proxy server.
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.