New feature on version 8

The version 8 of Veeam Backup & Replication add a lot of new feature in VBO (Veeam Backup for Microsoft 365. But before we start talking about what’s new, it’s important to remember why you should save Microsoft 365. Many people think that Microsoft supports data backup in the cloud. But the reality is very different. MS provides the platform and ensures its availability. The data remains the responsibility of the customer.

These days, Teams and Sharepoint are widely used and contain a large amount of company data. That’s why it’s so important to make daily back-ups to prevent accidental deletion, data encryption and malicious operations. Now that we’ve got that reminder out of the way, let’s take a look at what’s new in the system.

Proxy Pool. The proxy pool contain few backup proxy and permit to balance the load between different servers. This means that for large backups (e.g. large sharepoint sites, large mailboxes, etc.), the load is balanced across all the servers in the pool.

PostGreSQL is now used by Veeam Backup for Microsoft 365. The cache is now centralized on a PostgreSQL database. This new feature permit increased scalability.

Immuabilité for primary storage. It is now possible to activate immutability for primary storage. As a reminder, immutability was only possible with the backup copy job. We can now secure all our backup chains against malicious encryption.

Linux proxy with version 8. It’s now possible to use Windows and Linux proxy with version 8 of Veeam Backup for Microsoft 365. This allows the company to save on Microsoft licences.

Teams private channels are now supported. Private channels can be backed up to ensure total backup

MFA can be enable to prevent unauthorised access to the Veeam for Microsoft 365 console.

Install Veeam Backup for Microsoft 365

Mount the ISO file of the Veeam Backup for M365 v8 on a Windows server. This iso contains the necessary installation files. It is preferable to separate Veeam Backup for Microsoft 365 and Veeam Backup & Replication.

Start the installation by executing the file Veeam.Setup at the root of the ISO file.

Click on Install to begin the installation of Veeam Backup for Microsoft 365

We have a number of choices. Click on Veeam Backup for Microsoft 365 for a full installation of Veeam

• Veeam Backup for Microsoft 365 : Install Veeam Backup for Microsoft 365 on the server

• Veeam Backup for Microsoft 365 Console : Install only the console of Veeam Backup for Microsoft 365 on the server

• Veeam Backup for Microsoft 365 Powershell : Install the CmdLets Powershell for manage Veeam Backup for Microsoft 365

• Veeam Backup for Microsoft 365 Rest API & Restore Portal : Install only HTTPS ressources for the user interfaces. The restore portal on the REST APIs permit to configure restore delegations.

Accept the licence agreement by clicking on the button I accept. Click on Browse the select the licence file. If you not use the licence, Veeam backup for Microsoft 365 is configured on community edition (some limitation is apply with this edition). Click on Next.

The configuration is checked to ensure that the server meets the necessary prerequisites. In the next window, click Customi to configure the installation parameters.

Select the installation path and configure Database information.

NATS must be configured. This new feature added on Veeam Backup for Microsoft 365 v8 ensures communication between all Backup proxies in the proxy pool. It’s poszsible during the installation to install a new NATS server or use an existing server. If you want install a new NATS server leaves the default setting (Install new instance) and type username and password.

Verify the information and click on Install for begin the installation of Veeam Backup for M365.

Installation is in progress …

Click on Finish to close the installation wizard. Veeam is now correctly installed.

Add M365 tenant

From the desktop, launch the shortcut for access at the console Veeam Backup for M365. Click on Connect.

From the Organization tab, click on Add Org in the Home ribbon.

Select Microsoft 365 and the services that you want protect.

Basic authentification is deprecated and it’s recommended to use only the Modern authentification.

Type the name of the Entra ID Application and click on Install to create a new certificate. It’s used for authentification with Microsoft Entra ID. It’s possible to generate a new self-signed certificate, used an existing self-signed certificate or used a certificate issued by an internal PKI.

Select Generate a new self-signed certificate or option that you want and click on Next.

log in to Microsoft 365 must be performed. Click on Copy code to copy the code needed for authentification. Click on the link to open the link on web browser and proceed at the authentification. Administrative account it will be needed to perform this action.

Paste the code into the browser and use administrative account to connect to Microsoft 365.

Verify that the authentification is performed without any error. The connection is performed, if you don’t have any error, click on Finish. M365 organization is been added on the console and it can be renamed.