Category: Office 365

121321 0312 Howtoincrea1 240x180 - How to increate office 365 E3 (E5) mailbox storage limits from 50GB to 100GB

How to increate office 365 E3 (E5) mailbox storage limits from 50GB to 100GB

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.

100420 0035 HowtoInstal3 240x180 - How to Upgrade Veeam Backup for Microsoft Office 365 to V4c Day 0 Update

How to Upgrade Veeam Backup for Microsoft Office 365 to V4c Day 0 Update

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 4.0.1.519) was recalled due to a backup sync issue identified by Veeam quality assurance.

If you are running build 4.0.1.519 please refer to the KB3194 and install the corresponding patch.

012320 1948 FIXEDAccess1 240x180 - FIXED Access is Denied Error for upgrading VBO 365 Default Backup Repository

FIXED Access is Denied Error for upgrading VBO 365 Default Backup Repository

I was trying to upgrade VBO 365 from V3 to V4, everything looks fine except upgrading Default Backup Repository, the status shows Upgrade failed “Access is denied”, it has never happed with other customers for upgrading VBO 365 from V3 to V4.

011520 2311 HowtoUpgrad28 240x180 - How to Upgrade Veeam Backup for Microsoft Office 365 V3 to V4

How to Upgrade Veeam Backup for Microsoft Office 365 V3 to V4

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.

041219 0036 HowtoRemove1 240x180 - How to Remove Users License from Veeam Backup for Microsoft Office 365

How to Remove Users License from Veeam Backup for Microsoft Office 365

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.

040918 2348 MigrateExch1 240x180 - Migrate Exchange Services from On-premises to Office 365 PART 2- Deploy Azure AD Connect

Migrate Exchange Services from On-premises to Office 365 PART 2- Deploy Azure AD Connect

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.

040718 2002 MigrateExch3 240x180 - Migrate Exchange Services from On-premises to Office 365 PART 1- Pre-requisites, Add On-Premises Domain and Deploy Certificate

Migrate Exchange Services from On-premises to Office 365 PART 1- Pre-requisites, Add On-Premises Domain and Deploy Certificate

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.