Forum Discussion
Migrate to exchange online - NotFoundPermanentException
- Sep 01, 2020
Ich habe es gelöst. Indem ich die User aus dem Sync nahm, sie im Azure AD löschte und erneut gesynct hatte.
Hello Stefan Kießig,
I think we are facing a disconnect due to responses being translated. You can also post your issue at answers.microsoft.com for more personalized support in your language.
Assuming you are performing exchange hybrid migration via office 365 batches, I will try to summarize our conversation:
When you run from powershell connected to exchange online :
1. Get-Recipient -IncludeSoftDeletedRecipients 'ExchangeGUID value from error' | ft RecipientType,PrimarySmtpAddress,*WhenSoftDeleted*
The response you get is:
RecipientType PrimarySmtpAddress WhenSoftDeleted
------------- ------------------ ---------------
MailUser user@contoso.de
This output means that the 'ExchangeGUID value from error' is associated with the mail user: user@contoso.de
2. Next, When you run get-mailuser -identity user@contoso.de | fl *guid* , with the same mail user returned in step 1. You don't see the same exchange GUID ? or there is no ExchangeGUID at all ?
Check if same user is present in soft deleted mail users as well:
get-mailuser -softdeleted
3. Next, on your on-premises exchange powershell when you run:
get-mailbox -Identity user@contoso.de | fl *guid*
You get an exchange GUID, for example 1234-5678-54321
Now from exchange online powershell run the following command:
Get-Recipient -IncludeSoftDeletedRecipients '1234-5678-54321' | ft RecipientType,PrimarySmtpAddress,*WhenSoftDeleted*
Do you get any response from this command ?
There are a few moving parts here, You may also be facing an issue with duplicate users, were these 3 users created in office 365 directly at some point before installing aadconnect ? Please check active users and deleted users for any duplicates as well.
Thanks
Hello harveer singh
Get-Recipient -IncludeSoftDeletedRecipients 'ExchangeGUID value from error' | ft RecipientType,PrimarySmtpAddress,*WhenSoftDeleted*
did not yield any results
- Stefan KießigSep 01, 2020Brass Contributor
Ich habe es gelöst. Indem ich die User aus dem Sync nahm, sie im Azure AD löschte und erneut gesynct hatte.