Forum Widgets
Latest Discussions
Google Workspace migration to Microsoft 365 with multiple domains
I'm managing a project to migrate mail from Google Workspace to Microsoft 365 via (Google Workspace Migration). My scenario is composed as follows: Primary domain in GWS: domain1.com Secondary domain in GWS: domain2.com Routing domain (alias domain) in GWS: m365.domain1.com and gws.domain1.com Microsoft side: accepted domain: domain1.com,domain2.com, m365.domain1.com and gws.domain1.com Users domain1.com have aliases routing domain m365.domain1.com and external forwarding gws.domain2.com. Users domain2.com have aliases routing domain m365.domain1.com and external forwarding gws.domain1.com. For users domain1.com the hybrid coexistence scenario, mailflow and batch work perfectly. For domain2.com users, the batch works, but at the time of completion, it returns an error that Google asks for verification of the forwarding address, as it is different from domain2.com. “GmailForwardingAddressRequiresVerificationException” Which configuration am I doing wrong? And above all, is the scenario in question supported? Thank you
Migration Email to 365
Hello, I would like to transfer my email account from our host Siteground to Microsoft's business account. This is because the conventional hoster only has limited email storage and is almost full. The provider Siteground supports IMAP. I have several questions: How do I proceed now? Do I have to transfer the domain first and then can I also transfer the email account in the second step? Once the transfer has been completed, can I create additional email addresses via Siteground or do I now have to create all emails via 365 (which will probably incur costs)? Thank you!
GoDaddy to Microsoft 365 Migration Issues
Hi there, I wonder if I could get some help with an issue I've got. Currently I am attempting to migrate one user mailbox from the current GoDaddy tenant to our new Microsoft tenant, to initially test out the migration. I've followed the Migration tool in the Exchange admin center but am receiving the following error: Error: MigrationRecipientNotFoundException: A recipient wasn't found for "***@***.onmicrosoft.com". Create a recipient of the appropriate type for this migration and try again. I've got the user created in the Microsoft 365 admin center and a mailbox is set up for them. Both on GoDaddy and Microsoft it is UserMailbox recipient type. I'm using the IMAP Migration settings as outlined from the GoDaddy IMAP settings, and have since checked with GoDaddy and they give these settings: IMAP Server: imap.secureserver.net Authentication: Basic Encryption: SSL Accept untrusted certificates: Yes Port: 993 GoDaddy have also said that Basic authentication is supported by them and I have checked the Entra configuration to ensure that Basic is not blocked. I have even had the user I'm attempting to migrate log in to the temporary onmicrosoft account to make sure there are no log in issues there. I have posted this on the Answers forum as well and was pointed in this direction for further help. Any thoughts or help on this would be amazing. Thanks in advance, OliEFZ4 BAD Request is throttled
Hi, We recently migrated to Microsoft 365, and we have an application called KEO, which downloads emails for its internal functionality. However, the application is now displaying an error: "EFZ4 BAD Request is throttled. Wait XXXXX ms" Is there a way to fix this issue, or what steps should we take to resolve it? Thank you
Litigation Hold Mailbox Migration
My company is currently moving from Exchange 2016 to 365. We are currently setup in a hybrid environment. The question arose of how do we migrate mailboxes that are on litigation hold. I have found that you can do a migration of the lit hold mailboxes from on-prem to 365 without any issues per this document - https://learn.microsoft.com/en-us/exchange/policy-and-compliance/holds/holds?view=exchserver-2016#migrating-mailboxes-on-hold-from-exchange-server-to-microsoft-365-or-office-365. However, what I can't seem to find is the best way to test a migration for a lit hold mailbox. I also have found that some of our lit hold mailboxes have been on hold so long that their mailboxes are on Exchange version 0.10. So, I really have 2 questions. 1) How can I test migrating a lit hold mailbox from on prem to 365 without using an active person's mailbox? 2) Does the Exchange Version for the mailbox matter when I migrate them? Any help would be much appreciated.Migrating from Google Workspace to Microsoft 365 with to have two separate Mailboxes per User + SSO
Context and Requirements: My company (abc.com) is being acquired by another org (xyz.com). We’re currently on Google Workspace (G Suite) for abc.com email and want to migrate everything (email, calendar, contacts) into Microsoft 365 — specifically into the xyz.com tenant. After migration, each user must have two fully separate mailboxes: Mailbox A: email address removed for privacy reasons (data migrated from G Suite) Mailbox B: email address removed for privacy reasons (new mailbox in the xyz.com tenant) We need true single sign-on (SSO) so users can log in once and access both mailboxes (not just alias addresses) within the same tenant. We want to minimize complexity. FYI we will set up abc.com as an Accepted Domain in xyz.com Microsoft Exchange tenant. What I’ve Investigated So Far: Migration Tools: The Exchange Admin Center has a built-in G Suite migration wizard, but it mainly migrates mail to one mailbox. Third-party tools like BitTitan MigrationWiz can also handle G Suite → M365 migrations. Two-Mailbox Setup Approaches: One licensed mailbox + one shared mailbox: For example, the user’s main mailbox would be email address removed for privacy reasons (fully licensed with migrated data), while email address removed for privacy reasons is a shared mailbox to keep it separate. The email address removed for privacy reasons account gets Full Access and Send As permissions on the xyz.com mailbox. Pros: Single sign-on, one set of creds, minimal extra licensing. The data stays separate (two distinct mail stores). Cons: Shared mailboxes are limited to 50GB if unlicensed, and some compliance features may require a license. Two fully licensed user mailboxes (two Azure AD user accounts, e.g. email address removed for privacy reasons and email address removed for privacy reasons): Each mailbox is completely independent, but typically requires two sign-ins unless there’s advanced identity federation to unify credentials. Also doubles the licensing. Pros: Full feature set in both mailboxes, no shared mailbox constraints. Cons: Additional license costs, and not a straightforward “one-click” SSO for both. Questions Which approach is best for maintaining two discrete mailboxes per user without forcing them to manage multiple logins? Are there any best practices for migrating from Google Workspace into Exchange 365(specific tenaant) maintaining the same email address? Have you run into compliance or eDiscovery issues with a shared mailbox approach? Any caveats or special steps needed to ensure calendars and contacts migrate correctly from Google Workspace into the new environment?Help with 365 migration please
Can anyone help me with this Migration please. The tenancy has existed for some time and all users have had a business standard license to enable them to use Teams and Office 365 for some time. This means that mailboxes were created automatically but these have never been used. AD Sync was in place. I am trying to migrate from Exchange 2016 to 365. I have: Checked each user has an e-mail alias in Exchange @leonardgray.onmicrosoft.com. Configured Outlook Anywhere on my on-premises Exchange Server. Enabled MRS Proxy on your on-premises Exchange Server. Use the Microsoft Exchange Remote Connectivity Analyzer to test your connection settings. Used the Outlook Anywhere (RPC over HTTP) or Outlook Autodiscover tests - it is showing no issues. Checked the permissions on the account I'm using to migrate (domain admin and has FullAccess and assigned WriteProperty permissions). We're not on Exchange server 2007 so no need to worry about unified messaging. The domains are verified. The users are created licensed. I have the CSV with the list of users. I've created a variety of migration endpoints and it verified as it saved and saved successfully. I initially tried to use a cutover migration as it is what I have used successfully in the past. This failed, when I researched the error the articles suggested that it was because AD sync was in place. So I turned off AD sync. The cutover migration continued to fail. The articles suggested that a Staged migration was a better option for this scenario. This failed with this error: Error: MigrationTransientException: Failed to update the on-premises mailbox with the target address (SMTP:email address removed for privacy reasons). The mail sent to the user will not reach user's hosted mailbox. The error might be due to account credentials used for migration not having enough permission to write data back into the on-premise AD. Please ensure that the account credential has Domain Admin privilege. --] We weren't able to connect to the remote server. Please verify that the migration endpoint settings are correct and your certificate is valid, and then try again. Consider using the Exchange Remote Connectivity Analyzer (https://testexchangeconnectivity.com) to diagnose the connectivity issues. I did some more reading and found an article that suggested that Staged migrations can only be used from Server 2003 and 2007. So I decided to try a Remote Migration. This one failed with the error: Error: TargetUserAlreadyHasPrimaryMailboxException: Target user '902b455c-5986-47c7-9988-bb7282df52b5' already has a primary mailbox. The articles about this suggest I need to delete the data in homeMDB and homeMTA. The data in homeMDB looks like a pretty important link between Exchange on prem and Active Directory. I'm not particularly comfortable with just deleting this. Can anyone tell me what I'm missing?
Cuales son los pasos para migrar mi correo que tengo en Godaddy a Microsoft 365
Tengo una cuenta de correo en Godaddy con mi dominio personal, quiero comprar una licencia de Microsoft 365 y migrar mi correo hacia Microsoft 365 así poder aprovechas todos los servicios que ofrece Microsoft Mi licencia actual vence el 1 de enero del 2025 He tratado de comprar una licencia con la cuenta de correo, pero me da error porque me indica que está asociado a un proveedor externo que Godaddy. Intente migrarlo con la gente de Godaddy, me dice que debo tener un plan de licencia y el correo creado en Microsoft para que hagan la migración. Todo me indica que en Godaddy están haciendo lo imposible para entorpecer la migración. Quedo atento a su respuesta
Request for Consultation on M365 Power User Model Concept
Hello Team, As a Microsoft Solutions Provider, I am in the process of designing a detailed M365 Power User Model Concept aimed at enhancing an organization's current M365 environment with a focus on scalability and sustainability. The primary objective is to establish a Power User model to drive organizational efficiency, optimize user engagement, and leverage advanced M365 capabilities. This concept will include a structured approach to implementing the Power User model as part of a comprehensive upgrade to the latest M365 framework. Your expertise and consultation on the development and deployment of this model would be greatly appreciated. Thank you for your insights. Best regards,FastTrack in a Classic site collection in my tenant
I have a very brief question for which I have not been able to get any input or answers so, I am putting it out to anyone that might have some info to offer. I have a Classic SharePoint FastTrack site collection in my tenant containing Classic Add-ins. May I delete it and the Add-ins along with it without causing problems with the use of FastTrack programs and services? https://XXXXXX.sharepoint.com/sites/fasttrack https://XXXXXX.sharepoint.com/sites/apps Thank you for any insight you can offer.
