Office 365 Outlook Client Contact Read Only after G Suite migration

Hi Ryan,

Welcome to post your concern in our category.

You may first try to change your contact list permission to see if it works. Right click the contact list to go to properties, click Permission tab, try to change the permission to check the result.

If it doesn’t help, since contact works well in web side, this issue may be caused by Outlook desktop. I suggest you try the following options to see if there is any difference:

1. Open Outlook in safe mode and see if you can edit the contacts.

2. Try to repair Outlook client.

3. Download Microsoft Support and Recovery Assistant for Office 365 and follow the prompts to scan and fix Outlook client.

Thanks for your patience.

Regards,

Shawn

Hi Ryan,

Has your problem been solved now? Any feedback is appreciated.

Sincerely,

Shawn

I opened a ticket with MS and they advised its a global issue and gave a workaround below ( copy and paste)

You  have to modify the 0x36DA0102 Property from the Contacts folder, from the value it has (most likely 010440001000070401000000) to 010400801200070401000000 (which contains also the following flags: SharedViaExchange, SharedExchangeEver, SharedExchangeValid), or 010400001000 (which is the default value for that property, which contains no flags).

This can be modified with tools like MFCMapi. 

Further research yielded this link. It looks like a backend issue that they are trying to resolve. the workaround is not feasible as it is happening on ~120 machines

https://social.technet.microsoft.com/Forums/office/en-US/208dc680-dbb8-44c9-9c48-a3092eda639c/unable-to-edit-contacts-notes-field-in-outlook-2010?forum=outlook

Hi Ryan,

Thanks for your feedback and sharing your research on this issue.

You can refer to this article to know more detail about this fixed known issue: Unable to edit Contacts, Appointments, Meetings, or Tasks within Outlook

And I would like to make a summary here so that more people can know more about this issue.

About the cause:The reason for this phenomenon is because some items contain internet header information that causes Outlook to believe these items should not be editable. And it will affect not only contacts, appointments, meetings or tasks may also be involved.

About the fix:

a) Monthly Channel fix was released on April 29th in Version 1904 Build 11601.20144.

b) Semi Annual Channel will release ~May 14th in Version 1808 Build 10730.20340.

c) The fix for Outlook 2016, Outlook 2013, and Outlook 2010 (also known as perpetual versions) is planned for the August 13th 2019 Public Update. 

About the workarounds:

Outlook users: Create, view, and edit contacts and contact lists in Outlook.com

Office 365 users: Create, view, and edit contacts and contact lists in Outlook on the web

Fix contacts in bulk: Export all of your contacts, then import them so the internet headers are removed. This process marks the contacts as editable.

Thanks for your patience and feel sorry the inconvenience you have experienced.

Sincerely,

Hi, I have the same problem here after Gsuite to O365 migration. My Contacts are readonly for the whole company.

The trick with MFCMapi works but is not applicable to 150+ users.

Could you please provide a powershell command or something globally apply-able?

Thanks

Hi, I have the same problem here after Gsuite to O365 migration. My Contacts are readonly for the whole company.

The trick with MFCMapi works but is not applicable to 150+ users.

Could you please provide a powershell command or something globally apply-able?

Thanks

Hi GuillaumeAlive,

Thanks for post your concern in community.

Since this post is dedicated for the thread owner’s problem, I would like to suggest you post a new thread in this category, so that there will be a specific support engineer to offer help on your issue.

Thanks for your kind understanding for our work. And feel sorry for such an inconvenience.

Regards,

Shawn

Hi,

that's exactly the same problem, and same resolution on Outlook side...

I got a fix from MS to fix it for all users and will be trying it today. If it works i will post an update.

Hi Ryan, could you share the fix, just to see what MS propose?

Thanks a lot!