u/Hot_Connection9504

I’m trying to add a Gmail/Google Workspace account to Outlook with Microsoft 365 Apps, but I keep getting this error during setup:

“The connection to the incoming (IMAP) server was dropped. Please check the incoming (IMAP) server settings and try again.”

What I already checked:

• IMAP enabled in Gmail
• App Password created
• Correct settings:
  • imap.gmail.com / Port 993 / SSL
  • smtp.gmail.com / Port 587 / STARTTLS
• Internet connectivity working
• Port 993 reachable
• Outlook profile recreated
• Credential Manager cleaned
• Registry OAuth identity cache removed

Google login/authentication succeeds, but Outlook still throws this IMAP dropped connection error.

Has anyone found a proper fix for this issue on Outlook 365?

I’m trying to add a Gmail/Google Workspace account to Outlook with Microsoft 365 Apps, but I keep getting this error during setup:

“The connection to the incoming (IMAP) server was dropped. Please check the incoming (IMAP) server settings and try again.”

What I already checked:

• IMAP enabled in Gmail
• App Password created
• Correct settings:
  • imap.gmail.com / Port 993 / SSL
  • smtp.gmail.com / Port 587 / STARTTLS
• Internet connectivity working
• Port 993 reachable
• Outlook profile recreated
• Credential Manager cleaned
• Registry OAuth identity cache removed

Google login/authentication succeeds, but Outlook still throws this IMAP dropped connection error.

Has anyone found a proper fix for this issue on Outlook 365?

I’m trying to add a Gmail/Google Workspace account to Outlook with Microsoft 365 Apps, but I keep getting this error during setup:

“The connection to the incoming (IMAP) server was dropped. Please check the incoming (IMAP) server settings and try again.”

What I already checked:

• IMAP enabled in Gmail
• App Password created
• Correct settings:
  • imap.gmail.com / Port 993 / SSL
  • smtp.gmail.com / Port 587 / STARTTLS
• Internet connectivity working
• Port 993 reachable
• Outlook profile recreated
• Credential Manager cleaned
• Registry OAuth identity cache removed

Google login/authentication succeeds, but Outlook still throws this IMAP dropped connection error.

Has anyone found a proper fix for this issue on Outlook 365?

Sometimes I genuinely feel lost in the Indian IT industry.

I am 24 years old and I have almost 3 years of experience as an IT Executive and this is already my 3rd company. I work on Windows Server, Microsoft 365, networking, user support, infrastructure issues, and a lot of real-world IT tasks daily. I’ve spent a lot of time learning and improving my technical skills on my own as well.

But despite all this, my current CTC is only ₹3.85 LPA and my in-hand salary is around ₹26K/month.

The most frustrating part is that I still struggle to get into a proper corporate company because I don’t have my bachelor’s degree completed yet (currently pursuing it online). Sometimes it honestly feels like companies care more about a degree sheet than actual hands-on skills and experience.

I know there are people earning much more with less practical knowledge, and it gets mentally exhausting after a point.

Am I actually underpaid for my experience and skillset, or is this just how the Indian IT market works right now?

Hi everyone,

I’m testing Exchange Online MRM archive policies in a Microsoft 365 Business Basic trial tenant and wanted to understand if this behavior is normal.

Setup:

• Created a 1-day MRM retention tag (Move to Archive)
• Created and assigned an MRM retention policy
• Enabled Online Archive mailbox
• Verified policy assignment via PowerShell
• Mailbox archive status = Active

When I manually run:

Start-ManagedFolderAssistant -Identity user@domain.com

the eligible emails immediately move to the archive mailbox successfully.

However, automatic processing does not seem to happen even after emails are older than 24+ hours (sometimes multiple days).

So basically:

• Manual MFA = works perfectly
• Automatic MFA = seems delayed/not running

I also noticed Microsoft’s note in Purview mentioning that classic MRM is mainly recommended for archive movement now.

My question:
Is delayed/non-aggressive automatic MFA processing normal in small/trial/Business Basic tenants, or is there something else I should check?

Would appreciate insights from anyone who has tested MRM recently in Exchange Online.

Thanks!