Merge branch 'main' into users/sumanac/changelogfornextlink

Author: MSFT-Andrea

AGENTS.md

@@ -0,0 +1,42 @@
+# Agent Quick Guide
+
+Top-level entrypoint for agents working in this repository.
+
+## Authority
+
+If this file and `.github/copilot-instructions.md` ever differ, follow:
+
+1. `.github/copilot-instructions.md`
+2. The prompt and template files it routes you to
+
+This file is intentionally thin to avoid split-brain guidance.
+
+## Read first
+
+Before doing docs work in this repo:
+
+1. Read `.github/copilot-instructions.md`
+2. Determine whether the task is **authoring/updating** or **review**
+3. Load the prompt file that `.github/copilot-instructions.md` tells you to read first
+
+## Repo map
+
+- `api-reference/*/api/` — API operation topics
+- `api-reference/*/resources/` — resource and enum topics
+- `changelog/` — API change records
+- `concepts/whats-new-overview.md` — monthly release highlights
+- `concepts/` — conceptual topics such as tutorials, conceptual overviews, guides
+- `api-reference/*/toc/toc.mapping.json` — API reference TOC mapping
+- `api-reference/*/includes/rbac-for-apis/` — RBAC include files
+- `temp-docstubs/` — temporary authoring inputs
+
+## Workflow
+
+1. Start with `.github/copilot-instructions.md`
+2. Load the correct scenario guidance
+3. Make scoped changes only
+4. Run the validation expected by the loaded workflow
+
+## Rule of thumb
+
+Do not duplicate detailed rules in this file. Keep detailed authoring, review, changelog, What's New, TOC, enum, and RBAC guidance in the files referenced by `.github/copilot-instructions.md`.

api-reference/beta/api/plannertask-post-messages.md

@@ -16,6 +16,9 @@ Namespace: microsoft.graph
 
 Create a new [plannerTaskChatMessage](../resources/plannertaskchatmessage.md) on a [plannerTask](../resources/plannertask.md).
 
+> [!IMPORTANT]
+> This method only supports creating a new chat message on a [plannerTask](../resources/plannertask.md) that already has at least one existing message.
+
 [!INCLUDE [national-cloud-support](../../includes/global-only.md)]
 
 ## Permissions

api-reference/beta/resources/verifiedidprofileconfiguration.md

@@ -14,7 +14,7 @@ Namespace: microsoft.graph
 
 [!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)]
 
-Verified ID profile configuration defining set of properties of a specific Verified ID credential. 
+Verified ID profile configuration defining set of properties of a specific [Verified ID credential](../resources/verifiedidprofile.md). 
 
 ## Properties
 |Property|Type|Description|

api-reference/v1.0/api/bookingappointment-update.md

@@ -83,12 +83,15 @@ If successful, this method returns a `204 No Content` response code. It doesn't
 
 ## Examples
 
-### Request
+### Example 1: Change the date of service
+
+#### Request
 
 The following example changes the date of service by a day.
 
 <!-- {
   "blockType": "request",
+  "name": "update_bookingappointment_date",
   "sampleKeys": ["AAMkADKnAAA=", "Contosolunchdelivery@contoso.com"]
 }-->
 ```http
@@ -110,7 +113,59 @@ Content-type: application/json
 }
 ```
 
-### Response
+#### Response
+
+The following example shows the response.
+<!-- {
+  "blockType": "response"
+} -->
+```http
+HTTP/1.1 204 No Content
+```
+
+### Example 2: Update the customers for an appointment
+
+The following example updates the customers array for a multi-customer appointment. The **customers** property is a full replacement array — include all customers that should be part of the appointment, not just the new ones.
+
+> [!NOTE]
+> - Each object in the **customers** array must include `@odata.type` set to `#microsoft.graph.bookingCustomerInformation`. Omitting this property causes the request to fail.
+> - Include customer details such as **name**, **emailAddress**, and **phone** for each entry. The API does not automatically populate these fields from the **customerId** — if omitted, they will be blank on the appointment.
+> - The **customerId** must reference a valid [bookingCustomer](../resources/bookingcustomer.md) that exists in the Booking Calendar. If it doesn't exist, create one using the [Create bookingCustomer](bookingbusiness-post-customers.md) operation.
+> - The associated [bookingService](../resources/bookingservice.md) must have **maximumAttendeesCount** greater than 1 to support multiple customers.
+
+#### Request
+
+<!-- {
+  "blockType": "request",
+  "name": "update_bookingappointment_customers",
+  "sampleKeys": ["AAMkADKoAAA=", "Contosolunchdelivery@contoso.com"]
+}-->
+```http
+PATCH https://graph.microsoft.com/v1.0/solutions/bookingBusinesses/Contosolunchdelivery@contoso.com/appointments/AAMkADKoAAA=
+Content-type: application/json
+
+{
+    "@odata.type":"#microsoft.graph.bookingAppointment",
+    "customers": [
+        {
+            "@odata.type": "#microsoft.graph.bookingCustomerInformation",
+            "customerId": "cd56bb19-c348-42c6-af5c-09818c87fb8c",
+            "name": "John Doe",
+            "emailAddress": "john.doe@example.com",
+            "phone": "313-555-5555"
+        },
+        {
+            "@odata.type": "#microsoft.graph.bookingCustomerInformation",
+            "customerId": "72f148fa-9a86-4c59-b277-f5089d9ea0e7",
+            "name": "Jane Smith",
+            "emailAddress": "jane.smith@example.com",
+            "phone": "248-555-5678"
+        }
+    ]
+}
+```
+
+#### Response
 
 The following example shows the response.
 <!-- {

api-reference/v1.0/api/chat-list.md

@@ -17,7 +17,7 @@ Retrieve the list of [chats](../resources/chat.md) that the user is part of.
 This method supports federation. When a user ID is provided, the calling application must belong to the same tenant that the user belongs to.
 
 > [!NOTE]
-> This API has a [known issue](https://microsoftgraph.visualstudio.com/Known%20Issues/_workitems/edit/40947). When this API is called with the `$expand=members` query parameter, the response returns a maximum of **25 member items**, even if a larger `$top` value is specified. This behavior differs from the expected behavior where the `$top` parameter controls the maximum number of items returned. As a result, applications that rely on `$expand=members` might not retrieve the full list of members in a single request.
+> This API currently has the following limitation: when the API is called with the `$expand=members` query parameter, the response returns a maximum of **25 member items**, even if a larger `$top` value is specified. This behavior differs from the expected behavior where the `$top` parameter controls the maximum number of items returned. As a result, applications that rely on `$expand=members` might not retrieve the full list of members in a single request.
 > The API also behaves differently in one or more national clouds. For more information, see [Implementation differences in national clouds](/graph/teamwork-national-cloud-differences).
 
 [!INCLUDE [national-cloud-support](../../includes/all-clouds.md)]