migration
390 TopicsInterface Views in Microsoft 365 Admin Center
1. Simplified View Purpose: Designed for small businesses or organizations with limited IT resources. Features: Streamlined dashboard with essential tasks like user management, license assignment, and password resets. Minimal configuration options to reduce complexity. Quick access to support and basic service health info. Use Case: Ideal for admins who need to perform routine tasks without diving into advanced settings. 2. Dashboard View (Advanced View) Purpose: Tailored for medium to large enterprises with complex IT environments. Features: Full access to all admin centers (Exchange, SharePoint, Teams, etc.). Advanced analytics, reporting, and configuration tools. Role-based access control and security management. Customizable widgets and navigation for personalized workflows. Use Case: Suitable for IT teams managing multiple services, users, and compliance requirements. Customization Needs Are there specific tasks we perform frequently that can be automated in the dashboard?189Views0likes2CommentsQuest Tool Migrates Protected Email and Files Between Tenants
A new feature of the Quest On Demand migration suite supports the tenant-to-tenant migration of Exchange and SharePoint content protected by sensitivity labels. This might not seem a big deal, but it’s the first time that a migration product has been able to automatically move protected files and messages from one tenant to another, including files protected by sensitivity labels with user-defined permissions. https://office365itpros.com/2025/05/21/sensitivity-labels-t2t-migration/100Views0likes1CommentGoogle workspace migration - Automatic doesn't download the JSON while creating the migration endpoi
I recently came across an issue where the google workspace migration wasn't downloading the Json file. After a lot of struggle, I figured out that google by default blocks service account key creation. To resolve this, follow the below mentioned steps 1) login to https://console.cloud.google.com/iam-admin and select the root org 2) Add Organisation Policy Administrator role 3) Click on Organization policies and then search for "Disable service account key creation" and set the enforcement to OFF. 4) Now you should be able to download the JSON.3.2KViews5likes1CommentDomain is on Godaddy but email is hosted by Gmail
I purchased our domains through Godaddy and that is where they are still registered, however, the email is hosted by Gmail. My office wishes to migrate everything to Microsoft 365. We only have 2 users so it should be easy but I am concerned that having the hosting split as it is will create issues. One of my users has massive psts files and uses Outlook as his home for everything. Currently it is all on his desktop and connects to Gmail through imap. The other user logs into Gmail directly and keeps no email on her desktop. We have no file servers. Both users keep all their files on their desktop. I'm not too worried about the files. We can migrate them later. It's the email that has me concerned. Can you tell me what I should do to make sure we have a seamless migration?2.6KViews0likes3CommentsArticle on Migration of file share to SharePoint Site
I wrote an article on LinkedIn https://www.linkedin.com/pulse/migrate-your-file-share-content-microsoft-365-site-ikechukwu-elendu-7qg6f on how to migrate file share to a SharePoint site from your on-premises PC Please look at it and give me your honest feedback. Thanks a lot.20Views0likes0CommentsAdding Proxy Addresses in AD Before Tenant-to-Tenant Migration Cutover
We're in the process of migrating users from another M365 tenant into our own, which is synced with on-prem AD. Before the cutover, we'd like to add the proxy addresses from the source tenant to our AD and have them sync to the cloud once the domain is added to our M365 tenant. Would this work as expected, or are there any potential issues to be aware of?124Views0likes2CommentsExchange Online - Seeing all aliases of dist list
Hello all, We are preparing to sync our on prem AD distro groups and mail enabled security groups to O365, with a migration of email to EO to follow. (We already have user accounts synced via Azure AD Connect.) One gotcha, is that we have old email addresses (with unused domains) on these groups and I'm not sure if thats going to be a problem if I sync then before stripping those out. I was able to script removing those from the user accounts before we synced those, though doing it for the groups hasn't been successful so far. I went ahead and synced a couple of DG's to O365 just as a trial run, and when I view the groups in Exchange Admin Center / Groups/ Dist List, it shows the primary email email address and two of the alias addresses. Then it shows '+3 more'. I can't figure out how to view those '3 more' aliases. I'm wanting to see if those additional addresses are good addresses (with our domains that do exist in O365). If so, then I would seem that the sync leaves out the 'bad' addresses, if that makes sense. Thanks for any pointers!Solved357Views0likes2CommentsMigrating G suite to Office 365
Dears, Good day, I working on a company which hosted their email on G suite, and I want to migrate all mailboxes, calendar, tasks, files, all things to Office 365. kindly let me know the steps for Migration, we have 69 users needed to be completely migrated. Kindly advise4.1KViews0likes4CommentsAdministrative Units - are they a possible solution in this case?
Hi, I'm looking at a situation where a company has two divisions, which we will call Corporate and Operations. They are geographically distinct as well as having significantly different requirements in terms of security, data access, mobile device control, applications requirements and other factors. At the current time, for mostly historical reasons, all IT is run from Operations, primarily based on a Microsoft 365 Tenancy. This isn't working well, and for a variety of reasons it seems it would be significantly preferable if the current Admins dealt with, and could only access, things related to Operations while new admins deal with Corporate. If any admin is going to have access to everything it needs to be Corporate (e.g. Operations admins should not be able to see Corporate emails, the reverse is less of an issue) A solution they are seriously considering is simply starting a new Microsoft 365 Tenancy for Corporate and then linking between them as required, possibly using a Multi Tenant Organization. The divisions appear to be distinct enough this could function quite well. They own several domains and apparently, email addresses are currently split divisionally to two of those domains. However, I have just come across Administrative units and wonder if an alternative might be to use those? I'm still on the learning curve for 365 so despite having a look at the documentation it's currently unclear to me what the powers and restrictions that can be assigned to the administrator of a given unit.112Views0likes1Comment