Merge pull request #28287 from microsoftgraph/main

Auto Publish – main to live - 2026-02-21 00:30 UTC

Author: learn-build-service-prod[bot]

.github/prompts/author-api-docs.prompt.md

@@ -260,6 +260,51 @@ After updating What's new, update the appropriate TOC mapping file to make new d
 - Complex types should NEVER be in the `resources` array
 - API methods are NOT typically added to TOC - they auto-generate from the resource's Methods table
 
+### Common Process: Handling Code Snippets in Examples
+
+**DO NOT manually add SDK snippets or related artifacts to the Example request section**, including:
+- `# [HTTP](#tab/http)` tab declarations
+- Tab boundary markers (`---`)
+- Language-specific SDK snippet includes (e.g., `[!INCLUDE [sample-code](../includes/snippets/csharp/...)]`)
+- SDK snippet files in the includes folder
+
+**Why:** SDK snippets are automatically generated and managed separately via automation.
+
+**For new files:** Include only HTTP request examples using `msgraph-interactive` (for URLs without an ID placeholder, e.g., `https://graph.microsoft.com/v1.0/users`) or `http` language identifier. No tabs or SDK includes.
+
+**For existing files:** Follow the established pattern. If the file has no SDK snippets, add only HTTP examples. Do not introduce SDK snippets to files lacking them.
+
+**Example HTTP-only format:**
+
+```markdown
+### Request
+
+<!-- {
+  "blockType": "request",
+  "name": "create_user"
+}-->
+
+\```msgraph-interactive
+POST https://graph.microsoft.com/v1.0/users
+Content-type: application/json
+
+{
+  "accountEnabled": true,
+  "displayName": "Adele Vance",
+  "mailNickname": "AdeleV",
+  "userPrincipalName": "AdeleV@contoso.com",
+  "passwordProfile": {
+    "forceChangePasswordNextSignIn": true,
+    "password": "xWwvJ]6NMw+bWH-d"
+  }
+}
+\```
+```
+
+**When promoting from beta to v1.0:** Remove SDK snippets and tab markers for files copied from beta; keep only HTTP examples (see [Scenario 2](#scenario-2-promote-apis-from-beta-to-v10)).
+
+---
+
 ### Reference Standards: Namespace Qualification
 
 Microsoft Graph APIs use namespaces to organize types and operations. Understanding namespace qualification is critical for correct documentation.
@@ -406,6 +451,27 @@ The tooling that generates doc stubs typically assumes **all EntityType resource
 
 **Remember:** The presence of a doc stub does NOT mean the operation is supported. Always verify against the API.md file and Documentation Plan.
 
+#### Handling missing doc stubs
+
+**Important:** If doc stubs are missing for APIs/resources/permissions mentioned in the Documentation Plan or API.md file, DO NOT attempt to regenerate them manually.
+
+**What to do:**
+1. Identify which specific files are missing based on the Documentation Plan and API.md
+2. Inform the author about the missing files
+3. Ask the author to provide the missing doc stubs from Graph Studio or the autogeneration process
+4. Wait for the author to add the missing files to `temp-docstubs` before proceeding
+
+**Example notification to author:**
+"The Documentation Plan references [resource/API name], but I don't see the corresponding doc stub file in temp-docstubs. Please add the following missing files:
+- [list specific missing file names]"
+
+**Do NOT:**
+- Attempt to create doc stub files from scratch
+- Proceed with documentation without the required doc stubs
+- Assume missing files mean the feature should not be documented
+
+**Remember:** Doc stubs contain critical autogenerated metadata (permissions, namespace, type references, JSON representations) that should not be manually created.
+
 ### Supporting updates to consider
 
 For all API changes, include the following updates as applicable:
@@ -490,6 +556,7 @@ For each copied file, make the following updates:
    - This include should be deleted for v1.0 GA documentation
 
 2. **Remove SDK snippet links** from the Example Request section:
+   - See [Common Process: Handling Code Snippets in Examples](#common-process-handling-code-snippets-in-examples) for complete guidance
    - Remove the `# [HTTP](#tab/http)` tab
    - Remove the tab boundary marker (`---`)
    - Remove all language-specific SDK snippet include links (e.g., `[!INCLUDE [sample-code](../includes/snippets/csharp/...)]`)
@@ -1266,7 +1333,8 @@ Before working on any file, apply these rules to both resource and API files:
      - Example: An API that returns multiple object types might return an `@odata.type` property for each object to help differentiate each object type in the collection
 
 9. **Examples section:**
-   - Leave this section unchanged
+   - Follow HTTP-only example formatting (see [Common Process: Handling Code Snippets in Examples](#common-process-handling-code-snippets-in-examples))
+   - Do NOT manually add SDK snippet links, tab markers, or language-specific includes
    - When adding a new property to a resource, update example request and response bodies for that resource where applicable
 
 ### To add new properties to existing resources
@@ -1716,6 +1784,8 @@ Before completing any authoring task, verify:
 - [ ] Examples section: Copy examples from API.md and format as applicable
 - [ ] Examples section: Request URL matches URL in "HTTP request" block except full URL
 - [ ] Examples section: New properties reflected in request/response bodies where applicable
+- [ ] Examples section: SDK snippets NOT manually added (see [Common Process: Handling Code Snippets in Examples](#common-process-handling-code-snippets-in-examples))
+- [ ] Examples section: Only HTTP examples included for new files
 
 **For all files (new and updated):**
 - [ ] All required sections are present and in correct order

.github/workflows/changelog-validation.yml

@@ -10,12 +10,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v4
-      - name: Validate JSON
-        uses: docker://orrosenblatt/validate-json-action:latest
-        env:
-          INPUT_SCHEMA: /changelog/Changelog.Schema.json
-          INPUT_JSONS: /changelog/Manual.NonWorkloadChanges.json,/changelog/Microsoft.AAD.Reporting.json,/changelog/Microsoft.Analytics.json,/changelog/Microsoft.BitLocker.json,/changelog/Microsoft.CloudManagedDesktop.json,/changelog/Microsoft.Compliance.Ediscovery.json,/changelog/Microsoft.DirectoryServices.json,/changelog/Microsoft.EducationAssignment.json,/changelog/Microsoft.Excel.json,/changelog/Microsoft.Exchange.json,/changelog/Microsoft.FileServices.json,/changelog/Microsoft.HybridAuthentication.json,/changelog/Microsoft.IdentityGovernance.AccessReviews.json,/changelog/Microsoft.IdentityProtectionServices.json,/changelog/Microsoft.Intune.json,/changelog/Microsoft.MicrosoftSearch.json,/changelog/Microsoft.NAV.json,/changelog/Microsoft.O365Reporting.json,/changelog/Microsoft.Office.Tasks.json,/changelog/Microsoft.OneNote.json,/changelog/Microsoft.PrintService.json,/changelog/Microsoft.Search.json,/changelog/Microsoft.SharePoint.json,/changelog/Microsoft.Skype.Calling.json,/changelog/Microsoft.SubscriptionServices.json,/changelog/Microsoft.Teams.Core.json,/changelog/Microsoft.Teams.GraphSvc.json,/changelog/Microsoft.ThreatAssessment.json,/changelog/Microsoft.Todo.json,/changelog/Microsoft.People.json
-      - name: Validate Schema with Script
+      - name: Validate Changelog JSONs with Schema
         run: |
-          ./validate-changelog-json.ps1
+          ./scripts/validate-changelog-json.ps1
         shell: pwsh

.github/workflows/temp-docstubs-validation.yml

@@ -0,0 +1,16 @@
+name: Validate temp-docstubs folder
+
+on: [pull_request, push]
+
+permissions:
+  contents: read
+
+jobs:
+  verify-temp-docstubs:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Validate temp-docstubs folder
+        run: |
+          ./scripts/validate-temp-docstubs.ps1
+        shell: pwsh

api-reference/beta/resources/enums-security.md

@@ -1022,6 +1022,7 @@ Namespace: microsoft.graph.security
 |sPRuntimeAccessControl|
 |sPSharingNotifyUser|
 |sPSharingGenerateIncidentReport|
+|restrictWebGrounding|
 
 ### executionMode values
 

api-reference/beta/resources/restrictaccessactionbase.md

@@ -22,7 +22,7 @@ Use [restrictaccessaction](../resources/restrictaccessaction.md) to explicitly r
 
 |Property|Type|Description|
 |:---|:---|:---|
-|action|microsoft.graph.security.dlpAction|The type of DLP action. Inherited from [dlpActionInfo](../resources/dlpactioninfo.md).The possible values are: `notifyUser`, `blockAccess`, `restrictWebGrounding`,  `deviceRestriction`, `browserRestriction`, `unknownFutureValue`, `restrictAccess`, `generateAlert`, `generateIncidentReportAction`, `sPBlockAnonymousAccess`, `sPRuntimeAccessControl`, `sPSharingNotifyUser`, `sPSharingGenerateIncidentReport`. Use the `Prefer: include-unknown-enum-members` request header to get the following values from this [evolvable enum](/graph/best-practices-concept#handling-future-members-in-evolvable-enumerations): `restrictAccess` , `generateAlert` , `generateIncidentReportAction` , `sPBlockAnonymousAccess` , `sPRuntimeAccessControl` , `sPSharingNotifyUser` , `sPSharingGenerateIncidentReport`.|
+|action|microsoft.graph.security.dlpAction|The type of DLP action. Inherited from [dlpActionInfo](../resources/dlpactioninfo.md). The possible values are: `notifyUser`, `blockAccess`, `deviceRestriction`, `browserRestriction`, `unknownFutureValue`, `restrictAccess`, `generateAlert`, `generateIncidentReportAction`, `sPBlockAnonymousAccess`, `sPRuntimeAccessControl`, `sPSharingNotifyUser`, `sPSharingGenerateIncidentReport`, `restrictWebGrounding`. Use the `Prefer: include-unknown-enum-members` request header to get the following values from this [evolvable enum](/graph/best-practices-concept#handling-future-members-in-evolvable-enumerations): `restrictAccess`, `generateAlert`, `generateIncidentReportAction`, `sPBlockAnonymousAccess`, `sPRuntimeAccessControl`, `sPSharingNotifyUser`, `sPSharingGenerateIncidentReport`, `restrictWebGrounding`.|
 |restrictionAction|microsoft.graph.security.restrictionAction|Action for the app to take. The possible values are: `warn`, `audit`, `block`.|
 
 ## Relationships