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.
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.
When you add an organization using the modern app-only authentication method, you are required to provide Azure AD application settings. Please reference following link to create and configure Azure AD Application permissions.
Veeam Backup for Microsoft 365 Modern Authentication and Legacy Protocols Authentication requires that you grant permissions to Azure AD applications to back up and restore data from/to your Microsoft 365 organizations.
When you add organization using the modern app-only authentication method, the permissions for Azure AD applications that are granted automatically by Veeam Backup for Microsoft 365.
Anyway, if you prefer to use a custom application of your own, make sure to grant all the permissions as below.
Veeam released Veeam Backup for Microsoft 365 v6 on March 9, 2022, there are lots of new features at this version included Self-Service Restore Portal, Backup copy to low-cost object storage… etc. the detail information as following link.
Veeam released Veeam Backup for Microsoft 365 v6 on March 9, 2022, there are lots of new features at this version included Self-Service Restore Portal, Backup copy to low-cost object storage… etc. the detail information as following link.
Veeam released Veeam Backup for Microsoft Office 365 v5d on September 22, 2021, Veeam Backup for Microsoft Office 365 v5 now has purpose-built backup and recovery for Microsoft Teams. The #1 Office 365 backup makes it easier than ever for users to quickly find and restore Teams data, including entire teams or specific channels and settings.
Today I am going to show you how to upgrade Veeam Backup for Microsoft Office 365 to V5d.
Veeam Backup and Replication V11a release on September 27, if you are still using earlier version, it’s the time to upgrade it to V11a. Veeam Backup & Replication v11a is the newer build of version 11 that addresses issues reported by customers on the original build and adds the following new features and enhancements.
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.
Today, we help our client to build a new S2D server as new Veeam Repository, now, we need to move the SOBR performance tier from the old repository server to this new server, I am going to show you how to move it.
Veeam is one of the best backup tools, there are many companies use it for Data Protection. Today, I am going to show you how to restore the on-premises VM to Azure.
Today, I tried to resize the virtual machine at Azure, it failed because of the virtual machine enabled accelerated networking for network interface.
If you have the same issues as mine, please follow below steps to use Azure Cloud Shell to disable it and fix the resize virtual machine failed issues.
If you would like to monitor the backup policy result of Veeam backup for Microsoft Azure, the email notification is useful tool to help you to monitor it.
You can follow steps as below to use a free SendGrid account for the email notification at Azure.
Have you been tried to delete users from Azure active directory or office 365 but failed? The error shows couldn’t delete this user because the account is synchronized with your on-premises server. You can delete the user from your on-premise server. If your Azure AD connect server still alive, that’s easy to solve, you can delete the user from on-premise domain controller, it will remove the user atomically. If the on-promise Azure AD connect server is no longer available, you can’t manage or delete the user (object) from the on-premises environment, please follow steps as below to delete it.
Today, I deploy a new domain controller server at Azure after site to site VPN built. Verify the replication status looks fine, but when I check the SYSVOL and LOGON shares folders status, I noticed there is no any shared folder at the new domain controller server.