Outlook API Not Showing Complete Address After Changes

Max Mueller 31

When I make changes to any attributes of an address on the Outlook people website, and then retrieve that contact through the API, it only shows the updated attribute of the physicaladdress. However, it should show the entire address. As you can see in the screenshots, I only changed the ZIP code, but when I call that contact, it only shows the updated attribute of the address. Can someone please help? Is there any way to report this? Our integration with Outlook is currently stuck due to this issue.

screenshot-2022-08-23-125406

screenshot-2022-08-23-125543

References:
https://learn.microsoft.com/en-us/graph/api/resources/physicaladdress?view=graph-rest-1.0
https://learn.microsoft.com/en-us/graph/api/contact-get?view=graph-rest-1.0

Endpoint:
https://graph.microsoft.com/v1.0/me/contacts/{contactID}

Ivanka 11 Reputation points

2022-09-05T08:38:49.99+00:00

Unfortunately I have this problem too, how can we report this?

5 answers

Kristoffer 11 Reputation points

2022-09-20T10:08:42.657+00:00

The problem still persist, can someone help please?
Please sign in to rate this answer.

1 person found this answer helpful.
AtulThorat-MSFT 391 Reputation points

2022-09-20T11:13:57.543+00:00

Hi @Kristoffer ,

Support case on this issue has already been raised and our team has escalated it to Microsoft engineering team for further investigation and resolution. We will keep you posted on the update based on feedback from Microsoft engineering team.
Sign in to comment
AtulThorat-MSFT 391 Reputation points

2022-08-24T13:22:37.257+00:00

Hi @Max Mueller ,

Hope you are doing well.

We tried to replicate your scenario at our end but we are not able to reproduce this issue.

The graph API contact-get is working as expected. Please see below screenshot for the same.

So this seems to be tenant specific issue and some filter setting might be done at exchange admin level.

To address this issue please raise a case with MS Support team aad.portal.azure.com from your tenant where you are facing issue respective team will provide exclusion for your tenant.

Hope this helps.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have further questions about this answer, please click "Comment".
Please sign in to rate this answer.
Max Mueller 31 Reputation points

2022-08-24T16:30:43.76+00:00

Thanks for taking time and trying out.
But you made changes to all address inputs, please now only change the street to "Lane 3", and call the API once again, I think it only returns the street instead of the whole object.

AtulThorat-MSFT 391 Reputation points

2022-08-24T19:10:33.293+00:00

Hi @Max Mueller ,

Hope you are doing well.

I change the street to "Lane 3", and call the API once again, It has returned the updated street value and rest of the fields are same for whole object.

Please find below screenshot for the same.

Hope this helps.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have further questions about this answer, please click "Comment".

Max Mueller 31 Reputation points

2022-08-25T10:09:39.957+00:00

But you changed the other fields aswell, as I mentioned you should change only one field, let's say only street, not ZIP nur city, country or state, just change the street.

Max Mueller 31 Reputation points

2022-08-30T10:56:43.477+00:00

@AtulThorat-MSFT would you please look into this issue once more, as you can see @Glen Scales has also the same problem, I really appreciate it.

AtulThorat-MSFT 391 Reputation points

2022-09-08T16:54:37.44+00:00

Hi @Max Mueller ,

I would like to update you that a support case on this issue has already been raised and our team has escalated it to Microsoft engineering team for further investigation and resolution. We will keep you posted on the update based on feedback from Microsoft engineering team.

Thanks.
Sign in to comment
Glen Scales 4,431 Reputation points

2022-08-25T00:33:25.117+00:00

@AtulThorat-MSFT you need to test this by doing a patch on an existing contact eg

What is happening is when you update one property in the collection it's deleting all the other existing properties in the address collection which shouldn't really happen so it's either a bug or something that needs to be documented.
Please sign in to rate this answer.
Max Mueller 31 Reputation points

2022-08-25T10:15:34.14+00:00

@Glen Scales see! that's crazy! how can we document this, or report it, it has broken our software integration to Outlook contacts..

Glen Scales 4,431 Reputation points

2022-08-26T00:01:20.72+00:00

This should be the correct place to report it I'm sure once @AtulThorat-MSFT can reproduce it then a bug can be filed your other avenue is to go down opening a support ticket (you should get more feedback that way on expected time frames for a fix). If it something that previously worked and suddenly stopped working that's important detail to add and if you can correlate the time it stopped working then it easier for them to correlate that to what updates on the backend that might have broken it.
Sign in to comment
Srinivasa Rao Darna 6,686 Reputation points Microsoft Vendor

2022-10-11T11:43:15.787+00:00

Hi @Max Mueller ,

This is expected behavior, when you update structured properties such as homeAddress, you must pass the full property set. Documentation has been updated today with same contact-update.

Any property of type PhysicalAddress have to pass full property set as given the example snippet, failing to pass any property will update with null.

Hope this helps.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Please sign in to rate this answer.
Kristoffer 11 Reputation points

2022-10-11T15:03:09.333+00:00

The problem is not whether if the value of property is null or not, well infact the property itself is missing, that's the problem!!!
Even if you change the values in the Outlook interface and retrieve the data via API it returns the physicaladdress partially.
Now is 2 months and the problem is still there!
Sign in to comment
Alice 6 Reputation points

2023-01-05T18:02:32.62+00:00

Could someone report this problem to Microsoft? It still persists.
Please sign in to rate this answer.
Glen Scales 4,431 Reputation points

2023-01-16T23:47:06.7833333+00:00

At the time I did follow it up with Microsoft and created a support issue (Case #:32787094 if anybody is interested) the result was that this was by design they did update the documentation to reflect this "When you update structured properties such as homeAddress, you must pass the full property set.".

My understanding is the graph.physicalAddress is a complexType and on the Contact entity things like homeaddress,businessaddress and otheraddress are structural properties (or this type) http://docs.oasis-open.org/odata/odata/v4.0/errata03/os/complete/part3-csdl/odata-v4.0-errata03-os-part3-csdl-complete.html#_Structural_Property. So when you update these type of properties in the Graph you need to update the full set.

Alice 6 Reputation points

2023-01-18T16:17:03.9966667+00:00

@Glen Scales As stated by the OP, when updating a property, it only returns the changed property, even if you pass all properties while updating. Furthermore, he changed the address on the Microsoft website, not through the API, but when he called the API, he only received the postal code of that object.

Glen Scales 4,431 Reputation points

2023-01-18T23:55:01.13+00:00

Alice sorry if i misunderstood, there's a lot going on in this thread so it probably needs some clarification if your going to get some sort of traction. The group in question that this thread is sitting in is the Microsoft Graph Contact API so what most readers would expect is that your using the Graph API to do the update and read of the contact.

What's important with any problem is that somebody can reproduce it so it can be troubleshooted further. In the thread already there has been multiple attempts by a few people including myself to do this and the one issue we found was around updating the structured property. It sounds like this wasn't the root cause and you have a different problem so it would be useful for all involved if you could add some more details. Eg specially how the update is being made if its is using the Graph API can you reproduce the problem in the Graph Explorer and show the patch request you make and the response you get. If your not making the update via the Graph API how are you doing it ? (eg if your using an Outlook Add-in that would be via office.js, in that case there is a separate tag and group that should look at this). The original Op mentions the Outlook people website and then mentions and integration with outlook and references the Graph API, In the thread Atul already tried the reproduction of updating via the People node in Outlook on the Web and reading it back with the Graph and didn't find an issue (I tried the same thing and it works fine) . The version of mail is also important eg is it the Office365 or is it the retail version of Outlook (eg Hotmail, outlook live etc)

One further complication is if your seeing the behaviour in a particular client ? eg is it Outlook Mobile, Desktop, Mac, Outlook on the Web, "Project Monarch". These clients use different API's and protocols to do sync so it's possible if there is a bug its on the client side and not in the Graph or it maybe in the interaction between the two.

Alice 6 Reputation points

2023-01-24T11:49:17.9666667+00:00

@Glen Scales What I had done was update an existing contact on Outlook on the web and retrieve the same contact using the Graph API. I am not sure if any other software or API has the same problem..
I also noticed that you replied to @AtulThorat-MSFT here and explained the problem with a screenshot.

Glen Scales 4,431 Reputation points

2023-01-24T23:47:49.32+00:00

@Alice

What I had done was update an existing contact on Outlook on the web

In Outlook on the Web it has it's own private API (which mostly just a JS version of EWS) but it doesn't use the Microsoft Graph to do the update of the contact. If the problem is being cause by a bug in Outlook on the web the best group/tag would be [https://learn.microsoft.com/en-us/answers/tags/131/office-outlook . I tried again using your issue description and I can't reproduce your issue and given the frequency people update contacts it should be something that would float to the top of the support issues. What might be happening is that a lot of other apps sync contacts these days using a number of different mechanisms so you might have a bad actor app in the mix somewhere that is causing the problem. The best suggestion I have is that you should log a issue with Microsoft support and have them look at the problem in your tenant (I know this is a pretty painful process having gone though it a couple of times) but it maybe the only way of finding the root cause.

If you want to do some more troubleshooting yourself which i would also recommend here are some tips. if you use fiddler [https://www.telerik.com/fiddler to do a capture of when you make the change in Outlook on the Web you can see both the request it makes and also you can see the full response with all the props of the updated contact eg

So in the above capture the actual update request that Outlook on the Web makes is in the x-owaurlpostdata header which if you then URLDecode it and load it into a JSON parser should look something like

In the response you see the updated properties of the contact object.

This type of debugging helps to rule in/out a couple of things eg you can see exactly what OWA did and the result of that operation. So if the bug resides on the OWA side it will show up here

You can see from the UpdatePersonaRequest that on the backend they are parsing the address parts from a single update string (that is constructed by the client) so it could be something in your particular address update that's causing the problem in this operation (eg outside of whatever testing they do on It).

If the problem is being cause by another application that's a bit harder to troubleshoot but in theory if your seeing a loss of data within the address property in the Graph that should be also visible in OWA (there is client caching involved but after 15 minutes if you logoff/logon you should see the address information missing in OWA to reflect what you see in Graph).

Alice 6 Reputation points

2023-01-30T15:03:06.14+00:00

You couldn't reproduce the error because you didn't follow the steps to reproduce it.
Here are the correct steps:

Go to the Outlook website.

Create a contact with a name and full address.

Refresh the page.

Edit the contact.

Update only one field, e.g. the street.

Call the same contact using the Graph API.

It shows only the street value instead of the full address.

Glen Scales 4,431 Reputation points

2023-01-31T00:04:34.8433333+00:00

I did follow that reproduction and also if you look at Atul response he did the same thing. I can however now reproduce the issue and when i now look in fiddler i can see Microsoft have made a change on the backend (in my tenant this occurred in the last week) so in Outlook on the Web as to how contacts are updated here is the latest capture

So basically it looks like they have gone from updating the contact directly in the Exchange Store to updating it via https://apc.loki.delve.office.com/api/v1/peoplegraph/contact some sort of new people graph that syncs back to exchange (and other things I guess). So this problem is not really a Graph issue as such as I see the same problem when i access the contact using MAPI so the problem seems to me lies in the way this new peoplegraph mechanism syncs back to the Exchange Store. The Graph and other Exchange API's just show you what the raw properties values are in Exchange which this new thing is not syncing to correctly. Eg it affects all the client API's an update in Outlook on the Web will show okay in OWA but viewing the contact in the desktop version of Outlook or Outlook Mobile shows data loss.
Sign in to comment