Hi
I just use the UPDATE API place to set the tags. The response I got from the server is 200 and in the response body the tags has been updated correctly.
However when I make the GET request, the place tags is empty Array (nothing changed at all). May I know what happened? Does it take time to update data for the place?
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
Same here :
Here's my place in the admin center :

Here's what /beta/places/microsoft.graph.room is returning :
"id": "48c67636-fcc8-*****-****-*******",
"displayName": "Gehry",
"address": null,
"geoCoordinates": null,
"phone": "",
"nickname": "Gehry",
"emailAddress": "gehry@********.com",
"building": null,
"floorNumber": null,
"floorLabel": null,
"label": null,
"capacity": 4,
"bookingType": null,
"audioDeviceName": null,
"videoDeviceName": null,
"displayDeviceName": null,
"isWheelChairAccessible": false,
"tags": []
},
You can see that both names and capacity aren't matching.
Now, here's what /beta/users/cad689f4-*****-****-****-********/findrooms returns :
{
"name": "GehryRRR",
"address": "gehry@*******.com"
},
Either graph is returning old data, either it is not the same object, and I don't know where to modify it.
Another option is that Graph isn't updating: I've created a room named "pony", which doesn't appear with microsoft.graph.room but does appear with findRooms.
@ ChristopheMaingard btw do you know is there any way to add tags into the place by the admin center tool? Right now I got it working by using the API PLACE UPDATE but it's not convenient to manage it in the future.
Also in the Room resource we can add Custom attributes but I can't figure out any way to fetch them by using Microsft Graph Api....

@bang-reactron I'm afraid I have no idea
Hey @bang-reactron the M365 admin portal has not been updated yet to reflect the new properties supported in Exchange by the Graph API.
Was there ever any determination made regarding whether the issue was old data being returned, or if the room objects being returned by the places/microsoft.graph.room API differ from the ones that are being updated and/or returned by the me/findRooms API?
@ChristopheMaingard @bang-reactron @dtfischer When you create a new room it takes about 48 hrs to show up in our Places API. I know this is inconvenient and we hope to have this fixed within the next couple of months. Data that you add in the M365 portal or using set-user,set-mailbox or GET using FindRooms API will also take 48 hrs to replicate in our Places API. The reason for this is that one data is coming from AD while the other is coming from a tenant shard (tenant mailbox). We then need to sync AD information to the tenant shard. This is where we see the 48 hr delay. In the future we will solely use the Tenant shard and do inline updates to make this faster.
Most helpful comment
@ChristopheMaingard @bang-reactron @dtfischer When you create a new room it takes about 48 hrs to show up in our Places API. I know this is inconvenient and we hope to have this fixed within the next couple of months. Data that you add in the M365 portal or using set-user,set-mailbox or GET using FindRooms API will also take 48 hrs to replicate in our Places API. The reason for this is that one data is coming from AD while the other is coming from a tenant shard (tenant mailbox). We then need to sync AD information to the tenant shard. This is where we see the 48 hr delay. In the future we will solely use the Tenant shard and do inline updates to make this faster.