Merging changes synced from https://github.com/MicrosoftDocs/microsoft-365-docs-pr (branch live)

Author: Learn Build Service GitHub App

microsoft-365/admin/TOC.yml

@@ -559,7 +559,11 @@ items:
     - name: Troubleshoot
       href: /office/troubleshoot/  
     - name: Contact support
-      href: get-help-support.md
+      items:
+        - name: Get support for Microsoft 365 for business
+          href: get-help-support.md
+        - name: Case creation and diagnostic data
+          href: support-diagnostic-information-collection.md
     - name: Find support phone numbers
       href: https://support.microsoft.com/topic/customer-service-phone-numbers-c0389ade-5640-e588-8b0e-28de8afeb3f2#ID0EBBD=signinorgid
     - name: Navigation guide

microsoft-365/admin/support-diagnostic-information-collection.md

@@ -0,0 +1,85 @@
+---
+title: "Understanding Microsoft 365 case creation and diagnostic data access"
+ms.author: camillepack
+author: camillepack
+manager: scotv
+ms.date: 04/07/2025
+audience: Admin
+ms.topic: concept-article
+ms.service: microsoft-365-business
+ms.localizationpriority: medium
+ms.collection:
+- Tier1
+- scotvorg
+- Adm_O365
+- Adm_TOC
+description: "Learn about the diagnostic data Microsoft 365 Support engineers access to resolve support cases, including consent, data categories, retention periods, and logging details."
+---
+
+# Understanding Microsoft 365 case creation and diagnostic data access
+
+The purpose of this article is to inform Microsoft 365 customers about the type of information that Microsoft Support engineers may collect and use in order to resolve a support case.
+
+## Consent for diagnostic information
+
+When you [create a support request](get-help-support.md), you consent to allow a Microsoft Support engineer to remotely run diagnostics on the Microsoft 365 subscription(s) associated with your request. This access allows them to collect diagnostic information that enables them to troubleshoot and solve your problem.
+
+## How long does Microsoft have this access?
+
+Access is removed automatically when your support request is closed. If your request is still open, access is removed 30 days from the date of request creation, and you will be prompted to provide access again. If you have multiple requests open, the access expires 30 days from the date of creation of the latest request.
+
+Depending on the nature of your support request, the data that Microsoft can access would belong under one or more of the following categories:
+
+- **Support Data** – All data provided to Microsoft by the customer as part of a customer engagement to obtain support services.
+  - Examples
+    - Support requests from customers and phone conversations, online chat sessions, or remote assistance sessions between support professionals and customers
+    - Case notes and/or records related to support requests from customers
+    - Data provided to Microsoft by the customer as part of support activities
+
+- **Account Data** – Contact and billing/purchase/payment/license information.
+  - Examples
+    - Customer’s provisioning information
+    - Account configuration and billing data
+    - Tenant administrator contact information (for example, tenant administrator’s name, address, e-mail address, phone number)
+    - This also includes Licensing and Purchase Information.
+
+- **System Metadata** – Data generated in the course of running the service.
+  - Examples
+    - Event Logs
+    - Access Control Logs
+    - Account information belonging to Microsoft operations personnel
+    - Microsoft server names/server IPs
+    - Server patching and vulnerability data
+    - Service configuration data
+    - Telemetry (on-prem or cloud)
+
+- **Organization Identifiable Information (OII)** – Data that can be used to identify a particular tenant/deployment/organization (generally config or usage data)
+  - Examples
+    - Tenant ID (non-GUID)
+    - TenantID (GUID) – due to the existence of many out of boundary TenantID to name mapping tables
+    - Tenant usage data
+    - Tenant IP Addresses (IPv4) such as tenant’s firewall IP address
+    - Global Prefix and Subnet ID (first 64 bits of IPv6 address)
+    - Tenant Domain name in e-mail address (joe@**contoso.com**)
+    - Mapping of organizational GUID to organization
+
+- **End User Identifiable Information (EUII)** – Data that directly identifies or could be used to identify the authenticated user of a Microsoft service.
+  - Examples
+    - User-specific IP address (IPv4)
+    - User Principal Name (joe@company.com)
+    - Address Book Data
+    - User’s machine Name
+    - SIP URI
+
+- **End User Pseudonymous Identifiers (EUPI)** – An identifier created by Microsoft tied to the user of a Microsoft service.
+  - Examples
+    - User GUIDs or PUIDs
+    - Session IDs
+
+## How long is diagnostic data retained in Microsoft systems?
+
+Microsoft retains diagnostic data for up to 28 days after it is collected. After this period, the data is deleted.
+
+## Where is support activity on a customer tenant logged?
+
+Activity performed on a customer tenant is available under Microsoft Entra Audit logs.

microsoft-365/commerce/licenses/manage-license-requests.md

@@ -26,6 +26,7 @@ ms.custom:
 search.appverid: MET150
 description: "Learn how to review and approve or deny license requests for products and services from users in the Microsoft 365 admin center."
 ms.date: 04/07/2025
+ROBOTS: NOINDEX, NOFOLLOW
 ---
 
 # Manage self-service license requests in the Microsoft 365 admin center
@@ -86,9 +87,8 @@ When you return to the **Requests** list, you see the message **You're using you
    - A grayed-out option typically signifies that the security groups are either unlicensed or not yet configured.
    - For more information about how to assign licenses to a security group, see [Assign or unassign licenses to a group using the Microsoft 365 admin center](../../admin/manage/manage-group-licenses.md)
    - When multiple security groups are available, select the one to which you want to assign licenses.
-7. In the text box at the bottom of the pane, type a message (optional). The user receives an email containing either the default message or your customized message.
-8. When you're finished, select **Submit**. The details pane shows the details of the request.
-9. Close the details pane. Users receive an email that says their request was approved or denied.
+7. When you're finished, select **Submit**. The details pane shows the details of the request.
+8. Close the details pane. Users receive an email that says their request was approved or denied.
 
 ## Share a license request by email
 
@@ -101,7 +101,7 @@ If you don't have the authority within your organization to make decisions about
 5. In the **Share license request details** pane, type an email address, then select the recipient name.
    > [!NOTE]
    > You can select more than one recipient, but if the email that you entered doesn't resolve into a user name, you can't share the request.
-1. To personalize the email, select the **Include a personalized message** check box. Type a **Subject** and **Message** in the corresponding fields.
+1. To personalize the email, select the **Include a personalized message** check box, then type a **Message**.
 7. When you're finished, select **Share request**.
 
 ## Related content

microsoft-365/frontline/TOC.yml

@@ -32,6 +32,8 @@ items:
         href: flw-setup-microsoft-365.md
       - name: Choosing between dynamic and static frontline teams
         href: frontline-team-options.md
+      - name: Deploy frontline teams with flexible membership
+        href: deploy-flexible-membership-teams-at-scale.md
       - name: Deploy frontline dynamic teams at scale
         href: deploy-dynamic-teams-at-scale.md
       - name: Deploy frontline static teams at scale with PowerShell