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.
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.
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.
This document will show you how to step by step to configure Cisco Meraki to azure site to site VPN tunnels IPsec IKEv2.
The Cisco Meraki Security appliances running firmware must be on firmware 15 or greater to take advantage of IKEv2, because the firmware 15.x is still beta version, you need to ask Meraki support to upgrade it for you if you need it.
Veeam released the Backup & Replication v10 on February, and with it comes over 150+ anticipated new features and enhancements. Veeam now also have support for the option “Copy backups to object storage as soon as they are created” at SOBR Repositories settings, it will create additional copy of your backups for added redundancy by having all backups copied to the capacity tier as soon as they are created on the performance tier. Let’s follow steps to configure it.
When you try to send email out from exchange server VM at Azure, you will notice it will failed send email out. Because starting on November 15, 2017, outbound email messages that are sent directly to external domains (such as outlook.com and gmail.com) from a virtual machine (VM) are made available only to certain subscription types in Microsoft Azure. Outbound SMTP connections that use TCP port 25 were blocked. (Port 25 is primarily used for unauthenticated email delivery.), so you will notice the exchange server VM won’t send email out after you configure send connector.