Register now for the Migrate to Innovate Summit
Join the summit on March 11, presented in partnership with Intel. Stay agile, innovate for the future, and maintain a competitive edge by accelerating your cloud migration and modernization journey. Microsoft thought leaders will discuss the latest news and trends, showcase real-world case studies, and share how Azure can help you fully embrace AI. Join us to: Maximize business value and build the foundation for successful innovation by leveraging the latest Azure and Intel capabilities for your workloads. Dive into case studies and real-world examples showcasing how organizations have successfully transformed their business and how you can be next by migrating and modernizing on Azure. Make sure your cloud migration and modernization journey is using the best practices and strategies featured in product demonstrations. Register now > Migrate to Innovate Summit Tuesday, March 11, 2025 9:00 AM–11:30 AM Pacific Time (UTC-7)Register now for the Migrate to Innovate Summit
Join the summit on March 11, presented in partnership with Intel. Stay agile, innovate for the future, and maintain a competitive edge by accelerating your cloud migration and modernization journey. Microsoft thought leaders will discuss the latest news and trends, showcase real-world case studies, and share how Azure can help you fully embrace AI. Join us to: Maximize business value and build the foundation for successful innovation by leveraging the latest Azure and Intel capabilities for your workloads. Dive into case studies and real-world examples showcasing how organizations have successfully transformed their business and how you can be next by migrating and modernizing on Azure. Make sure your cloud migration and modernization journey is using the best practices and strategies featured in product demonstrations. Register now > Migrate to Innovate Summit Tuesday, March 11, 2025 9:00 AM–11:30 AM Pacific Time (UTC-7)
Adding 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?What's in a Name?
Recently the ADMS (Active Directory Migration Service) changed its name to IMS (Identity Migration Service). If you’re not familiar with the ADMS offering, it is an orchestration of technologies that allows migration of user and computer objects from one or many on-premises Active Directory domains to another. This can be helpful in many scenarios including mergers, acquisitions and divestitures. ADMS features include: Secure connections to ADMS services for synchronization and migration. Identity synchronization and transformation. Group and User sidHistory Unified migration portal with multiple migration methods App remediation pipeline Many to one/One to many connections Client application flexibility – Customer supplied scripts can be added to meet the needs of the individual customers as migrations occur. Preservation of user profiles The best feature, the crème de la crème if you will, is the self-service model. This means that your busy CFO (don’t forget who pays the bills), can wait until he’s free to opt into a migration rather than someone in IT dictating when he gets migrated. If you prefer the white glove treatment, you can leverage surrogate migration where skilled IT personnel perform the user migration on behalf of a special user. Why Change? Recently we’ve had an opportunity to look at what the service provides and what lies ahead, and the name just doesn’t fully fit what we do and what we’re intending for our products’ road map. Identity Migration Service is more encompassing for the features and functionality we’re targeting across multiple services. Why is this important? We’re using our years of experience, knowledge and expertise to extend our on-premises domain migrations to cloud services. As a first release of IMS we will debut a tenant-to-tenant migration (for customers who have no on-premises footprint). This will fully synchronize your directory from the source tenant into the target and perform the user migration, remediation tasks as well as workstation Entra join to the new Entra tenant (while maintaining the user’s profile). A following release will add functionality to migrate customers who have deployed on premise Active Directory and are ready to step into the cloud. Our on-premises AD to Entra migration will work similarly to both tenant to tenant and AD to AD where the user and group objects are synchronized, activated at migration time and workstations migrated. This will have the option of using our self-service, opt-in model we currently leverage in our ADMS product. Does this mean ADMS functionality is going away? No, we are simply expanding the functionality to include services our customers want and need. We understand that the ADMS feature set is still sought out by our customers and we are committed to enabling customer migrations within every service. Is ADMS/IMS just a migration solution? No, it is a family of solutions. We have many great services and tools that have enabled customers to navigate logical issues with identity transitions (Migrations, modernizations, synchronizations, etc.). Below are some of our other current services: ADGMS - Active Directory Group Modernization Service, for the conversion of on-premises synchronized distribution groups into cloud only groups ADSS - The backbone of migrations is a customizable sync engine that can apply business logic for the objects being synced and transformed between directories. This is leveraged by many of our solutions; however, it can be a standalone sync service as well. Tsync - Tenant synchronization. Using the ADSS synchronization engine we can synchronize and transform objects between tenants. SOA - Source of Authority. Customizable business logic that can be applied to AAD Connect so it can pivot the authoritative source of an object to another directory. This allows AAD Connect to marry the new, authoritative user with the correct identity in Entra. Which IMS solution best fits your needs? Which features would you like to see on our roadmap? Have any questions about an existing service or functionality? Let us know in the comments or reach out to us at IMSSales@microsoft.com
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?
How to In-Place Upgrade Windows Server 2008 R2 to Windows Server 2019
As you know the Windows Server 2008 and Windows Server 2008 R2 are out of support on January 14th, 2020. Customer will need to upgrade their Windows Server 2008 and Windows Server 2008 R2 to a newer version of Windows Server or migrate these servers to Microsoft Azure.Migrating 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 advise
