Azure AD / Entra ID and Microsoft 365 Basic
In the last few weeks, I have struggled with new technologies. This encompasses the latest on the market in Android based mobile phones and a new Ryzen 9 mini desktop computer. To eliminate both old phone apps and old laptop applications in the MS Store (Apps) update, I wiped old phone access to accounts via Edge and Google. However, old laptop, which is an HP Ryzen 3 held on to apps and preferences somewhere across systems. So, on both my new mini desktop and the old laptop, I used PowerShell to eliminate remnants of DevHome Pre and CoPilot Pre which kept popping up. Low and behold, I saw new things in my Microsoft and Google Play stores on my devices. Not sure why this would not have happened on installation... Then thinking I was ready to remove XBOX. I did this as well via PowerShell commands. So, now both my machines are work machines with the AMD graphics qualities and XBOX gaming services. Then I removed any old credentials on the old laptop that would use my email address attached to the Work and School account. However, Azure AD and Entra ID will not let me run anything as related to my own accounts. For example, a) I can't change my own password on the Azure AD / Entra ID page. When I attempt to change my password, I get a writeback error: SSPR_0010. However, you need to buy Entra ID Connect to correct this. Entra ID is a trial version to my Azure AD sign-ins so even if I exist in Entra ID and Microsoft is moving to Entra ID, why am I being forced into purchasing things to correct this issue? b) I can't enroll into Microsoft 365 Business Basic using my Work and School Account email address. The enrollment sends me to a blank screen and never enrolls. If I try a second time using my Work and School email address, I get an error that states I have to use a different email address. It seems someone besides me is using my email address here for account access because the Work and School account holds a Visio (web only version) and my Personal account holds a real one that I can't use on my new mini which uses my own email address and not gmail.com or outlook.com. c) Edge creates a blank profile on its own that does not have my profile information in it if I do not use my Work and School account email address to sign-in. I keep losing my profile on first tab load in Edge. d) The Windows 11 Pro license on my new mini request my Work and School account login. The two have nothing to do with each other except that the email address is the same for account purposes. At one point, this CoPilot screen that says "Coming Soon" did not appear and now it is back again. Can you please assist in resolving this issue? I should technically be able to remove my Windows Live account that uses my Work and School email address and recreate it on a new machine without this much of a hassle.
Bridge 2 Cloud- Migrating CSP Partner During Term
We have a customer wanting to move from their existing CSP provider to ourselves, but they have a ‘bridge 2 cloud’ promotion of 40% discount which is mid-term. Can you confirm whether we could leverage this offer for them if we migrated their services to us, and whether the discount would carry over to us and be honoured so that they are not affected. If so, is there a particular process that would need to be followed or is it the same as migrating any CSP customer? Many thanks,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 respuestaMaking your public folder migrations faster and more reliable
The key for a successful migration (of any type) is to ensure that source data is in a healthy condition. Public folder migrations are no different, especially if you have been using public folders for years. Orphaned ACLs, mis-matched Mail Enabled Public Folder objects (MEPF’s), or corrupted dumpster folders can cause public folder migrations to slow down considerably, if not fail altogether.
Public Folder Migration Failed
We have a problem migrating public folders from an Exchange 2019 OnPremise to an Exchange Online. We followed the Microsoft guide: Batch migrate Exchange Server public folders to Microsoft 365 or Office 365 | Microsoft Learn We get to step 7. When completing the PublicFolderMigration job, the status changes to “Completing” and then to “Failed”. The error message in the EXO Shell is: Status: Failed Message: Error calling “net.tcp://be1p281mb2001.deup281.prod.outlook.com:9821/Microsoft.Exchange.MailboxReplicationService BE1P281MB2001.DEUP281.PROD.OUTLOOK.COM (15.20.8207.17 ServerCaps:FFFFFFFF, ProxyCaps:1FFFFFFFFFFFFFFFC7DD2DFDBF5FFFFFCB07EFFF, MailboxCaps:, legacyCaps:FFFFFFFF)”. Error details: The communication object System.ServiceModel.Channels.ServiceChannel cannot be used for communication because it is in a Faulted state. --> The communication object System.ServiceModel.Channels.ServiceChannel cannot be used for communication because it is in a Faulted state. Does anyone have an idea what this error means? We have already removed and restarted the entire migration, but the same error occurs again.
