| Category | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| admin | Experience Insights Dashboard | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/misc/experience-insights-dashboard.md | For the first time, you can now see what articles your users are consuming on Su :::image type="content" source="../../media/experience-insights-teams-help-article2.png" alt-text="Screenshot: Image showing the number of help articles read and the corresponding Microsoft 365 product"::: +## Manage adoption success with actions in Experience insights ++Actions let you track the actions you take to drive user engagement and success for Microsoft 365 in your organization. You can measure the impact of your actions by analyzing how each action correlates with changes in usage, NPS, feedback, and help article views. This empowers you to make data-driven decisions and continuously improve your strategies for user engagement and satisfaction. ++The actions experience within Microsoft 365 admin center includes the following features and capabilities: ++- Add an action ++- Import multiple actions from a CSV file ++- Edit and remove previously added actions ++- Duplicate actions ++- Export the list of actions to CSV ++- View your action impact on Experience insights graphs ++- See the list of actions related to a product on the product detail card ++### Get started ++To manage actions, open the Experience Insights dashboard in the Microsoft 365 admin center, and then select the Actions tab. There are two key experiences to familiarize yourself within actions experience: ++###  ++Adding new actions ++1.     Select __Add action__. ++2.     Complete the form with the following details: ++- __Title__: Provide a distinct and descriptive title to help identify the action. ++- __Date of action__: Enter the date of that you took the action. ++- __Action type__: Select the type of action. ++- __Notes:__ Optional field to add in further description of your action. ++- __Target products__: Select one or more products associated with the action. ++3.     Once all required details are entered, select __Save__. ++  ++You can also import multiple actions from CSV.   Select __Import from CSV__ and follow the instructions for editing and uploading the file. There’s even a sample, pre-formatted CSV file that you can use to get started. ++### Viewing action impact ++Once an action is added, you can view it in the graphs in Experience insights, facilitating the analysis of how specific actions influence the data. ++1. From the __Actions__ list, select the __Target product__ for an action. This will open the product detail card. ++1. Select the Usage, Help Content, Product feedback, or Net Promoter Score tab. ++1. On the date of the action, there will be a vertical dashed line tracking the action against the graph’s data. ++ Note: You might need to change the __Date range__ to see the action. + +1. When you select the __Title__ of the action, above the vertical dashed line, you’ll get more details about the action. ++ + ## Additional resources ### View your organization's Adoption Score |
| enterprise | Engineering Direct Portal | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/engineering-direct-portal.md | + + Title: "Engineering Direct Portal in the Microsoft 365 Admin Center" +++ Last updated : 08/07/2024 ++++ms.localizationpriority: medium ++- scotvorg +- must-keep +++search.appverid: MET150 +f1.keywords: +audience: +description: Understand the new Engineering Direct Portal in the Microsoft 365 admin center and learn how to access and use its features +ai-usage: ai-assisted + ++# Engineering Direct Portal in the Microsoft 365 Admin Center ++The Engineering Direct Portal is a new feature within the Microsoft 365 admin center designed to provide Office Engineering Direct (OED) customers with an enhanced engineering experience. This article provides an overview of the portal's features, how to access it, and its functionality. ++The Engineering Direct Portal offers: ++- Delivery metrics to help highlight what OED provides and how you use the service +- Insight into support tickets that have been raised to the product group +- Self-service diagnostics to empower you with immediate insights and resolutions +- Features and diagnostics suggested by our OED customers ++> [!NOTE] +> The portal is available to all OED customers and their in-scope tenants at no additional charge. Permissions are currently granted to anyone within your tenant with an RBAC (role-based access control) **support** role. ++## Accessing the Engineering Direct Portal ++The Engineering Direct Portal is located under **Support** within the Microsoft 365 admin center. To access the portal, follow these steps: ++1. Navigate to the Microsoft 365 admin center. +1. Select **Support**. +1. Select **Engineering Direct** to enter the portal. ++ ++## Overview Page ++Once in the portal, you'll see the **Overview** page. This page contains several key elements: ++- **ACE Contact**: If you have an Advanced Cloud Engineer (ACE) assigned, you'll see an ACE tile with primary contact information. This lists your ACE email address with a clickable option to start an email. The tile won't be visible to customers without an ACE. +- **Insights: Key Metrics**: This tile lists both your engineering escalations and those that have been resolved for the last six months. An issue is considered an 'engineering escalation' once it has been raised to and assigned to a Microsoft Engineering team member (either through our support organization, or through your usage of the "Escalate to Engineering" feature). + - Total escalations include open or closed tickets + - Active escalations include only those tickets that are open +- **Customer Advisory Board (CAB)**: The CAB tile will list the last and next CAB events as well as the last and next community calls. This is informational only; registrations and calendar blockers will continue to be provided separately through existing process channels. +- **Insights: Escalation Trend Per Week by Status**: A monthly view of escalations by open and closed for the last six months. This is a focused view of all reactive issues, filtered by all issues that have a Microsoft engineering element. +- **Request A Feature**: Allows you to submit feedback or a request to the Engineering Direct Portal team. Feedback can be both related to the portal itself and its functionality, and any broader engineering features you would like to see in Engineering Direct. Feature requests submitted via this method are visible to users in your private **MyFeedback** section of the feedback portal. ++ ++## Insights Page ++The **Insights** page provides detailed metrics, visuals, and lists on both your current engineering tickets and those that have been resolved within the last six months. This could be through support or through the "Escalate to Engineering" feature. The layout of this page might differ from the screenshot. This page contains: ++1. **Total escalation metrics** ΓÇô Cumulative total of tickets escalated to product groups in the last six months. +2. **Escalate to Engineering** - Cumulative total of tickets using the Escalate to Engineering feature in the last six months. +3. **Escalations by product** ΓÇô Active engineering tickets to the product groups by service product. +4. **Escalation trend per week by status** ΓÇô Monthly view of open or closed tickets escalated to the product groups. +5. **Support vs. Escalate to Engineering** ΓÇô Visual showcasing active tickets escalated to engineering either via support or the Escalate to Engineering feature. The number in the center represents the current total active tickets. +6. **Distribution of escalation severity** ΓÇô Visual of tickets escalated to the product groups by severity. +7. **Service Requests Escalated to engineering** ΓÇô List view with filters of tickets that have been escalated to product groups: ++ - **Title** ΓÇô support ticket title + - **Created By** ΓÇô individual who opened the support ticket + - **Ticket #** ΓÇô support ticket number + - **Severity** ΓÇô ticket severity + - **Escalation date** ΓÇô date the issue was first escalated to the product groups + - **Status** ΓÇô status of the ticket escalated to the product groups. Status lists open or closed to start. + - **Escalate to Engineering ΓÇô true or false** - represents whether the customer raised the issue directly to engineering + - **Product** ΓÇô service product ++ ++## Diagnostics Page ++The **Diagnostics** page hosts diagnostic tools for self-service issue resolution within your environment. One notable tool is **Visual Mail Flow**, which helps investigate email-related issues. ++ ++### Using Visual Mail Flow ++Visual Mail Flow enables you to examine issues related to mail flow, such as email submission, group expansion, processing by transport agents (such as AntiSpam, mail flow rules, Data Loss Prevention), and delivery. ++Some common situations where Visual Mail Flow can be useful: ++- Checking the delivery status of recipients +- Determining reasons for nonreceipt of emails by certain recipients +- Understanding variations in email delivery between recipients +- Identifying mail flow rules applied to an email and their actions +- Identifying Data Loss Prevention rules applied to an email and their actions ++### Input Requirements ++To use Visual Mail Flow, you need either the email's Message ID *or* the Network Message ID. You can locate either the message ID or the network message ID by opening the email in question, go to **File** -> **Properties** -> **Internet headers**. You can parse through the headers to find either the message ID or network ID. Alternatively, you can copy/paste the entire internet header box and use a tool like [Message Header Analyzer](https://mha.azurewebsites.net/) to parse this information for you. ++> [!NOTE] +> Ensure the submitted messages are within the age range of 1 to 90 days. ++- **Message ID**: Found in the email header with the "Message-ID:" token. Users can provide this information to help investigate specific messages. Be sure to include the full message ID. This might include angle brackets (<>). Although the form varies depending on the email system, here's an example of what a message ID would look like: `<08f1e0f806a47b4ac109109ae6ef@server.domain>`. +- **Network Message ID**: Found in the email header with the "X-MS-Exchange-Organization-Network-Message-Id:" token. An example of a network message ID is `4d4c1224-7398-4e8e-949f-ce1932c4ab9d`. ++### Running the Diagnostic ++Enter either the Message ID or Network Message ID, then select **Troubleshoot** to start the diagnosis. Results are generated in approximately 30 seconds. ++### Understanding the Results ++The Visual Mail Flow diagnostic result includes: ++- **Summary**: General conclusion on the mail flow. +- **Highlights**: List of outstanding info and detected issues. +- **Recommendations**: Intelligent recommendations for resolving detected issues. ++The **Visual Mail Flow Tree** is an interactive display showing the stages an email went through, with the ability to zoom, drag, and view detailed node information. By examining the tree, you can gain a detailed understanding of how Exchange Online processed the email. In some cases, you might notice that the tree node is split into multiple child nodes. This is due to Exchange Online's bifurcation feature, which separates recipients into multiple sets to process them separately during mail flow. ++ ++### Investigating Further ++Select a tree node to view a flyout with other details, including recipients processed and node-specific properties for troubleshooting mail flow issues. The flyout contains other details for you to review and investigate. It contains a common ΓÇ£RecipientsΓÇ¥ property to show which recipients this node processed, and more node-specific properties that vary between nodes to help better troubleshoot mail flow issues. ++> [!TIP] +> Emails sent to many recipients or large groups will take a longer time to query or could time out. Querying emails with fewer recipients could improve your experience. ++ ++If Visual Mail Flow canΓÇÖt help you resolve the issue, contact Microsoft Support for further help. ++## More information ++As we roll out new features, your experience might change. ++If you would like to get help or have questions, reach out to [edfeedback@microsoft.com](mailto:edfeedback@microsoft.com) or use the feedback mechanism within the Engineering Direct Portal page. If you are encountering any technical issues, open a support ticket via your normal support channel. |
| syntex | Create A Form Processing Model | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/create-a-form-processing-model.md | You need to tag the documents to teach the model to understand the fields and ta > [!NOTE] > If a structured or freeform document processing model and an unstructured document processing model are applied to the same library, the file is classified using the unstructured document processing model and any trained extractors for that model. If there are any empty columns that match the document processing model, the columns will be populated using those extracted values. +### Set a page range for processing ++For this model, you can specify to process a range of pages for a file rather than the entire file. You do this under **Model settings**, in the **Page range** setting. By default, the **Page range** setting is empty. If no page range is provided, the entire document will be processed. For more information, see [Set a page range to extract information from specific pages](page-range.md). + ### Classification Date field -When any custom model is applied to a document library, the **Classification Date** field is included in the library schema. By default, this field is empty. However, when documents are processed and classified by a model, this field is updated with a date-time stamp of completion. +When any custom model is applied to a document library, the **Classification Date** field is included in the library schema. By default, this field is empty. However, when documents are processed and classified by a model, this field is updated with a date-time stamp of completion. When a model is stamped with the **Classification Date**, you can use the **Send an email after Syntex processes a file** flow to notify users that a new file has been processed and classified by a model in the SharePoint document library. |
| syntex | Esignature Review Sign Requests | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/esignature-review-sign-requests.md | If you review the document and donΓÇÖt want to sign it, you can decline to sign. 1. In the document viewer, select **More options** (...), and then select **Decline to sign**. +  + 2. On the **You're declining to sign** screen, enter a reason for not signing the document, and then select **Decline**. Or if you change your mind, select **Cancel**. -  +  Once you decline, you won't be able to add your signature, but you'll be able to see the document in read-only mode. |
| syntex | Esignature Send Requests | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/esignature-send-requests.md | If you create a signature request and want to cancel it, follow these steps. 2. When the document is open in the document viewer, select **More options** (...), and then select **Cancel request**. -  +  3. On the **Cancel signature request** confirmation screen, enter a message detailing why the request is canceled if needed, and then select **Yes, cancel**. -  +  Once canceled, the status of the request is set to **Canceled** and recipients receive an email notification telling them that the request was canceled and that no further action is possible on this request. |
| syntex | Page Range | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/page-range.md | |
| syntex | Prebuilt Model Contract | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/prebuilt-model-contract.md | The prebuilt contracts model lets you have multiple values for a given field. Fo > [!TIP] > You can use the scroll wheel on your mouse or the controls at the bottom of the document area to zoom in or out as needed to read the entity fields. +### Set a page range for processing ++For this model, you can specify to process a range of pages for a file rather than the entire file. If no page range is provided, the entire document will be processed. For more information, see [Set a page range to extract information from specific pages](page-range.md). + ### Select an extractor entity You can select an extractor either from the document area or from the **Extractors** panel, depending on your preference. |
| syntex | Prebuilt Model Invoice | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/prebuilt-model-invoice.md | The entity fields that are highlighted in green in the document area are the ite > [!TIP] > You can use the scroll wheel on your mouse or the controls at the bottom of the document area to zoom in or out as needed to read the entity fields. +### Set a page range for processing ++For this model, you can specify to process a range of pages for a file rather than the entire file. If no page range is provided, the entire document will be processed. For more information, see [Set a page range to extract information from specific pages](page-range.md). + ### Select an extractor entity You can select an extractor either from the document area or from the **Extractors** panel, depending on your preference. |
| syntex | Prebuilt Model Receipt | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/prebuilt-model-receipt.md | The entity fields that are highlighted in green in the document area are the ite > [!TIP] > You can use the scroll wheel on your mouse or the controls at the bottom of the document area to zoom in or out as needed to read the entity fields. +### Set a page range for processing ++For this model, you can specify to process a range of pages for a file rather than the entire file. If no page range is provided, the entire document will be processed. For more information, see [Set a page range to extract information from specific pages](page-range.md). + ### Select an extractor entity You can select an extractor either from the document area or from the **Extractors** panel, depending on your preference. |