Which field property dictates whether the completeness check will trigger an error?
Skip to main content This browser is no longer supported. Show
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Required diagnostic data for Office
In this articleDiagnostic data is used to keep Office secure and up-to-date, detect, diagnose and fix problems, and also make product improvements. This data does not include a user's name or email address, the content of the user's files, or information about apps unrelated to Office. This diagnostic data is collected and sent to Microsoft about Office client software running on the user's device. Some diagnostic data is required, while some diagnostic data is optional. We give you the ability to choose whether to send us required or optional diagnostic data through the use of privacy controls, such as policy settings for organizations. You can see the diagnostic data being sent to us by using the Diagnostic Data Viewer. Required diagnostic data is the minimum data necessary to help keep Office secure, up-to-date, and performing as expected on the device it's installed on. Required diagnostic data helps to identify problems with Office that may be related to a device or software configuration. For example, it can help determine if an Office feature crashes more frequently on a particular operating system version, with newly introduced features, or when certain Office features are disabled. Required diagnostic data helps us detect, diagnose, and fix these problems more quickly so the impact to users or organizations is reduced. For more information about diagnostic data, see the following articles:
If you're the admin for your organization, you might also be interested in the following articles:
Categories, data subtypes, events, and data fields for required diagnostic dataRequired diagnostic data is organized into categories and data subtypes. Within each data subtype are events, which contain data fields that are specific to that event. The following table provides a list of the categories for required diagnostic data. The data subtypes within each category are listed, along with a description of the focus for that data subtype. There are links to each data subtype section where you'll find the following information:
Note
Categories and data fields that are common for all eventsThere is some information about events that is common to all events, regardless of category or data subtype. This common information, which is sometimes referred to as data contracts, is organized into categories. Each category contains fields, and these fields are the metadata and properties of an individual event. You can view this information by using the Diagnostic Data Viewer. The categories of information that is collected about events can be divided into two groups:
Information common to all eventsInformation common to all events is collected in the following categories. AppInformation about the application. All fields are constant for all sessions of a given application version. This category contains the following fields:
ClientIdentifier related to an Office instance on a device. Constant for all sessions of all apps of a given installation version for multi-app suites, or constant for all sessions of a given application version. This category contains the following fields:
ConsentInformation regarding the users consent for diagnostic data and connected experiences. This category contains the following fields:
DeviceInformation about the operating system and build. This category contains the following fields:
LegacyProvides an App ID and OS version for compatibility with existing legacy collection practices. This category contains the following fields:
ReleaseInformation related to the release channel. All fields are constant for all sessions of all apps of a given installation version. Identifies a group of devices all in one phase of a product release cycle. This category contains the following fields:
SessionInformation about the process session. All fields are constant for this session. This category contains the following fields:
UserProvides tenant information for commercial software SKUs. This category contains the following fields:
Information that specifically supports diagnostic data collectionInformation that specifically supports diagnostic data collection is collected in the following categories. ActivityInformation to understand the success of the collection event itself. This category contains the following fields:
ApplicationInformation about the installation of the application from which the events are being gathered. This category contains the following fields:
ClientInformation about the Office client. This category contains the following fields:
DeviceInformation about device configuration and capabilities. This category contains the following fields:
EventEvent-specific information, including its unique identifier in the session. This category contains the following fields:
HostInformation about an application that hosts an embedded application This category contains the following fields:
LegacyInformation needed for legacy system compatibility. This category contains the following fields:
SessionInformation about the process session. This category contains the following fields:
Data fields that are common for OneNote eventsThe following data fields are common for all events for OneNote on Mac, iOS, and Android. Note When using the Diagnostic Data Viewer, events for OneNote on Mac, iOS, and Android will appear to have a name of Activity, ReportData, or Unexpected. To find the actual event name, select the event, and then look at the EventName field.
Data fields that are common for Outlook mobile eventsOutlook mobile collects common fields for each of our events so that we can ensure the app is up-to-date, secure, and functioning as expected. The following data fields are common for all events for Outlook for iOS and Android.
In addition, the following fields are common for all events for Outlook for iOS.
In addition, the following fields are common for all events for Outlook for Android.
Software setup and inventory data eventsThe following are the data subtypes in this category:
Office setup and inventory subtypeInstalled product and version and the installation status. add.sso.accountThis will alert Microsoft to the success or failure of a user adding an account through single sign-on (SSO). The following fields are collected:
install.referralThis event is triggered at the initial install of the app and records from where the user was referred (if available). The following fields are collected:
Office.ClickToRun.UpdateStatusApplicable to all win32 applications. Helps us understand the status of the update process of the Office suite (Success or failure with error details) The following fields are collected:
Office.Compliance.FileFormatBallotDisplayedOnFirstBootIndicates whether the Office File Format choice dialog box was shown to the user on first/second boot of Word, Excel, PowerPoint on Win32. Tracks whether the FileFormat Ballot dialog box is displayed - event is sent at the first/second boot of Word, Excel, or PPT Win32. The following fields are collected.
Office.Compliance.FileFormatBallotOptionTracks whether the FileFormat Ballot dialog box is displayed - event is sent at the first/second boot of Word, Excel, or PPT Win32. Indicates whether the Office File Format choice dialog box is displayed on first or second boot of Word, Excel, or PowerPoint on Win32. The following fields are collected:
Office.CorrelationMetadata.UTCCorrelationMetadataCollects Office metadata through UTC to compare with equivalent data collected through the Office telemetry pipeline to check correctness and completeness of data. The following fields are collected:
Office.OneNote.Android.App.OneNoteLaunchedNonActivated[This event was previously named OneNote.App.OneNoteLaunchedNonActivated.] Records information about activation state of the App. The data is monitored to ensure we identify spikes in activation issues. We also analyze the data to find areas of improvement. The following fields are collected:
Office.OneNote.Android.ResetStatus[This event was previously named OneNote.ResetStatus.] The signal used to record any issues encountered when a user tries to reset the App. The telemetry is used to monitor, detect, and fix any issues caused during reset. The following fields are collected:
Office.OneNote.Android.SignIn.SignInCompleted[This event was previously named OneNote.SignIn.SignInCompleted.] The signal is used to ensure sign-in successful or not. The data is collected to ensure critical regression detection for OneNote app and service health. The following fields are collected:
Office.OneNote.Android.SignIn.SignInStarted[This event was previously named OneNote.SignIn.SignInStarted.] The signal is used to indicate any issues encountered while using Message Bar. The data is used to monitor, detect, and fix any issues caused during interaction with Message Bar. The following fields are collected:
Office.OneNote.FirstRun.FirstRunThe critical signal used to ensure new users can successfully launch and run OneNote for the first time. The telemetry is collected to ensure critical regression detection for OneNote app and service health. If users can't launch the app for the first time, this would trigger a high severity incident.
Office.OneNote.FirstRun.FirstRunForMSAThe critical signal used to ensure new consumer users (Microsoft Account) can successfully launch and use OneNote for the first time. Telemetry used to ensure critical regression detection for OneNote app and service health. If users can't launch the app for the first time, this would trigger a high severity incident. The following fields are collected:
Office.OneNote.FirstRun.FirstRunForOrgIdThe critical signal used to ensure new enterprise users (AAD/OrgID) can successfully launch and run OneNote for the first time. Telemetry used to ensure critical regression detection for OneNote app and service health. If users can't launch the app for the first time, this would trigger a high severity incident.
Office.OneNote.FirstRun.MruReaderNoteBookEntriesThe signal used to record any issues encountered when loading Notebooks during First Run. The telemetry is used to monitor, detect, and fix any issues in First run. The following fields are collected:
Office.OneNote.System.AppLifeCycle.UserAccountInfoThis event is triggered for shared code and records values for type of accounts signed in via isEdu, isMsftInternal, isIW, isMSA. The data is collected the first time the queue becomes idle after launch. This marker is used to track the types of accounts which have been signed in on the device. This will help us identify EDU users in OneNote. The following fields are collected:
Office.Programmability.Addins.OnStartupCompleteEnterpriseThis event is generated when a Legacy or COM Add-in is loaded on an enterprise device. The data is used to determine adoption and performance of Office add-ins. The following fields are collected:
Office.TargetedMessaging.EnsureCachedTracks if a package for Dynamic Canvas was downloaded. Considered a software configuration because the package must be successfully downloaded to enable the client to render the right experience. Is especially critical in consumer subscriptions where we use canvas to communicate to the user that the license has expired. Used to track metadata of a dynamic content package downloaded and cached by the product and results of operations performed on the package: download failures, unpacking failures, consistency checks failures, cache hits, package usages, download sources. The following fields are collected:
Office.Visio.VisioSKUCaptures Visio SKU whether it's standard or professional. Essential to categorize issues based on SKU. The following fields are collected:
Office add-in configuration subtypeSoftware add-ins and their settings. Excel.AddinDefinedFunction.CustomFunctionsAllInOneCollects information about runtime behavior of custom add-in functions. Maintains counters of execution attempts, successful completions, infrastructure errors, and user code errors. This is used to identify reliability issues in the product and fix user-impacting problems. The following fields are collected:
Office.Extensibility.AppCommands.AppCmdProjectionStatusCollects information to track which Office add-in installations successfully updated the ribbon vs failed. Used to fix common registration issues where add-ins are not installed properly and never show up resulting in them being unusable. The following fields are collected:
Office.Extensibility.AppCommands.AddSolutionCollects install information for Office add-ins that customize the ribbon. Used to detect issues with how custom add-ins modify the Office ribbon. The following fields are collected:
Office.Extensibility.Catalog.ExchangeGetEntitlementsData regarding the success for failure of retrieving add-in entitlement data for the Office 365 tenant admin assigned add-ins. Used for health metrics, charts, and analysis of customer problems. The following fields are collected:
Office.Extensibility.Catalog.ExchangeGetLastUpdateData regarding the success for failure of retrieving the need for updated data regarding the Office 365 tenant admin assigned add-ins. Used for health metrics, charts, and analysis of customer problems. ExchangeGetLastUpdate will always run on boot as part of the host code and determine whether add-in assignments have changed for a user. If so then osf.DLL will be loaded so we can call ExchangeGetEntitlements to get the specific assignments (and ExchangeGetManifests will be called to retrieve any new manifests that are needed). ExchangeGetEntitlements (and ExchangeGetManifests) could also be called on demand after host application has been running. The idea is to not load the large DLL if we don't need to. Without this event in Required, we would not be able to tell if users are failing to get add-ins assigned to them if that first service call fails. It's also the main signal for any auth problems we face talking to our service. The following fields are collected:
Office.Extensibility.Catalog.ExchangeGetManifestsData regarding the success for failure of retrieving add-in manifests data for the Office 365 tenant admin assigned add-ins. Used for health metrics, charts, and analysis of customer problems. The following fields are collected:
Office.Extensibility.UX.FEnsureLoadOsfDLLTracks failure to load Osf.DLL. Detect DLL load failure that prevents feature from running. The following fields are collected:
Office.Extensibility.UX.FEnsureLoadOsfUIDLLTracks failure to load OsfUI.DLL. Detect DLL load failure that prevents feature from running. The following fields are collected:
Office.Extensibility.UX.FEnsureOsfSharedDLLLoadTracks failure to load OsfShared.DLL. Detect DLL load failure that prevents feature from running. The following fields are collected:
Office.Extensibility.VBATelemetryComObjectInstantiatedCollects information about invocation of automation server or client in VBA solutions. Used to understand interaction between VBA and COM Objects. The following fields are collected:
Office.Extensibility.VBATelemetryDeclareCollects information about invocation of Win32 APIs in VBA solutions. Used to understand interaction between VBA and usage and to supplement security investigations. The following fields are collected:
Office.Outlook.Desktop.Add-ins.Add-inLoadedCollects the success and failure of Outlook loading of an add-in. This data is actively monitored in order to ensure Outlook is correctly working with customer add-ins. This data is used to detect and investigate issues. The following fields are collected:
Office.Outlook.Mac.AddinAPIUsageCollects success and failure of add-in execution in Outlook. This data is actively monitored to ensure Outlook is correctly working with add-ins. This data is used to detect and investigate issues. The following fields are collected:
Office.Outlook.Mac.AddinEventAPIsUsageCollects success or failure of add-in execution in Outlook. This data is actively monitored to ensure Outlook is correctly working with add-ins. This data is used to detect and investigate issues. The following fields are collected:
Office.Outlook.Mac.AddInInstallationFromInClientStoreCollects success or failure of add-in installation in Outlook. This data is actively monitored to ensure Outlook is correctly working with add-ins. This data is used to detect and investigate issues. The following fields are collected:
Office.Programmability.Addins.InternalSetConnectEnterpriseEvent generated when a COM Add-in is loaded on an enterprise device. Used to determine adoption, performance, and reliability issues with Office add-ins. The following fields are collected:
Office.Programmability.Addins.RibbonButtonClickThe event is generated the first time in a session the user clicks a button added to the ribbon by a specific add-in. If the session spans multiple days, this telemetry will be sent once per day instead. The data is used in two ways: 1. When an add-in breaks, knowing how much users truly use the add-in will help us triage the issue. 2. To display to admins as part of COM add-in management scenarios in add-in Inventory and as part of planned add-in health scenarios in Microsoft 365 Apps health. Admins will be able to monitor add-in usage per device, letting them disable or uninstall unused COM add-ins. The following fields are collected:
Office.Visio.Visio.AddonLoadCaptures errors when a solution fails to load. Essential to debug addon load errors in Visio. The following fields are collected:
Office.Visio.Visio.AddonUsageCaptures errors when there is an error in solution functionality. Essential to debug addon errors in add-ons. The following fields are collected:
Security subtypeDocument, feature, and add-in error conditions that may compromise security, including product update readiness. Office.AppGuard.CreateContainerWe collect error codes and whether the container already existed or not. We also collect error codes for a reset event in case we fail to create the container on our first attempt. Data will be used identify the percentage of sessions we successfully create the container for launching Office Application Guard apps. Data will also allow Microsoft to identify and address error codes from the container creation. The following fields are collected:
Office.AppGuard.LaunchFileThis event denotes the result of an Application Guard launch file execution. We will be able to define the percentage of sessions we successfully launched a Word, Excel, or PowerPoint file and the error codes for the failed attempts. The following fields are collected:
Office.AppGuard.OpenInContainerThis event is triggered when the Office application running in the Application Guard container signals that the request to open a file has been received. The data is used to diagnose failures during the initialization of the Office application in the Application Guard container. The following fields are collected:
Office.Security.ActivationFilter.CLSIDActivatedTracks when a specific Class Identifier (Flash, Silverlight etc.) is activated in Office. Used to track impact of blocking Flash, Silverlight, and Shockwave controls on end users. The following fields are collected:
Office.Security.ActivationFilter.FailedToRegisterTracks an error condition in security mitigation that blocks activation of dangerous controls in Office. Used to diagnose error conditions in security mitigation that could impact security of end users. The following fields are collected:
Office.Security.ComSecurity.FileExtensionListFromServiceTracks if packager block extensions were read from config service or we used client default list. Used to ensure effectiveness of security mitigation that protects end users of Office. The following fields are collected:
Office.Security.ComSecurity.LoadTracks when an OLE object is loaded in a document. Used to ensure effectiveness of security mitigation that protects end users of Office. The following fields are collected:
Office.Security.ComSecurity.ObjDetectedTracks when an OLE object is detected in a document. Used to ensure effectiveness of security mitigation that protects end users of Office. The following fields are collected:
Office.Security.ComSecurity.PackagerActivationTracks the outcome of security mitigation that blocks dangerous extensions embedded in Office documents. Used to ensure effectiveness of security mitigation that protects end users of Office. The following fields are collected:
Office.Security.ComSecurity.PackagerActivationErrorsTracks error conditions in security mitigation that blocks dangerous extensions embedded in Office documents. Used to ensure effectiveness of security mitigation that protects end users of Office. The following fields are collected:
Office.Security.Macro.InternetVBABlockEnabledTracks whether the Block Macro from Internet setting is enabled in a client. Assess use of security mitigation to protect against malicious macros. The following fields are collected:
Office.Security.Macro.PolicyDigSigTrustedPublishersTracks if the macro was verified to be from a trusted publisher. Used to ensure effectiveness of security mitigation that protects end users of Office. The following fields are collected:
Office.Security.Macro.PromptedTracks when a user is prompted to enable VBA Macros. Used to assess prevalence of VBA Macros and drive future security mitigations that restrict macro execution in response to security incidents. The following fields are collected:
Office.Security.Macro.VBASecureRuntimeSessionEnableStateTracks each AMSI runtime verification performed when a macro executes. Tracks effectiveness of the AMSI runtime verification of Macro execution and identify errors that could impact security of end users. The following fields are collected:
Office.Security.Macro.XL4PromptedTracks when a user is prompted to enable XL4 Macros. Used to assess prevalence of XL4 Macros in Excel to drive future security mitigations that block XL4 by default in response to security incidents that involve abusing XL4 macros. The following fields are collected:
Office.Security.OCX.UFIPromptTracks when a security prompt is shown to the user when loading an ActiveX control that is marked Unsafe for Initialization. Used to track prevalence of UFI ActiveX controls in Office documents to drive mitigations (for example, killbitting controls) in response to security incidents. The following fields are collected:
Office.Security.SecureReaderHost.OpenInOSRTracks completion of an open in Protected View. Used to diagnose conditions that lead to failures when opening files in Protected View impacting security and productivity of customers. The following fields are collected:
Product and service usage data eventsThe following are the data subtypes in this category:
Application feature success subtypeSuccess of application functionality. Limited to opening and closing of the application and documents, file editing, and file sharing (collaboration). account.actionThe event is triggered when the user creates, adds, resets, or deletes their account. The data is needed to ensure account configuration is operating successfully and is used to monitor health of account creation, ability to add new email accounts, and monitor soft account resets. The following fields are collected:
account.lifecycleThis event is collected to ensure account configuration is operating successfully and is used to monitor health of account creation, ability to add new email accounts, and monitor soft account resets. The following fields are collected:
add.new.account.stepThis event lets us detect how far the user has gotten in the create new account form. It indicates when the user has moved to another step or if they have dropped off. We need this information to detect if any steps are failing and to ensure user account creation was successful. The following field is collected:
app.errorTracks critical app errors used so that we can prevent issues that could cause your app to crash or prevent you from reading email. The following fields are collected:
All characters are also possible properties. This helps us understand the characters in the body of the draft message when the error occurred. For example, "a", "b", "c" are possible properties. app.launch.reportThis event is triggered when Outlook starts slowly or incompletely. The data collected provides information on the specific features that were enabled and how long parts of the startup took. It allows us to detect and fix the cause of the issues. The following fields are collected:
calendar.actionThis event reports part of the calendar event data after creating event or editing events. This is used for monitoring any possible negative impact on your ability to perform core calendar actions. The event could also include a series of property names and if they have changed or not. For example, "title_changed", "online_meeting_changed", and "description_changed" are property names that are included to help us understand if there are any issues with editing certain properties. The following fields are collected:
combined.search.useThis event is triggered when a user enters or exits search mode or interacts with search entities such as results, suggestions, or filters. Used for monitoring possible negative impact on your ability to perform key search functionality such as searching for mail, contacts, or events. The following fields are collected across iOS and Android:
The following fields are collected across iOS applications of Outlook Mobile:
compose.mail.accessoryThis event lets us detect and fix issues with key mail compose actions to prevent you from running into issues with attaching a file, taking a photo as an attachment, or sending your availability. The following fields are collected:
conversation.view.actionThis event is triggered when a user interacts with the conversation view. For example, attempting to load more conversations or opening quick reply. The data is used for monitoring possible negative impact on the ability to view and reply to email messages as well as for determining issues related to conversation features such as reactions, suggested replies, pinning, etc. The following fields are collected:
draft.actionThe event is triggered when the user closes by tapping the top left button at the full compose view or save some drafts from quick reply view. The data is used for monitoring possible negative impact on the ability to create and save mail drafts. The following fields are collected:
drag.and.dropThis event lets us detect if the drag and drop action was successful or not. It is used to ensure that drag-and-drop experiences are working correctly across applications both as a drop event into Outlook and a drag event that leaves Outlook. With this data, we are able to ensure that the end-to-end experience with other applications is working as expected. The following fields are collected:
drawer.eventUsed for monitoring possible negative impact on your ability to access folders in your inbox The following fields are collected:
IpcCreateRepublishingLicenseCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when the IpcCreateRepublishingLicense API call is made. The following fields are collected:
IpcGetLicensePropertyCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when the IpcGetLicenseProperty API call is made. The following fields are collected:
IpcGetSerializedLicensePropertyCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when the IpcGetSerializedLicenseProperty API call is made. The following fields are collected:
IpcGetTemplateIssuerListCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when the IpcGetTemplateIssuerList API call is made. The following fields are collected:
IpcGetTemplateListCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when the IpcGetTemplateList API call is made. The following fields are collected:
IpcpCreateLicenseFromScratchCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when the IpcpCreateLicenseFromScratch API call is made. The following fields are collected:
IpcpCreateLicenseFromTemplateCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when the IpcpCreateLicenseFromTemplate API call is made. The following fields are collected:
IpcpGetTemplateListForUserCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when the IpcpGetTemplateListForUser API call is made. The following fields are collected:
IpcpSerializeLicenseCollected when a user attempts to apply IRM protections on the doc. It contains the information needed to be able to properly investigate and diagnose issues that happen when the IpcpSerializeLicense API call is made. The following fields are collected:
IpcSetLicensePropertyCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when the IpcSetLicenseProperty API call is made. The following fields are collected:
link.clicked.actionThe event is used to track users' success in viewing a URL in the Edge web view and completing standard web scenarios in that web view without facing errors The following fields are collected:
log.event.appointment.attendeeThis event is triggered when the user clicks on any add-in on their calendar page. The data is used to detect the usage of add-ins and determine the if the feature is performing correctly. The following fields are collected:
mail.actionUsed for monitoring possible negative impact on your ability to perform critical mail actions (like running mail threaded mode, ensuring mail triage actions work) to ensure our app is functioning properly for mail. The following fields are collected:
mail.composeUsed for monitoring possible negative impact on your ability to compose and reply to emails such as running into issues with reply-all, formatting your email, or sending your emails. The following fields are collected:
meeting.call.to.actionUsed for monitoring possible negative impact on your ability to perform critical meeting actions like creating, editing, and responding to meetings. The following fields are collected:
message.reminderThis event is triggered when a user interacts with a message reminder. A message reminder is a User Interface (UI) element that prompts the user to interact with a message they might have forgotten about and should follow up on. The data is used to determine the optimal UI for showing message reminders and for monitoring the success and impact of the feature. The following fields are collected across iOS and Android:
multi.window.launchThis event captures when the user takes action that involves multi-window launch on foldable devices, e.g., compose mail, event, open calendar window. It uses the action to remember such action, e.g., to keep getting the prompt or always launch in new window. The data collected by this event will be used to assess discoverability, effectiveness as well as general user preferences to drive current and future developments of multi window related functionalities. The following fields are collected:
notification.centerThis event allows us to track when users enter and exit the notification center in addition to the count of unseen notifications. This helps us make sure that the notification center is consistent with all other clients. We also track when a user taps on a notification so we can tell what type it is. The following fields are collected:
Office.Android.DocsUI.FileOperations.OpenDocumentMeasurementsThis event is collected for Office applications running under Android platform and records when a file open operation takes place. The event helps in keeping the file open operation secure, up- to- date and performing properly. The goal of collecting this data is to continuously improve the file open performance. The following fields are collected:
Office.Android.DocsUI.PaywallControl.PreSignInFRE[This event was previously named Office.DocsUI.PaywallControl.PreSignInFRE.] This is critical usage telemetry for the upsell in the First Run Experience for unsigned users. This event captures the first-run sign-in metrics. The data will be used to infer insights for the pre sign-in and understand if the user is continuing to the next stage in the user flow. The following fields are collected:
Office.Android.DocsUI.PaywallControl.SkuChooserToggledUsage telemetry to view how many times user switches between different SKUs before attempting a purchase. Used to understand usage of the SKU chooser and optimize the in app purchase experience in future versions. The following fields are collected:
Office.Android.DocsUI.PaywallControl.UserImageClicked[This event was previously named Office.DocsUI.PaywallControl.UserImageClicked.] This event measures telemetry to see if users are trying to complete an action by clicking on a user avatar. This data will be used to measure how many users interact with the avatar icon to assess the need for a follow-up experience upon tap. The following fields are collected:
Office.Android.EarlyTelemetry.AdInfraEvent[This event was previously named Office.Android.AdInfraEvent.] This event is triggered when an ad request is sent, and a response is received from the ad network. This event does not collect any user related data from the online platform. This data is logged to understand:
The following fields are collected:
Office.Android.EarlyTelemetry.ExpansionFilesAvailabilityWe are enabling Android Package Kit (APK) expansion files for the Office mobile app. APK Expansion files are supplementary resource files that Android app developers can publish along with their app. To understand the reliability of the expansion files, we log a flag indicating whether expansion files are available or not at every boot. The following fields are collected:
Office.Android.EarlyTelemetry.ExpansionFilesDownloaderWe are enabling Android Package Kit (APK) expansion files for the Office mobile app. APK Expansion files are supplementary resource files, that Android app developers can publish along with their app. To understand the reliability of our expansion file download mechanism, we are logging a flag indicating whether we are successfully able to download expansion files. The following fields are collected:
Office.Android.EarlyTelemetry.NoteCreatedCritical signal that is used to monitor the ability of Sticky Notes users to create notes in the app. Telemetry is used to ensure critical regression detection for OneNote app and service health. If users can’t create a note, this would trigger a high severity incident. The following fields are collected:
Office.Android.EarlyTelemetry.NoteViewedCritical signal that is used to monitor the ability of Sticky Notes users to view notes in the app. Telemetry is used to ensure critical regression detection for OneNote app and service health. If users can’t view their notes, this would trigger a high severity incident. The following fields are collected:
Office.Android.Intune.IntuneComplianceRequestThis event is collected for Office applications running on Android, including Office mobile, Word, Excel, PowerPoint, and OneNote. The event indicates an attempt to sign in to an Intune licensed organization account where the organization administrator has configured policy to enforce app conditional access. It is used to understand the number of end users who are attempting to use apps under this policy configuration, and is combined with another event, Office.Android.Intune.IntuneComplianceStatus, to ensure the configured policy is enforced. No data fields are collected. Office.Android.Intune.IntuneComplianceStatusThis event is collected for Office applications running on Android, including Office mobile, Word, Excel, PowerPoint, and OneNote. The event indicates an attempt to sign in to an Intune licensed organization account where the organization administrator has configured policy to enforce app conditional access. This event indicates the compliance status of the application to which the user has signed-in and is used to investigate failures. It is combined with another event, Office.Android.Intune.IntuneComplianceRequest, to ensure the configured policy is enforced. The following fields are collected:
Office.Android.ODWXPSSO.TelemetryThis event helps in understanding with which other Microsoft app in the device, our app got silent single sign on, from which entry point and so on. Also helps in understanding the failure reason for not getting silent single sign on. We get better insights like from which Microsoft app in the device, we are getting single sign on experience. Act upon failures, where single sign on isn't working as expected. The following fields are collected:
Office.Android.PhoneNumberSignInsThis event helps in understanding if user signed in or signed up with phone number-based account or email based personal Microsoft account. This event helps in knowing count of users signing in or signing up with phone number based personal Microsoft account. The following fields are collected:
Office.Android.UserSignInDecisionThis event helps in understanding at which stage user is dropping in sign in flow, why sign in is failing, how many users are getting signed in successfully from which entry point in the app and so on. This event helps with sign-in funnel data, which helps in understand at which stage users are getting dropped more and so on. The following fields are collected:
Office.AppCompat.AppCompat.AgentScanAndUploadOnly collected when end user has enabled Office Telemetry Dashboard. It collects information on when the Office Telemetry Agent is executed. This is only collected when Office Telemetry Dashboard is enabled and is used to determine the health of Office Telemetry agent. The following fields are collected:
Office.AppCompat.AppCompat.AgentUploadGenerated on client startup when end user has enabled Office Telemetry Dashboard. It collects information on when the Office Telemetry Agent has uploaded data to the share folder. The primary use of this event is to monitor the health of the Office Telemetry agent and the secondary use of the event is to estimate usage of the Office Telemetry Dashboard. The following fields are collected:
Office.AppCompat.AppCompat.TelemetryDashboardResiliencyCrashLogOnly collected when Office Telemetry Dashboard has been enabled by end user (most likely an admin). It collects the occurrence of Office Add-ins and documents crashes. This is only collected when user has enabled Office Telemetry Dashboard and is used to determine if there is an increased occurrence of add-in or document crashes. The following fields are collected:
Office.AppDocs.AppDocs.DocumentOperationThis event is collected for Office applications running on Android, iOS, Universal, or Windows platforms. The event records when a file operation (create/open/save/export/etc.) takes place and it is used to understand and prioritize user-experiences based on the file operation information. The following fields are collected:
Office.Apple.ActivatePerpetualThis event is collected for Office applications running under Apple platforms. The event is used to monitor the health of the perpetual activation flow as well as investigating causes of failures by reviewing the FailedAt values. The following fields are collected:
Office.Apple.ActivateSubscriptionThis event is collected for Office applications running under Apple platforms. We collect information related to the migration from the legacy licensing code stack to the vNext licensing code tack. This is used to monitor the health of the subscription activation flow as well as tracking if this is a migration to licensing vNext and if the primary identity was used. The following fields are collected:
Office.Apple.CISAuthTicketWithIdentityThis event is collected for Office applications running under Apple platforms. The event is used for capturing auth token generation failures during InAppPurchase on the Mac (the event logs the error code received). This event is used for detecting and helping troubleshoot auth token generation failures The following fields are collected:
Office.Apple.InAppAssociationActivityThis event is collected for Office applications running under Apple platforms. We collect information related to product association after an in-app purchase. We log which subscription SKU we are associating. This is used to monitor the health of the in-app purchase product associations. The following fields are collected:
Office.Apple.InAppPurchaseActivityThis event is collected for Office applications running under Apple platforms. We collect information related to product purchases on the AppStore. We track the result of the purchase (Failure, success, payment issue, etc.), the type of the purchase request (restore, purchase) and the SKU/product being purchased (Microsoft 365 Family, etc.). This data is used for monitoring the health of the in-app purchase flows. The following fields are collected:
Office.Apple.InTuneThis event is collected for Office applications running under Apple platforms. We collect whether the current session is Intune-managed. This is used to pivot/filter on Intune managed sessions and allows us to investigate potential issues related to Office being run as an Intune-managed application. The following fields are collected:
Office.Apple.Licensing.Mac.LicensingStateThis event is collected for Office applications running under Apple platforms. The event captures the current state of the license for a session in a machine (OLS license ID, SKU being used, grace-period or not, RFM, etc.). The data collected is used for detecting errors and investigating causes of failures. The following fields are collected:
Office.ConnectDevice.Activity.StartAllows us to know if a connection to a device or application was successful. Used for feature health and monitoring. This event is generated by Microsoft Data Streamer for Excel Add-in. The following fields are collected:
Office.ConnectDevice.Activity.StopAllows us to know if a connection to a device or application was successful. Used for feature health and monitoring This event is generated by Microsoft Data Streamer for Excel Add-in. The following fields are collected:
Office.Docs.AppDocs.OperationOpenFromMruByPathThis event is collected for Office applications running on Android, iOS, Universal, or Windows platforms. The event records when a file open operation takes place from the path provided in the most recently used list and is used to understand and prioritize user-experience errors based on file open operation information. The following fields are collected:
Office.Docs.AppDocs.OperationOpenFromMruByUrlThis event is collected for Office applications running on Android, iOS, Universal, or Windows platforms. The event records when a file open operation takes place from the URL provided in the most recently used list and is used to understand and prioritize user-experiences based on file open operation information. The following fields are collected:
Office.Docs.AppDocs.OperationOpenFromPathThis event is collected for Office applications running on Android, iOS, Universal, or Windows platforms. The event records when a file open operation takes place from a path and is used to understand and prioritize user-experiences based on file open operation information. The following fields are collected:
Office.Docs.AppDocs.OperationOpenFromProtocolHandlerThis event is collected for Office applications running on Android, iOS, Universal, or Windows platforms. The event records when a file open operation takes place from another application using the protocol handler interface and is used to understand and prioritize user-experiences based on file open operation information. The following fields are collected:
Office.Docs.AppDocs.OperationOpenFromShellThis event is collected for Office applications running on Android, iOS, Universal, or Windows platforms. The event records when a file open operation takes place from the shell and is used to understand and prioritize user-experiences based on file open operation information. The following fields are collected:
Office.Docs.AppDocs.OperationOpenFromUrlThis event is collected for Office applications running on Android, iOS, Universal, or Windows platforms. The event records when a file open operation takes place from a URL and is used to understand and prioritize user-experiences based on file open operation information. The following fields are collected:
Office.Docs.Apple.DocsUXiOSSaveAsThroughFileMenuThis event is collected for Office applications running under Apple platforms. The event records when a "Save as" operation takes place and is used to understand and prioritize user-experiences based on file operation information such as location categories. A "Save as" operation occurs whenever a user creates a new file and saves it for the first time or saves a copy of an existing file to a new location. The following fields are collected:
Office.Docs.Apple.DocsUXMacAtMentionInsertedAtMentionThis event is collected for Office applications running under Apple platforms. This event records when a user "@" mentions another user and is used to understand and prioritize user-experiences based on how users collaborate with other users. The following fields are collected:
Office.Docs.Apple.DocsUXMacODSPSharingWebViewSharingCompletedThis event is collected for Office applications running under Apple platforms. This event records when a user chooses to share a cloud document using the OneDrive sharing experience and is used to better understand and prioritize user-experiences based on sharing documents. The following fields are collected:
Office.DocsUI.Collaboration.CoauthorGalleryRowTappedThis event is collected for Office applications running under Apple platforms. This event records when a user selects to look at the list of current co-authors. This data is used to better understand and prioritize user-experiences relating to co-authoring a document at the same time. The following fields are collected:
Office.DocsUI.Collaboration.CollabCornerPeopleGalleryCoauthorsUpdatedThis event is collected for Office applications running under Apple platforms. The event records when the number of active co-authors in a cloud document changes. This data is used to better understand and prioritize user-experiences relating to co-authoring a document at the same time. The following fields are collected:
Office.DocsUI.DocStage.DocStageCreateNewFromTemplateThis event is collected for Office applications running under Apple platforms. The event records when a new file is created from the "New from template" experience and is used to better understand and prioritize user-experiences based on document creation information. The following fields are collected:
Office.DocsUI.DocStage.RecommendedOpenThis event is collected for Office applications running under Apple platforms. The event records when a file-open operation takes place from the recommended files section of the document gallery and is used to understand and prioritize user-experiences based on file open operation information. The following fields are collected:
Office.DocsUI.FileOperations.DocsUIFileOpenMacRequiredThis event is collected for Office applications running under Apple platforms. The event records when a file open operation takes place and is used to understand and prioritize user-experiences based on file open operation information such as location categories "ServiceType" and the first four characters of the extension. The following fields are collected:
Office.DocsUI.FileOperations.OpenDocumentMeasurementsThis event is collected for Office applications running under iOS platform. The event records when a file open operation takes place and is used to understand and prioritize user-experiences based on file open operation information, especially performance information. The following fields are collected:
Office.DocsUI.FileOperations.OpenFileWithReasonThis event is collected for Office applications running under Apple platforms. The event records when a file open operation takes place and is used to understand and prioritize user-experiences based on file open operation information such as location categories "ServiceType" and from where within Application the user requested to open a file. The following fields are collected:
Office.DocsUI.FileOperations.SaveToURLThis event is collected for Office applications running under Apple platforms. The event records when a "save as" operation takes place and is used to understand and prioritize user-experiences based on file operation information such as location categories and the first four characters of the extension. A "save as" operation occurs whenever a user creates a new file and saves it for the first time or saves a copy of an existing file to a new location. The following fields are collected:
Office.DocsUI.SharingUI.CloudUpsellShownThis event is collected for Office applications running under Apple platforms. This event records when a user goes through the document upsell to cloud flow. This data is used to better understand and prioritize user-experiences relating to moving documents to cloud locations. The following fields are collected:
Office.DocsUI.SharingUI.CloudUpsellUploadThis event is collected for Office applications running under Apple platforms. This event records when a user chooses to upload a new or local file to the cloud and the result of that operation. This data is used to better understand and prioritize user-experiences relating to moving documents to cloud locations. The following fields are collected:
Office.DocsUI.SharingUI.CopyLinkOperationThis event is collected for Office applications running under Apple platforms. This event records when a user chooses to share a document by generating a link to a cloud document and is used to better understand and prioritize user-experiences based on sharing documents. The following fields are collected:
Office.DocsUI.SharingUI.DocsUIOneDriveShareThis event is collected for Office applications running under Apple platforms. This event records when a user chooses to share a cloud document using the OneDrive sharing experience and is used to better understand and prioritize user-experiences based on sharing documents. The following fields are collected:
Office.DocsUI.SharingUI.InvitePeopleThis event is collected for Office applications running under Apple platforms. This event records when a user chooses to invite people to a cloud document and is used to better understand and prioritize user-experiences based on sharing documents. The following fields are collected:
Office.DocsUI.SharingUI.SendACopyOperationThis event is collected for Office applications running under Apple platforms. The event records when a user chooses to send a copy of a document and is used to better understand and prioritize user-experiences based on sharing documents. The following fields are collected:
Office.DocsUI.SharingUI.UpsellShareThis event is collected for Office applications running under Apple platforms. This event records when a user goes through the document upsell to cloud flow when trying to share a document. This data is used to better understand and prioritize user experiences relating to moving documents to cloud locations. The following fields are collected:
Office.Excel.XlEditSessionCollected when the user starts editing a spreadsheet. The data collected allows Microsoft to evaluate the feature health of actions that change the spreadsheet. It is also used to calculate monthly active users and devices. The following fields are collected:
Office.Extensibility.Catalog.ExchangeProcessEntitlementData regarding the processing of an individual entitlement of and Office 365 tenant admin assigned add-in. Used in charting (requested by team management) of customer success and analysis of customer problems. The following fields are collected:
Office.Extensibility.Catalog.ExchangeProcessManifestData regarding the processing of an individual manifest for an Office 365 tenant admin assigned add-in. Used in analysis of customer problems and charting of customer success. The following fields are collected:
Office.Extensibility.ODPAppCommandsRibbonClickCollects whether clicking the custom add-in control succeeded or not. Used to detect issues in user interaction with add-in controls. The following fields are collected:
Office.Feed.Events.InitializingThis event is collected when the feed has started initializing. This event is used to indicate that the feed is starting and to diagnose reliability issues in launching the feed.
Office.Feed.Events.OfficeFeedDidAppearThis event is collected when the feed is shown to the user. The event is used to verify that the feed completed initialization step and to diagnose reliability issues in launching the feed.
Office.Feedback.Survey.FloodgateClient.GetDecisionForActionPreStartIn Office apps we control the frequency of in-product and push messages through a governance layer. This event gets logged in error conditions when we try to apply governance to in-app messages before the module that is handling governance is fully activated. This telemetry helps make our governance logic more robust by collecting details of the scenarios in which the governance is not being applied. The following fields are collected:
Office.Feedback.Survey.FloodgateClient.SurveyTrackedTracks when a device that is eligible for a survey starts an app. Used to assess the health of the survey user selection process and to ensure the signal used to analyze customer issues and health is working properly. The following fields are collected:
Office.Feedback.Survey.FloodgateClient.TriggerMetTracks when a device has met the criteria to show a survey. Used to assess the health of the survey triggering process and to ensure the signal used to analyze customer issues and health is working properly. The following fields are collected:
Office.Feedback.Survey.FloodgateClient.UserSelectedTracks when a device has been selected for a survey. Used to assess the health of the survey user selection process and to ensure the signal used to analyze customer issues and health is working properly. The following fields are collected:
Office.Feedback.Survey.UI.AndroidOn an Android device, it tracks when a user on a device interacts with the survey prompt and survey UI. Used to assess the health of the end-to-end survey experience and to ensure the signal used to analyze customer issues and health is working properly. The following fields are collected:
Office.Feedback.Survey.UI.IOSOn an iOS device, it tracks when a user on a device interacts with the survey prompt and survey UI. Used to assess the health of the end-to-end survey experience and to ensure the signal used to analyze customer issues and health is working properly. The following fields are collected:
Office.Feedback.Survey.UI.MacOn a Mac device, it tracks when a user on a device interacts with the survey prompt and survey UI. Used to assess the health of the end-to-end survey experience and to ensure the signal used to analyze customer issues and health is working properly. The following fields are collected:
Office.Feedback.Survey.UI.Win32On a Win32 device, it tracks when a user on a device interacts with the survey prompt and survey UI. Used to assess the health of the end-to-end survey experience and to ensure the signal used to analyze customer issues and health is working properly. The following fields are collected:
Office.Feedback.Survey.UI.Win32.ToastTracks when survey prompt is shown. Used to assess the health of the survey prompt process and to ensure the signal used to analyze customer issues and health is working properly. The following fields are collected:
Office.FileIO.CSI.CCachedFileCsiLoadFileBasicAllows us to know if a file successfully opened from the FIO Layer. Used for feature health and monitoring. The following fields are collected:
Office.FileIO.CSI.CCachedFileCsiSaveFileBasicThis event allows us to know if a file was successfully saved from the FIO Layer. Used for Feature Health and monitoring. The following fields are collected:
Office.FindTime.AppFailedToStartCollected when app fails to start due to an unexpected error during startup. Used to track exceptions & crashes. Helps monitor & debug app health. The following fields are collected:
Office.FirstRun.Apple.ActivationResultThis event is collected for Office applications running under Apple platforms. The event is used to monitor the health of our application activation flow. We collect data to figure out the outcome of the Office 365 subscription activation along with the flow used to activate (First Run Experience, In-App-Flow, Purchase, etc.). The following fields are collected:
Office.FirstRun.Apple.ActivationStatusThis event is collected for Office applications running under Apple platforms. The event is used to figure out the outcome of the Office 365 subscription activation along with the flow used to activate (FRE, InApp, Purchase, etc.). We collect data containing the Activation type, flow type (FRE/DocStage/Purchase) and Office Licensing Service ID. The following fields are collected:
Office.FirstRun.Apple.FirstRunCompleteThis event is collected for Office applications running under Apple platforms. The event lets us know if the user running in freemium, the flow type being run (FRE/DocStage/Purchase) and the identity type (MSA/OrgID). We use this event to figure out if the First Run-Experience (FRE) was completed and type of identity used to sign in (MSA/OrgID). The following fields are collected:
Office.FirstRun.Apple.FirstRunStartThis event is collected for Office applications running under Apple platforms. The event lets us know a user has entered first run experience and the flow type being run (FRE/DocStage/Purchase). We use this event to figure out if the First Run-Experience (FRE) was started successfully. The following fields are collected:
Office.FirstRun.Apple.FirstRunStartedAndCompletedThis event is collected for Office applications running under Apple platforms. The event lets us know if the user running in freemium, the flow type being run (FRE/DocStage/Purchase) and the identity type (MSA/OrgID). We use this event to figure out the health and effectiveness of our First-Run Experience (FRE) flow. The following fields are collected:
Office.FirstRun.Apple.InAppPurchaseActivationFailThis event is collected for Office applications running under Apple platforms. The event is used to monitor the health of our application activation flow. We collect data to figure out the outcome of the In-App purchase activation along with the flow used to activate (First Run Experience, In-App-Flow, Purchase, etc.). The following fields are collected:
Office.FirstRun.Apple.InAppPurchaseActivationSuccessThis event is collected for Office applications running under Apple platforms. The event is used to monitor the health of our application activation flow. We collect data to figure out the outcome of the In-App purchase activation along with the flow used to activate (First Run Experience, In-App-Flow, Purchase, etc.). The following fields are collected:
Office.FirstRun.Apple.InAppPurchaseAssociationFailedThis event is collected for Office applications running under Apple platforms. The event is used to monitor the health of our application activation flow. We collect data to figure out the outcome of the In-App purchase activation along with the flow used to activate (First Run Experience, In-App-Flow, Purchase, etc.). The following fields are collected:
Office.FirstRun.Apple.InAppPurchaseAssociationSuccessThis event is collected for Office applications running under Apple platforms. The event is used to monitor the health of our application activation flow. We collect data to figure out the outcome of the In-App purchase activation along with the flow used to activate (First Run Experience, In-App-Flow, Purchase, etc.). The following fields are collected:
Office.FirstRun.Apple.InAppPurchaseFailuresThis event is collected for Office applications running under Apple platforms. The event is used to monitor the health of our application activation flow. We collect data on the outcome of the In-App purchase flow. The following fields are collected:
Office.FirstRun.Apple.InAppPurchasesAttemptedThis event is collected for Office applications running under Apple platforms. The event is used to monitor the health of our application in-app purchase flow. We collect data to track the attempted In-App purchases and their Type of SKU being purchased (Monthly/Annual/Home/Personal). The following fields are collected:
Office.FirstRun.Apple.InAppRestoreAttemptedThis event is collected for Office applications running under Apple platforms. The event is used to monitor the health of our application in-app purchase flow. We collect data to track the attempted In-App restorations The following fields are collected:
Office.FirstRun.Apple.InAppRestoreAttemptFailedThis event is collected for Office applications running under Apple platforms. The event is used to monitor the health of our application in-app purchase flow. We collect data to track the attempted In-App restorations and their associated flows and errors. The following fields are collected:
Office.FirstRun.Apple.MacFirstRunCompletedThis event is collected for Office applications running under Apple platforms. The event lets us know a user has gone through first run experience. We use this event to figure out if the First Run-Experience (FRE) was completed successfully. The following fields are collected:
Office.FirstRun.Apple.MacWXPFirstRunStartedThis event is collected for Office applications running under Apple platforms. The event lets us know a user has entered first run experience. We use this event to figure out if the First Run-Experience (FRE) was started successfully. The following fields are collected:
Office.Floodgate.UserFact.AppUsageThis indicates when a user has used high value features within the product. It may indicate if the user discovered the feature or used it. The signal will feed feature usage product insights that help make the product better. The following fields are collected:
Office.Lens.LensSdk.CloudConnectorLaunchWhen the user crops the image and taps confirm on the final image selection for using OCR, this event is collected. This is user-to-request record for the service as there is no user-to-service-job mapping on the service. UserId is required to fulfill GDPR requirements as service is not directly exposed to users, but through clients and identify the total number of people using the service, helping the service track the volume of users using the product, as well as identifying changes in trends, help look for and rectify issues in the product. The following fields are collected:
Office.Lens.LensSdk.CloudConnectorUploadErrorIn Image to Table, when the user taps either Share, Copy or Open, the corrections in the table made by the user are shared with the service to improve the OCR. This event is collected on the error response of that service and contains the relevant identifiers to troubleshoot various issues on the service. The following fields are collected:
Office.Lens.LensSdk.CloudConnectorUploadSuccessIn Image to Table, when the user taps either Share, Copy or Open, the corrections in the table made by the user are shared with the service to improve the OCR. This event is collected on the successful response of that service and contains the relevant identifiers to troubleshoot the process. It also helps analyze the usage of service improvement pipeline. The following fields are collected:
Office.Lens.LensSdk.SaveMediaThis event is invoked when the user clicks on the done button and saves images on Android and iOS. It helps measure the level of user engagement by quantifying users who end up saving images through our app. The following fields are collected on Android:
The following fields are collected on iOS:
Office.Lens.LensSdk.ServiceIDMappingThis event is collected when Lens SDK interacts with Microsoft’s Image-to-document (or I2D) service. This means that the event is called:
The data is used to analyse the usage and troubleshoot issues on the service side. The following fields are collected:
Office.LivePersonaCard.ConfigurationSetActionWe log when the user is in an app that loads a Persona Card in anticipation of the user opening the Live Persona Card. The data is used to determine whether the card loaded correctly. The following fields are collected:
Office.LivePersonaCard.UserActions.ClosedExpandedPersonaCardLogged when the user closes an expanded Persona Card. It is used to observe critical anomalies in failure rates of closing the Live Persona Card. The following fields are collected:
Office.LivePersonaCard.UserActions.ClosedPersonaCardWe log when the user closes a Persona Card. The data is used to determine whether the card closed correctly. The following fields are collected:
Office.LivePersonaCard.UserActions.OpenedExpandedPersonaCardLogged when the user opens an expanded Persona Card. It is used to observe critical anomalies in failure rates of launching the Live Persona Card. The following fields are collected:
Office.LivePersonaCard.UserActions.OpenedPersonaCardLogged when the user opens a Persona Card. It is used to observe critical anomalies in failure rates of launching the Live Persona Card. The following fields are collected:
Office.Manageability.Client Fetch.PolicyPreChecksCritical telemetry to track failure\success for cloud policy fetch precheck validation. ExitReason contains an enumerator map to the pre-check condition that failed. The following fields are collected:
Office.Manageability.Client.Fetch.AndApplyPolicyCritical telemetry to track failure\success for cloud policy fetch initiation from app. Exit Reason contains an enumerator Map to the failure reason. The following fields are collected:
Office.OfficeMobile.Fluid.FluidFileOperationsThis event is collected for Office applications when a fluid file operation takes place. Data is used to track feature health and understand user-experience based on the operation information. The following fields are collected:
Office.OfficeMobile.Lens.LensRequiredUsageThis event is triggered when one of the following things happens:
The following fields are collected:
Office.OfficeMobile.PdfViewer.PdfFileOperations (on Android)The event is collected for the Office app for Android. It records when a .pdf open, close, or save operation takes place and is used to understand and prioritize the user experience based on .pdf file operation information. The event enables us to keep the .pdf open, close, and save operations performing as expected, and to improve .pdf file operation performance. The following fields are collected:
Office.OfficeMobile.PdfViewer.PdfFileOperations (on iOS)The event is collected for the Office app for iOS. It records when a .pdf open, close, or save operation takes place and is used to understand and prioritize the user experience based on .pdf file operation information. The event enables us to keep the .pdf open, close, and save operations performing as expected, and to improve .pdf file operation performance.
Office.OfficeMobile.Search.VoiceSearchUsageThis event is triggered when the user taps on the microphone in the search box inside the Office Mobile app. The event will track the usage of voice search and also time taken to establish service request post tap on microphone. This data will be used to track the usage and health of the feature. The following fields are collected:
Office.OneNote.Android.App.Navigation.NavigationUIStateChanged[This event was previously named OneNote.App.Navigation.NavigationUIStateChanged.] This event collects the critical signal used to ensure OneNote users can successfully navigate through the app. The telemetry is used to ensure critical regression detection for OneNote app and service health. The following fields are collected:
Office.OneNote.Android.Canvas.PageCreatedThis event is triggered when a new OneNote page is created. The data is used to monitor, detect and fix any issues caused when a page is created in OneNote. The following fields are collected:
Office.OneNote.Android.Canvas.PageOpened[This event was previously named OneNote.Canvas.PageOpened.] This event is triggered when a Page is opened. The telemetry is used to monitor, detect, and fix any issues caused when a Page is opened in OneNote. The following fields are collected:
Office.OneNote.Android.Capture.NewNote.NewNoteTaken[This event was previously named OneNote.Capture.NewNote.NewNoteTaken.] This signal is used to ensure that after a user signs-into a OneNote Android App, notebooks are properly provisioned, and user has successfully created a new note. This is used to ensure critical regression detection for OneNote app and service health. The following fields are collected:
Office.OneNote.Android.LensSDK.OfficeLensLaunched[This event was previously named OneNote.LensSDK.OfficeLensLaunched.] This event collects the critical signal used to ensure that OfficeLens is launched correctly. The telemetry is used to ensure critical regression detection for OneNote app and service health. The following fields are collected:
Office.OneNote.Android.MessageBar.MessageBarClicked[This event was previously named OneNote.MessageBar.MessageBarClicked.] The signal used to indicate any issues encountered while using Message Bar. The telemetry is used to monitor, detect, and fix any issues caused during interaction with Message Bar The following fields are collected:
Office.OneNote.Android.StickyNotes.NoteCreatedCritical signal that is used to monitor the ability of Sticky Notes users to create notes in the app. Telemetry is used to ensure critical regression detection for OneNote app and service health. If users can’t create a note, this would trigger a high severity incident. The following fields are collected:
Office.OneNote.Android.StickyNotes.NoteViewedCritical signal that is used to monitor the ability of Sticky Notes users to view notes in the app. Telemetry is used to ensure critical regression detection for OneNote app and service health. If users can’t view their notes, this would trigger a high severity incident. The following fields are collected:
Office.OneNote.Canvas.Ink.InkStrokeLoggerThis event is used to detect and diagnose a high frequency bug that a user encounters while using Ink feature. This will be used to determine the most appropriate mode of fixing this issue. The following fields are collected:
Office.OneNote.FirstRun.FirstRunDurationsBreakdownThe event is triggered upon completion of provisioning of the user in the app. This happens right after user signs into the app for the first time. The event collects durations of different stages of provisioning. The data will help Microsoft determine which stages of provisioning consume the most time and help us develop a solution to reduce the time taken. The following fields are collected:
Office.OneNote.Navigation.CreatePageCritical signal used to monitor the ability of OneNote users to create pages in OneNote. Telemetry used to ensure critical regression detection for OneNote app and service health. If users can't create a page this would trigger a high severity incident. The following fields are collected:
Office.OneNote.Navigation.CreateSectionCritical signal used to monitor the ability of OneNote users to create sections in OneNote. Telemetry used to ensure critical regression detection for OneNote app and service health. If users can't create a page this would trigger a high severity incident. The following fields are collected
Office.OneNote.Navigation.NavigateCritical signal used to monitor the ability of OneNote users to navigate between pages in OneNote. Telemetry used to ensure critical regression detection for OneNote app and service health. If users can't navigate this would trigger a high severity incident. The following fields are collected:
Office.OneNote.NotebookManagement.CreateNotebookCritical signal used to monitor the ability of OneNote users to create notebooks in OneNote. Telemetry used to ensure critical regression detection for OneNote app and service health. If users can't create notebooks this would trigger a high severity incident. The following fields are collected:
Office.OneNote.NotebookManagement.OpenNotebookCritical signal used to monitor the ability of OneNote users to open notebooks in OneNote. Telemetry used to ensure critical regression detection for OneNote app and service health. If users can't open notebooks this would trigger a high severity incident. The following fields are collected:
Office.OneNote.Search.SearchCritical signal ID used to monitor the ability of OneNote users to find information across thousands of pages and notebooks. Telemetry used to ensure critical regression detection for OneNote app and service health. If users can't find information across notebooks this would trigger a high severity incident. The following fields are collected:
Office.OneNote.SIGS.CriticalErrorEncounteredThis event captures a critical signal that is used to monitor the health of Signal Ingestion Service (SIGS), by logging whenever a critical error is encountered. Critical errors can block the whole of SIGS, and this will help us catch any such issues as soon as they are encountered by users. Without this, we will be dependent on users to report the problems they are facing. Absence of such telemetry would make the turnaround time for such issues much higher. The following fields are collected:
Office.OneNote.StickyNotes.NoteCreated (on iOS), OneNote.StickyNotes.NoteCreated (on Android)This is a critical signal that is used to monitor the ability of Sticky Notes users to create notes in the app. Telemetry is used to ensure critical regression detection for OneNote app and service health. If users can't create a note, this would trigger a high severity incident. The following fields are collected:
Office.OneNote.StickyNotes.NoteViewed (on iOS), OneNote.StickyNotes.NoteViewed (on Android)This is a critical signal that is used to monitor the ability of Sticky Notes users to create notes in the app. Telemetry is used to ensure critical regression detection for OneNote app and service health. If users can't create a note, this would trigger a high severity incident. The following fields are collected:
Office.OneNote.Storage.NotebookSyncResultThis event logs notebook sync result. It is used for figuring out how many unique sync targets when calculating OneNote sync score. The following fields are collected
Office.OneNote.System.AppLifeCycle.AppLaunchThe critical signal used to ensure OneNote users can successfully launch the app. The telemetry is used to ensure critical regression detection for OneNote app and service health. If users can't launch the app in our performance window, this would trigger a high severity incident. The following fields are collected: None Office.Outlook.Desktop.AccountConfiguration.CreateAccountResultResult of adding an account to Outlook in a new profile, from the Office Backstage, or from the account settings dialog. The data is actively monitored to ensure we don't see any spikes in failures. We also analyze the data to find areas of improvement. We aim to improve this success rate with each release. The following fields are collected:
Office.Outlook.Desktop.AccountConfiguration.RepairAccountResultResult of repairing an account or changing advanced account settings. The data is actively monitored to ensure we don't see any spikes in failures. We also analyze the data to find areas of improvement. Since this a new (refactored) experience we want to make sure we got this right. The following fields are collected:
Office.Outlook.Desktop.AccountConfiguration.UpdatePasswordResultResult of updating an account's password from the Account Settings dropdown. The data is actively monitored to ensure we don't see any spikes in failures. We also analyze the data to find areas of improvement. Since this a new (refactored) experience we want to make sure we got this right. The following fields are collected:
Office.Outlook.Desktop.Stores.CreateNewStoreCollects the result of creating a new store (with type and version), and the result code. We actively monitor this event to track the health a user's ability to sync and store mail locally, archive mails (in a PST), or use Groups. The following fields are collected:
Office.Outlook.Mac.AccountAddWorkflowResult of adding an account in Outlook. The data is monitored to ensure we don't see any spikes in failures. We also analyze the data to find areas of improvement. We aim to improve this success rate with each release. The following fields are collected:
Office.Outlook.Mac.AccountOnboardingFlowResult of adding an account in Outlook using new account configuration experience. The data is monitored to ensure we don't see any spikes in failures. We also analyze the data to find areas of improvement. We aim to improve this success rate with each release. The following fields are collected:
Office.Outlook.Mac.DeleteAccountUsageResult of deleting an account in Outlook. The data is monitored to ensure we don't see any spikes in failures. We also analyze the data to find areas of improvement. We aim to improve this success rate with each release. The following fields are collected:
Office.PowerPoint.DocOperation.CloseCollected when PowerPoint presentations are closed. It contains the information needed to be able to properly investigate and diagnose issues that happen through the close process which entail persisting and syncing the user's data. Microsoft uses this data to ensure that close is working as expected and user content is successfully being persisted. The following fields are collected:
Office.PowerPoint.DocOperation.NewDocumentCollected when PowerPoint creates a new presentation. Includes success failure and performance metrics. This information is used to ensure we can create files successfully and with no degradation in performance. The following fields are collected:
Office.PowerPoint.DocOperation.OpenCompleteProtocolCollected when PowerPoint opens presentations. It contains the information needed to be able to properly investigate and diagnose issues that happen through the end stages of the open process. Microsoft uses this data to ensure the feature is working as expected and there is no degradation to opening presentations. The following fields are collected:
Office.PowerPoint.DocOperation.SaveCollected whenever PowerPoint performs a save using the modern code path. Includes success or failure result type of save performance metrics and relevant document metadata. Failures in save can result in data loss. Microsoft uses this data to ensure the feature is working as expected and user content is successfully being persisted. The following fields are collected:
Office.PowerPoint.DocOperation.SaveAsCollected whenever PowerPoint performs a Save As. Includes success or failure result type of save performance metrics and relevant document metadata. Failures in save can result in data loss. Microsoft uses this data to ensure the feature is working as expected and user content is successfully being persisted. The following fields are collected:
Office.PowerPoint.DocOperation.SaveLegacyCollected whenever PowerPoint performs a save using the legacy code path. Includes success or failure result type of save performance metrics and relevant document metadata. Failures in save can result in data loss. Microsoft uses this data to ensure the feature is working as expected and user content is successfully being persisted. The following fields are collected:
Office.PowerPoint.PPT.Android.RehearseView.FeedbackReceivedThis event is used to analyze the seen/tried/kept funnel of the feature. This event along with Seen and Tried event helps us determine if users are dropping out of the funnel. The data is used to determine into if users are dropping because of errors faced during the experience. This helps us maintain the health of the feature. The following fields are collected:
Office.PowerPoint.PPT.Android.RehearseView.SessionStartedThis event is used to analyze the seen/tried/kept funnel of the feature. This event along with Seen and Kept event helps us figure out if users are dropping out of the funnel. This data is used to understand if users are dropping because of errors faced during experience. This helps us maintain the health of the feature. The following fields are collected:
Office.PowerPoint.PPT.IOS.RehearseViewThis event is denoting that user has stopped the rehearsal session. The data is used in combination with Office.PowerPoint.IOS.Android.RehearseView.StartSession as the first indicator of any crashes or errors that user faces. The following fields are collected:
Office.PowerPoint.PPT.IOS.RehearseView.RehearsalSummaryPageEvent is triggered when summary page has finished loading. This event helps us capture the performance of the summary page. It tells how much time it takes for the rehearsal summary service page to load on the client. It is required to keep the feature performant. The following fields are collected:
Office.PowerPoint.PPT.IOS.RehearseView.StartSessionThis event is triggered when the user clicks on start session. This event helps us capture how many users are using the Presenter coach feature on iOS. When combined with Office.PowerPoint.PPT.iOS.RehearseView it will tell us how many users successfully completed the rehearsal session and how many couldn’t. This is our first indicator of crashes or errors in the feature. The following fields are collected:
Office.PowerPoint.PPT.Mac.Shell.PrintInfoCollected whenever an export PDF operation has completed and contains information about the success of the operation. This information is critical to identify the success of export PDF operations for our application. The following fields are collected:
Office.PowerPoint.PPT.Shared.RehearseView.RehearseClickedThis event captures when RehearseWithCoach is clicked. This event is used to analyze the seen- tried-kept funnel of the feature. This event along with tried and kept event helps us figure out if users are dropping out of the funnel. This helps us maintain the health of the feature. The following fields are collected:
Office.PowerPoint.PPT.Shared.SlideShow.FailureCollecting failures during slide show as a key feature for PowerPoint. Microsoft is collecting when error happens during slide show to help improve user experience on slide show. Microsoft uses this data to get diagnostic information about where the error happens while user is using slide show. The following fields are collected:
Office.PowerPoint.Rehearsal.RehearseAgainThis event captures when Rehearse Again is clicked in the summary report. This event is used to analyze the success of the PowerPoint Coach entry points, and is an indicator of the health of the feature. The following fields are collected:
Office.PowerPoint.RunPrintOperationCollected whenever a print PDF operation has completed and contains information about the layout type, use of slide numbers, and the success of the operation. This information is critical to identify the success of print PDF operations for our application. The following fields are collected:
Office.Project.ProjectFileSaveProject saves a file. This event indicates a Project save. It allows Microsoft to measure success of Project saving a file, which is important to avoid document data loss. The following fields are collected:
Office.Session.Activity.StartAllows us to know when a data streamer session has started. Used for feature health and monitoring. This event is generated by Microsoft Data Streamer for Excel Add-in. The following fields are collected:
Office.Session.Activity.StopAllows us to know when a data streamer session has stopped Used for feature health and monitoring. This event is generated by Microsoft Data Streamer for Excel Add-in. The following fields are collected:
Office.StreamDevice.Activity.StartAllows us to know if start streaming data source is successful. Used for feature health and monitoring. This event is generated by Microsoft Data Streamer for Excel Add-in. The following fields are collected:
Office.StreamDevice.Activity.StopAllows us to know if stop streaming data source is successful. Used for feature health and monitoring. This event is generated by Microsoft Data Streamer for Excel Add-in. The following fields are collected:
Office.TargetedMessaging.ABExperimentMessageTriggerTracks the number of users receiving BizBar and Dynamic Canvas messages from TargetedMessagingService (TMS). This data is critical to understand what messages users are getting and on what surface so that we can ensure they are not missing any messages that may be critical to their continued use of the product. Also needed to accurately measure the success of our experiments and campaigns run through TMS. The following fields are collected:
Office.Text.FontPickerFontSelected.Win32This event indicates whether the downloaded font was rendered correctly. Used to indicate success or failure of Font Download. The following fields are collected:
Office.Text.ResourceClient.RequestResourceInternalThis event indicates whether the font was downloaded correctly. Used to indicate success or failure of rendering the downloaded font. The following fields are collected:
Office.Translator.DocumentTranslatedCollects success or failure of a full document translation a user trigger in the Translator SDX. This is critical to evaluate the health of the translation feature and react to any outages that might occur. Monitor the health of the "Translate Document" scenario in Word. The following fields are collected:
Office.Translator.TextTranslatedCollects success or failure of a selection translation that a user action triggers in the Translator SDX. This is critical to evaluate the health of the translation feature and react to any outages that might occur. Used to monitor the health of the "Translate Selection" scenario in Excel, PowerPoint, Word. The following fields are collected:
Office.UX.AccChecker.AccCheckerFinalViolationCountPerRuleThis event is triggered when Accessibility issues are reported for the currently opened document. This event represents the Accessibility violations (Errors, Warnings, and Tips) that exist per Rule, for the opened document at the beginning and end of the session. This event is used to record the counts of Accessibility violations (Errors, Warnings, and Tips) per Rule, for the opened document at the beginning and end of the session. Details of violation counts per rule help Microsoft to identify which Accessibility issues are most common in Office documents. This helps with work on remediating them and drives the creation of an inclusive environment in the workplace and classroom for people with disabilities. The following fields are collected:
Office.UX.AccChecker.AccCheckerViolationInformationThis event is triggered when Accessibility issues are reported for the currently opened document. It represents the aggregate counts of violations (Errors, Warnings, and Tips) for the opened document at the beginning and end of the session. This event is used to record the aggregate counts of Accessibility violations (Errors, Warnings, and Tips) for the opened document at the beginning and end of the session. The knowledge of Accessibility checker usage allows Microsoft to improve its application experiences to be more inclusive for people with disabilities in Office usage scenarios for the workplace and classroom. The following fields are collected:
Office.UX.AccChecker.BackgroundAccCheckerEnabledStateThis event is triggered when the user or IT Admin has enabled the Background Accessibility checker for the Office user. This event is used to understand the instances when the Background Accessibility checker is enabled for Office users. The enabled status of the Background Accessibility checker allows Microsoft to understand if documents can be scanned automatically in the background. This helps to create a more inclusive workplace and classroom environment for people with disabilities. The following fields are collected:
Office.UX.AccChecker.BackgroundScanningCheckboxClickedThis event is triggered when the user enables the Background Accessibility checker from the Accessibility checker task pane. This event is used to understand the instances when the Background Accessibility checker is enabled for Office documents. The enabled status of the Background Accessibility checker allows Microsoft to understand if documents can be scanned automatically in the background. This helps to create a more inclusive workplace and classroom environment for people with disabilities. The following fields are collected:
Office.UX.AccChecker.DisabledResultsThis event is triggered when the Accessibility Checker gets disabled for the opened document. This event is used to understand the instances when the Office Accessibility checker gets disabled, due to a legacy or unsupported Office document. The disabled status of the Accessibility checker allows Microsoft to understand how often a document cannot be scanned, and to assist users in allowing the scanning of such documents – by upconverting the document to a modern file format. This helps to create a more inclusive workplace and classroom environment for people with disabilities. The following fields are collected:
Office.UX.AccChecker.ShowTaskPaneThis event is triggered when the Accessibility Checker task pane is launched for the currently opened document. This event is used to understand the usage of the Office Accessibility Checker. The Accessibility Checker is used to identify and remediate Accessibility issues in Office documents. The knowledge of Accessibility Checker usage allows Microsoft to improve its application experiences to be more inclusive for people with disabilities in Office usage scenarios for the workplace and classroom. The following fields are collected:
Office.Visio.Shared.FeatureExperimentationTracks feature flighting for users. This event helps us determines success or failure of feature flights. The following fields are collected:
Office.Visio.Shared.RefreshSmartDiagramCaptures diagram refresh failures when file is created through DV. This helps us debug the failures and issues in data refresh in a DV diagram. The following fields are collected:
Office.Visio.Shared.WritebackToExcelCaptures Excel write back failures when file is created through DV. This helps us debug the failures and issues in writing back data to Excel in a DV diagram. The following fields are collected:
Office.Word.Accessibility.LearningTools.ReadAloud.EventName.ReadAloudGetDataFromCacheThe event is triggered when user listens to a paragraph that has already been prefetched and Read Aloud will be playing the cached paragraph now instead of making a request to EDU service to get the neural voice. The data helps track how many of users are using previously-fetched paragraphs thereby giving usage ideas along with the solidifying our calculation for Read Aloud play minutes since the paragraphs which are read from cache are currently not getting tracked. Data is used to track the usage of Read Aloud neural implementation via cached files, how many minutes are being generated. The following fields are collected:
Office.Word.FileNew.CreateNewFileThis event indicates that a new document is created in Office Word and tracks success or failure of the operation. The event is used to monitor that new document creation is working as expected. It is also used to calculated monthly active users/devices and cloud reliability metrics. The following fields are collected:
Office.Word.FileOpen.UserInitiatedOpenThis event indicates Office Word opens a document by user initiation instead of by Office Word programmatically. It also contains critical file open performance data and is an app start event from user perspective. The event monitors whether file-open is working as expected. It is also used to calculated monthly active users/devices, and cloud reliability metrics. The following fields are collected:
Office.Word.FileSave.ActCmdGosubSaveAsThis event indicates that a user is saving their changes to a new document. The event monitors whether saving to a new document is working as expected. It is also used to calculated monthly active users/devices and cloud reliability metrics. The following fields are collected:
Office.Word.FileSave.ActFConfirmSaveDocCoreQuerySaveThis event indicates Office Word prompts the user to save changes when it tries to close the document. It allows Microsoft to monitor whether save-at-quit works as expected to avoid document data loss. The event monitors whether save-at-quit is working as expected. It is also used to calculated monthly active users/devices and cloud reliability metrics. The following fields are collected:
Office.Word.FileSave.SaveAsSaveFileThis event indicates Office Word saves a document into a new document. It allows Microsoft to detect errors in save-as which is important to avoid document data loss. The event monitors whether save-as is working as expected. It is also used to calculated monthly active users/devices and cloud reliability metrics. The following fields are collected:
Office.Word.Word.DocumentDirtyFlagChangedThis event indicates Office Word edits a document that changes the document internal state into "dirty". It allows Microsoft to evaluate the feature health of edit-document. The event is a heartbeat of user edits. It is also used to calculated monthly active users/devices. The following fields are collected:
OneNote.App.Navigation.RatingReminderDialogShownThe critical signal used to measure effectiveness of trigger logic for Rating reminder. This dialog is shown when the user has met all the conditions to see the rating reminder (no. of active days, has rated previously or not, etc.). This is used to ensure that the trigger logic for Rating reminder. If the users are seeing this dialog, it will provide us with ways to receive feedback from the customers on the right time and improve app health. The following fields are collected:
ParseLicenseOpCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when parsing licenses operation is performed. The following fields are collected:
qr.code.scanThis event lets us know when a user signs into Outlook Mobile by scanning an auth QR code on a desktop Outlook client which securely contains the user's sign-in information, thereby eliminating the need for manual sign-in. The event is used to detect the successful initiation and completion of the user authentication process using QR functionality. The event diagnoses sign-in errors that could prevent the user from successfully authenticating in the mobile app. The following fields are collected:
read.conversationThis event is triggered when an email is not visible on the device screen anymore. Used for monitoring possible negative impact on the health and performance of rendering an email message. The following fields are collected:
save.attemptAllows us to identify the impact of issues caused by users attempting to save a file by evaluating the number of sessions impacted and if there are common features of those sessions. The following fields are collected:
search.subtab.selectedThe event collects origin points for the reason a search sub_tab was selected. The sub tabs sit under the primary app search bar to filter data. This event lets us track the entity type pills (all, mail, contacts, and calendar) that users are using when they do their searches so we can ensure the search filter mechanisms are working properly. The following fields are collected:
send.messageThis event is triggered when the user has finished composing and taps the send button. Data collected indicates possible negative impact on the performance and health of sending email messages. The data is used to understand if the feature is functioning successfully. The following fields are collected:
sessionAllows us to detect and fix situations where we are using up too much of your device's battery and helps us identify what could be the cause. The following fields are collected:
settings.actionThis event collects the configuration information in settings. The data allows us to detect situations where there is possible negative impact on the users’ ability configure app settings, such as notification settings, primary mail account, and configuring the email signature. The following fields are collected:
sidebar.actionAllows us to detect situations where there is possible negative impact on your ability configure your app settings, such as your notification settings, your primary mail account, and configuring your mail signature. Data fields that are common for Outlook Mobile for this event on iOS and Android:
The following fields are collected:
StoreOpCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when Rights Management Service license store operation is performed. The following fields are collected:
Survey.Floodgate.TriggerMetTracks when a device has met the criteria to show a survey. Used to assess the health of the survey triggering process as well as to ensure the signal used to analyze customer issues and health is working properly. The following fields are collected:
Survey.UI.Form.SubmitTracks when a survey is submitted. Used to assess the health of the survey submission process as well as to ensure the signal used to analyze customer issues and health is working properly. The following fields are collected:
watchAppV2This event is triggered from the Outlook watch app, when notifications are communicated from Outlook mobile to the Outlook watch app, and when the user is performing actions in the Outlook watch app. This event allows us to detect and fix possible issues with capabilities on the watch, such as receiving notifications and responding to emails. The following fields are collected:
Application status and boot subtypeDetermination if specific feature events have occurred, such as start or stop, and if feature is running. app.startupThis event lets us detect and fix issues where Outlook is starting slowly or incompletely, making it difficult for users to use our app. This includes information on the specific features that were enabled and how long parts of the startup took. The following fields are collected:
boot.timeThis event lets us detect when critical app errors occurred that would cause your app to crash or experience serious issues like causing you to see empty rows in your inbox. This event collects information that allows us to categorize and classify issues to help prioritize the impact of issues on customers. The following fields are collected:
DnsLookupOpCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when DNS information lookup operation is performed. The following fields are collected:
first.visibleThis event lets us detect the first time the app is launched intentionally by the user. This event is required to ensure that the app is successfully working in Original Equipment Manufacturer (OEM) builds. The following fields are collected:
GetUserOpCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when getting user certificates operation is performed. The following fields are collected:
HttpOpCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when http request operation is performed. The following fields are collected:
InitializedAllows us to analyze the health of the interface that allows mobile apps to fetch user and privacy settings from Office services and diagnose connectivity and privacy setting service issues. The following fields are collected:
IpcCreateOauth2TokenCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when the IpcCreateOauth2Token API call is made. The following fields are collected:
Office.Android.AccountStorageInfoThis event determines the number of MSA and ADAL accounts in the registry and shared preferences. It enables the analysis of inconsistencies between data stores and helps us to stabilize app performance. The following fields are collected:
Office.Android.AndroidOffice16BootLatencyCritical to capture for app performance metric with respect to the response time of the app from the boot. Microsoft uses this to collect the time taken for the app to be responsive and also detect scenarios that may impact boot time in Word, Excel, or PowerPoint. The following fields are collected:
Office.Extensibility.OfficeJS.AppactivatedRecords information about unexpected shutdowns of Office. This allows us to identify crashes or hangs in the product so that they can be addressed. The following fields are collected:
Office.Extensibility.Sandbox.ODPActivationHangingCollects when an Office add-in takes unexpectedly long to launch (>5 sec). Used to detect and fix problems with Office add-ins launching. The following fields are collected:
Office.Lens.LensSdk.LaunchLensLaunches help us determine the number of users or devices launching the app and further understand feature usage. It helps us track the volume of users using the product, as well as identifying changes in trends, help look for and rectify issues in the product. The following fields are collected on Android:
The following fields are collected on iOS:
Office.OfficeMobile.AppActivation.LaunchThis event identifies first time and subsequent activations through external triggers that activate the app. App activation loads certain dependencies that are responsible for making the app run smoothly and this event will record if it loaded successfully. It will also record the source of activation and app intent that was responsible for activating the app The following fields are collected:
Office.OfficeMobile.FRE.FirstRunSetupThe first run of the app after installation will trigger this heartbeat event. It will help identify installs and auto upgrades from older versions of the app and enable us to identify errors in auto-upgrades, including library loads and expansion/language package download failures. The following fields are collected:
Office.OneNote.Android.App.AppBootComplete, Office.Android.EarlyTelemetry.AppBootComplete[This event was previously named OneNote.App.AppBootComplete.] The event is recorded once every session when the app boot is completed. The data is used to ensure new consumer users can successfully launch and use OneNote for the first time and, to ensure critical regression detection for the OneNote app and service health. The following fields are collected:
Office.OneNote.Android.App.OneNoteAppForeground, Office.Android.EarlyTelemetry.OneNoteAppForeground[This event was previously named OneNote.App.OneNoteAppForeground.] The signal used to indicate OneNote App is in foreground. The telemetry is used to ensure critical regression detection for OneNote app and service health. The following fields are collected:
Office.OneNote.Android.AppLaunch, Office.Android.EarlyTelemetry.AppLaunch[This event was previously named OneNote.AppLaunch.] The critical signal used to ensure OneNote users can successfully launch the app. The telemetry is used to ensure critical regression detection for OneNote app and service health. The following fields are collected:
Office.Outlook.Desktop.ExchangePuidAndTenantCorrelationCollects the user PUID and Tenant Identifier once per session. The correlation of PUID and Tenant are necessary to understand and diagnose Outlook issues on a per-tenant basis. The following fields are collected:
Office.Outlook.Mac.MacOLKActivationStateCollects how Outlook is activated, such as with a subscription or volume license. The data is monitored to ensure we don't see any spikes in failures. We also analyze the data to find areas of improvement. The following fields are collected:
Office.PowerPoint.DocOperation.OpenCollected whenever PowerPoint opens a file. Contains success information, failure details, performance metrics, and basic details about the file including file format type and document metadata. This information is necessary to ensure PowerPoint can open files successfully with no degradation in performance. It allows us to diagnose any problems we discover. The following fields are collected:
Office.PowerPoint.PPT.Desktop.BootimeCollecting how PowerPoint is booted. It includes boot PowerPoint in protected view, in assisted reading mode, from Macro, print, new and blank document, document recovery, from automation and if it is click- to-run. It also collects how long it takes PowerPoint to boot. This data is critical to guarantee PowerPoint performs well when booted from different modes. Microsoft uses this data to catch long booting time when opening PowerPoint from different modes. The following fields are collected:
Office.PowerPoint.PPT.HasUserEditedDocumentCollected when a user starts editing a document. Microsoft uses this data to calculate active users who edited a PowerPoint document The following fields are collected:
Office.Project.BootAndOpenProjectProject is booted by opening a file. This event indicates that a user has opened Office Project with an associated file. It contains critical success data of making sure Project can start and load a file. The following fields are collected:
Office.Project.BootProjectProject is booted without opening a file. This event indicates that a user has opened Office Project without an associated file. It contains critical success data of making sure Project can start. The following fields are collected:
Office.Project.OpenProjectProject opens a file. This event indicates a user directly opening a Project file by a user. It contains critical success data of opening files in Project. The following fields are collected:
Office.SessionIdProvider.OfficeProcessSessionStartApplicable to all the Office windows-based applications: win32 and UWP The following fields are collected:
Office.System.SessionHandoffIndicates that the current Office session is a handoff session. This means that handling of a user's request to open a document is being handed off to an already running instance of the same application. The following fields are collected.
Office.TelemetryEngine.IsPreLaunchApplicable for Office UWP applications. This event is fired when an Office application is initiated for the first-time post upgrade/install from the store. This is part of basic diagnostic data, used to track whether a session is launch session or not. The following fields are collected:
Office.TelemetryEngine.SessionHandOffApplicable to Win32 Office applications. This event helps us understand whether there was a new session created to handle a user-initiated file open event. It is a critical diagnostic information that is used to derive reliability signal and ensure that the application is working as expected. The following fields are collected:
Office.Visio.VisioIosAppBootTimeThis is triggered every time the Visio iOS application boots. It is essential to understand boot performance of the Visio iOS app. Used to troubleshoot poor performance. The following fields are collected:
Office.Visio.VisioIosAppResumeTimeThis event is triggered every time the Visio iOS app resumes focus. It is essential to measure app resume performance and troubleshoot performance issues of Visio iOS app. The following fields are collected:
Office.Word.FileOpen.OpenCmdFileMruPrivThis event indicates Office Word opens a document from the Most Recent Used (MRU) list. It also contains critical file open performance data and is an app start event from user perspective. The event monitors whether fileopen-from-MRU is working as expected. It is also used to calculated monthly active users/devices, and cloud reliability metrics. The following fields are collected:
Office.Word.FileOpen.OpenFFileOpenXstzCoreThis event indicates Office Word opens a document who is double-clicked by a user. It also contains critical file open performance data and is an app start event from user perspective. The event monitors whether file-openfrom-file-double-click is working as expected. It is also used to calculated monthly active users/devices, and cloud reliability metrics. The following fields are collected:
Office.Word.FileOpen.OpenIfrInitArgsThis event indicates Office Word opens a document via COM activation or command line. It also contains critical file open performance data, and is an app start event from user perspective. The event monitors whether file-open-from-command-line is working as expected. It is also used to calculated monthly active users/devices, and cloud reliability metrics. The following fields are collected:
Office.Word.FileOpen.OpenLoadFileThis event indicates Office Word opens a document via Open dialog. It also contains critical file open performance data and is an app start event from user perspective. The event monitors whether file-open-from-the-open-filedialog is working as expected. It is also used to calculated monthly active users/devices, and cloud reliability metrics. The following fields are collected:
RenewUserOpCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when renew user certificates operation is performed. The following fields are collected:
ServiceDiscoveryOpCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when service discovery operation is performed. The following fields are collected:
sharedcore.bootstagestatisticsThe event is triggered during start-up and shutdown as various layers of the application complete their phase of process. The event captures performance markers for each layer of application start-up and shutdown. The data is used to determine if the app is healthy and performing as expected. The following fields are collected:
Common Fields (documented once for the set of Required events for the app)
Office accessibility configuration subtypeOffice accessibility features Office.Accessibility.AccessibilityToolSessionPresenceWin32Allows us to detect that the user has an Assistive technology tool and its name. This allows us to understand if an Office user is experiencing issues with a specific Assistive Technology tool. The following fields are collected:
Office.Apple.DarkModeThis event is collected for Office applications running under Apple platforms. The event tells us if user is running a System on DarkMode and whether the user overwrote the DarkMode System setting in Office. We use this event to help ensure accessibility and prioritize user-experience optimization. The following fields are collected:
Office.Apple.HardwareKeyboardInUse.AppleThis event is collected for Office applications running under Apple platforms. The event tells us that a user is attaching a keyboard to their mobile device. The event helps us improve accessibility and optimize our user experience. The following fields are collected:
Office.Apple.MbuInstrument.DeviceAccessibilitySettingsThis event is collected for Office applications running under Apple platforms. The event collects the state of the different accessibility options available during a session. We use this event to help ensure accessibility and prioritize user-experience optimization. The following fields are collected:
Office.UX.AccChecker.FixItMenuItemSelectionThis event is used to track the selected choice within the Accessibility Checker Fixit menu. The data allows Microsoft to understand how documents are being remediated to fix accessibility issues, which helps to create a more inclusive workplace and classroom environment for people with disabilities. The following fields are collected:
Office.UX.AccChecker.FixItMenuOpenCloseThis event is used to track the frequency with which the Accessibility Checker Fixit menu is invoked or dismissed. The data helps Microsoft understand the frequency with which and how documents are being remediated to fix accessibility issues. This contributes to a more inclusive workplace and classroom environment for people with disabilities. The following fields are collected:
Office.Word.Accessibility.LearningTools.ReadAloud.PlayReadAloudThis event indicates Office Word reads aloud the text in the document. The event is a heartbeat of the accessibility feature, which allows Microsoft to evaluate the feature health of read-aloud-text. The following fields are collected:
Office.Word.Accessibility.LearningTools.ReadAloud.StopReadAloudThis event indicates Office Word stops reading aloud the text in the document. The event allows Microsoft to evaluate the feature health of read-aloud-text by measuring the working duration. The following fields are collected:
Privacy subtypeOffice privacy settings Office.Android.DocsUI.Views.UpsellBlockedAADCThis event captures that subscription upsell was blocked for non-adult users when they encountered the upsell message in Word, Excel or PowerPoint mobile app. We will use the data to summarize how many upsell opportunities were lost due to age compliance. The following fields are collected:
Office.IntelligentService.PrivacyConsent.PrivacyEventThis event represents a user or system initiated action that is part of the privacy User experience for Office. It is triggered on the privacy First Run dialogs, Account Privacy dialog, and privacy notifications. The event is used to understand the following: users consenting to Office privacy settings, users changing Office privacy settings, and Office privacy settings getting updated in user sessions. The following fields are collected:
Office.OfficeMobile.FRE.UpsellBlockedAADCThis event captures that subscription upsell was blocked for non-adult users when they encountered the upsell message in the Office Mobile app. We will use the data to summarize how many upsell opportunities were lost due to age compliance. The following fields are collected:
Office.Privacy.OffersOptInThis event is triggered when values for privacy controls are loaded or reloaded. This happens when the user first boots the process and whenever these settings change, such as the user updating them or the values roaming from another device reports information about user’s opt-in status to Personalized Offers. The event is used to ensure that users' privacy choices related to the Personalized Offers control are being enforced as expected. The following fields are collected:
Office.Privacy.UnifiedConsent.UI.ConsentAcceptedThis event is triggered when a user accepts/acknowledges an account-level consent notice. Data is used to understand the frequency of successes and failures in client components, allowing detection and mitigation of common issues. The following fields are collected:
Office.Privacy.UnifiedConsent.UI.ConsentRenderFailedThis event is used to track a failure to properly render an account-level consent user interface. Data is used to understand the frequency of successes and failures in client components, allowing detection and mitigation of common issues. The following fields are collected:
Office.Privacy.UnifiedConsent.UI.ConsentRenderSuccessThis event is used to track successful rendering of user interface dialog for an account-level consent notice. Data is used to understand the frequency of successes and failures in client components, allowing detection and mitigation of common issues. The following fields are collected:
Product and service performance data eventsThe following are the data subtypes in this category:
Unexpected application exit (crash) subtypeUnexpected application exits and the state of the application when that happens. app.startup.reasonThis event lets us detect and fix issues where Outlook crashed during app startup. This event includes information on why the crash happened so we can fix the issue quickly. The following fields are collected:
The following fields are collected for only Outlook Mobile for iOS:
application.crashUsed for monitoring critical app crashes and helps us collect information on why the app has crashed and how to prevent it. The following fields are collected:
crash.eventAllows us to detect and fix situations where critical app crashes have occurred and helps us collect information on why the app has crashed and how to prevent it. The following fields are collected:
ErrorAllows us to understand the issues that mobile apps are facing when attempting to fetch privacy settings from the server. The following fields are collected:
Office.Android.EarlyTelemetry.UngracefulAppExitInfoThis event is triggered in each session and collects information about the exit reasons of the previous process of the app. The data is used to collect information on the Android process exit to help Office understand where apps are experiencing issues and diagnose them appropriately. The following fields are collected:
Office.AppDomain.UnhandledExceptionHandlerFailedCollects information for any unhandled exceptions using the Data Streamer App. This data is used to monitor the health of the application. This event is generated by Microsoft Data Streamer for Excel Add-in. The following fields are collected:
Office.Apple.IdentityDomainNameThis event is collected for Office applications running under Apple platforms. The event is used to monitor the health of our system as well as investigating causes of failures by certain domain users. We collect the domain used by our users when they authenticate. We use this data to help identify and fix those issues that might not seem too impactful at a broader level, but that turn out to be very impactful to a certain domain of users. The following fields are collected:
Office.Apple.SystemHealthAppExitMacAndiOSThis event is collected for Office applications running under Apple platforms. The event is used to monitor the health of our Office applications and for investigating causes of failures. We collect data on each application exit to determine whether an application exited gracefully. The following fields are collected:
Office.Extensibility.COMAddinUnhandledExceptionEvent generated when COM Add-in crashes on a consumer version of Office applications. This is used to compute a global, non-enterprise-specific Microsoft 365 Apps for enterprise "adoption" for an add-in, which is then used by tools like the Readiness Toolkit. This allows enterprise customers to validate if the add-ins they have deployed in their organizations are compatible with the latest versions of Microsoft 365 Apps for enterprise and plan their upgrades accordingly. The following fields are collected:
Office.Extensibility.COMAddinUnhandledExceptionEnterpriseEvent generated when COM Add-in crashes on an enterprise version of Office applications. This is used to compute a global, non-enterprise-specific Microsoft 365 Apps for enterprise "adoption" for an add-in, which is then used by tools like the Readiness Toolkit. This allows enterprise customers to validate if the add-ins they have deployed in their organizations are compatible with the latest versions of Microsoft 365 Apps for enterprise and plan their upgrades accordingly.
Office.Extensibility.Sandbox.ODPActivationHeartbeatOffice Add-ins run in a sandbox. This event collects heartbeat information on activations. When an add-in crashes, this event collects why it crashed in the case it's related to our sandbox. Used to investigate when customers escalate issues. The following fields are collected:
Office.Extensibility.VbaTelemetryBreakEvent generated when a macro-enabled file runs into a compile or runtime error Desktop Analytics: This is used as numerator in the computation of enterprise-specific health status for macro types (for example, Word macros, Excel macros, etc.) which is used to infer during pilot if the add-in is "ready to upgrade" in the production ring. The following fields are collected:
Office.FindTime.AppFailedToStartCollected when app fails to start due to an unexpected error during startup. Used to track exceptions & crashes. Helps monitor and debug app health. The following fields are collected:
Office.Outlook.Desktop.HangBucketMetricsCollects hang time for outlook hangs – a unique identifier per hang, elapsed time, and call stack information. The data is used to detect and identify app crashes in order to fix in future updates. The following fields are collected:
Office.Outlook.Desktop.HangReportingScopePerfMetricsCollects time taken for outlook core scenarios – switchfolder, switchmodule, sendmailoutbox, openitemclassic, sendmailtransport. The data is actively monitored for anomalous performance issues. It is used to detect and diagnose performance issues and improve performance with each update. The following fields are collected:
Office.Outlook.Desktop.WatsonBucketsThis rule collects the crash information from the event logs when Outlook crashed in the previous session. The data is actively monitored for anomalous hangs. It is used to detect and identify hangs in order to fix in future updates. The following fields are collected:
Office.PowerPoint.SessionCollecting feature usages on each PowerPoint session. This data is used to calculate the ratio of PowerPoint ungraceful exit while using a feature. The ratio of PowerPoint ungraceful exit is a key signal to guarantee PowerPoint is running as expected. The following fields are collected:
Office.PowerPoint.UAE.DialogCollected every time when PowerPoint ungracefully exited while a dialog open on top of PowerPoint main window. This information is critical to catch PowerPoint ungracefully exits due to an active dialog blocking PowerPoint main window. Microsoft is using this data to diagnose the issue in order to guarantee PowerPoint running as expected. The following fields are collected:
Office.PowerPoint.UAE.DocumentCollecting what feature is being used on a document when PowerPoint ungracefully exited. These features include slide show, document open, save, edit, co-authoring, shutdown. This information is critical to catch PowerPoint ungracefully exits while using a feature. Microsoft is using this data to diagnose the issue in order to guarantee PowerPoint running as expected. The following fields are collected:
Office.PowerPoint.UAE.OpenCollecting every time when PowerPoint ungracefully exit while opening a document. This information is critical to catch PowerPoint ungracefully exits while opening a document. Microsoft is using this data to diagnose the issue in order to guarantee PowerPoint running as expected. The following fields are collected:
Office.PowerPoint.UAE.SessionCollecting what feature has been used when PowerPoint session ungracefully exited. This information is critical to catch PowerPoint ungracefully exits. Microsoft is using this data to diagnose the issue in order to guarantee PowerPoint running as expected. The following fields are collected:
Office.PowerPoint.UAE.ShutdownCollecting PowerPoint ungracefully exit while shutting down. This information is critical to catch PowerPoint ungraceful exits while shutting down. Microsoft uses this data to diagnose the issue in order to guarantee PowerPoint runs as expected. The following fields are collected:
Office.PowerPoint.UAE.SlideShowCollecting PowerPoint ungracefully exit while shutting down. This information is critical to catch PowerPoint ungraceful exits while shutting down. Microsoft uses this data to diagnose the issue in order to guarantee PowerPoint runs as expected. The following fields are collected:
Office.Programmability.Addins.COMAddInCrashEvent generated when a COM Add-in crashes. Used to determine adoption and reliability issues with Office add-ins. The following fields are collected:
Office.Programmability.Telemetry.AddInCrashEvent generated when a COM Add-in is loaded. This information is critical to determine whether an add-in caused an Office application crash. It is used to assess global add-in compatibility with Office applications. The following fields are collected:
Office.Programmability.Telemetry.MacroFileOpenedTriggered upon opening a macro (VBA)-containing file on a device that has been onboarded to Office Apps as a Service (OAAS) by the IT admin and where Microsoft 365 Apps for enterprise has been activated with an enterprise license. The event is used to understand the health of macro(VBA)-containing files in a tenant and is compared to Office.Programmability.Telemetry.VbaTelemetryBreak which tracks errors on VBA-containing files. No fields are collected. Office.System.SystemHealthUngracefulAppExitDesktopCOMAddInThe event is triggered by an abnormal application termination while executing COM Add-in for Office client applications such as Word, Excel, PowerPoint, and Outlook. The data is used to determine reliability of add-ins and issues in Office connected to add-in crashes. The following fields are collected:
Office.System.SystemHealthUngracefulAppExitMacAndiOSOn boot event that captures ungraceful app exits for further investigation. The following fields are collected:
Office.ThisAddIn.StartupFailedCollects information for exception that occur during startup of the Data Streamer App. This data is used to monitor the health of the application. This event is generated by Microsoft Data Streamer for Excel Add-in. The following fields are collected:
OneNote.SafeBootActionThis is triggered during application start if the app crashed in the previous session. This data is used to track the new crashes and will help us identify if the crash detection logic is working properly and to keep track of number of boot crashes and early crashes. The following fields are collected:
OneNote.SafeBootResetCrashCounterOnAppSuspend, Office.OneNote.Android.SafeBootResetCrashCounterOnAppSuspend, Office.Android.EarlyTelemetry.SafeBootResetCrashCounterOnAppSuspendThe critical signal is sent when we are resetting the crash counter on app suspend before safe boot dialog is shown. This marker is required to track and diagnose the health of the app. A safe boot dialog is shown when the app crashes multiple times continuously. It gives the user an option to reset the app. This marker will help figure out if Safe boot dialog was not shown to a user despite hitting trigger criteria. The following fields are collected:
telemetry.errorThis event lets us diagnose and fix issues that are preventing necessary diagnostic data from being generated or sent. These events let us understand if we are missing critical data needed to identify security issues or major issues with how your app is working. The following fields are collected:
watchdog.anrNeeded for monitoring app performance errors to prevent cases where the app stops responding, and your screen becomes frozen in the app (referred to as ANR - application not responding). The following fields are collected:
Application feature performance subtypePoor response time or performance for scenarios such as application startup or opening a file. android.frame.metricsAllows us to detect and fix situations where our Android app components are causing performance issues, for example, if your inbox is not scrolling smoothly. The following fields are collected:
cal.componentThis event lets us detect and fix issues where there is perceivable performance impact on our calendar UI components that would cause your calendar to have scrolling issues. The following fields are collected:
contact.actionThis event is triggered on different actions on contacts - viewing, updating, and deleting contacts as well as viewing the contacts list. It is used to determine if there are any performance regressions that have to do with contacts. The following fields are collected:
conversation.load.timeThis event lets us detect and fix issues where there is perceivable performance impact on loading your email conversations to ensure your emails are loading as expected. The following fields are collected:
conversation.reloadedThis event lets us detect how often we reload the conversation based on service notifications. We need to track if the update notifications are being too loud and need to be trimmed because they are degrading usability. The following fields are collected:
core.data.migrationAllows us to detect and fix situations where there was an error in updating email data on your device to a newer version. The following fields are collected:
core.data.performanceAllows us to detect and fix situations where the email data we're storing on your device is causing performance issues. The following fields are collected:
inbox.componentThis event collects two types of user data: Microsoft 365 subscription status, and whether the user sees ads. This helps us detect and fix issues where there is perceivable performance impact on the user's inbox UI components, which would cause email messages, avatar, read/unread state to not load or display properly. The following fields are collected:
Initial.page.landingThis event helps track the type of experience that users see when they land in our application page. This data is used to determine the traffic of users piped into each experience in our application and also helps us to easily consolidate experimentation results. The following fields are collected:
IpcpBootstrapUserCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when the IpcpBootstrapUser API call is made. The following fields are collected:
IpcpGetKeyCollected when a user attempts to open an Information Rights Managed (IRM) protected document or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when the IpcpGetKey API call is made. The following fields are collected:
json.parse.errorThis event denotes that an error is thrown by the json parser. We will be able to debug the read registry string that was sent to the json parser, to allow a smooth experience for our users. The following fields are collected:
mail.filter.componentThis event lets us detect and fix issues where there is perceivable performance impact on your mail filtering experience, which would cause your filters to not load or display properly. The following fields are collected:
message.rendering.interceptedThis event enables us to track how often the users intercept the rendering process before it is completed. We use this data to detect performance issues. The following fields are collected:
message.rendering.performanceThis event lets us monitor the performance of the message rendering process, so that we can analyze the performance of different rendering processes and detect performance issues. The following fields are collected:
Office.Android.AdsMobile.Wxpu.AdUIEvent[This event was previously named Office.Android.AdsMobile.AdUIEvent.] This is event is triggered when a user interacts with an advertisement. This event collects information that is used to determine the app and feature performance for the users who are exposed to ads. The following fields are collected:
Office.Android.AndroidOfficeLaunchToLandingPageLatencyCritical to capture for app performance metric with respect to the response time of the app from the boot. Microsoft uses this to collect the time taken for the app to be responsive and also detect scenarios that may impact boot time in Word, Excel, or PowerPoint. The following fields are collected:
Office.Android.AuthPerfADALEndToSignInEndThis event is triggered when an enterprise user clicks on the Next button on the password page to sign in completion. This information helps Microsoft determine the time taken in this flow for performance comparison and make performance improvements as required. The following fields are collected:
Office.Android.AuthPerfAuthStartToOneAuthAcquireCredStartThis event is triggered when the prompt flow is initiated, and the credential acquisition flow starts. This information helps Microsoft determine the time taken in this flow for performance comparison and make performance improvements as required. The following fields are collected:
Office.Android.AuthPerfAuthStartToOneAuthSignInInteractiveStartThis event is triggered when the authentication flow is initiated in Office Android apps. This information helps Microsoft determine the time taken in this flow and to measure the time spent in integrated flows so that required performance improvements can be made. The following fields are collected:
Office.Android.AuthPerfFixMeToOneAuthAcquireCredStartThis event is triggered when the prompt flow initiates the credential acquisition flow for an account that is in invalid state and needs fixing by the user. This helps Microsoft determine the time taken in this flow for performance comparison and make performance improvements as required. The following fields are collected:
Office.Android.AuthPerfHRDEndToADALStartThis event is triggered when an enterprise user clicks on the next button in an email page. This information helps Microsoft determine the time taken in this flow for performance comparison and make performance improvements as required. The following fields are collected:
Office.Android.AuthPerfHRDEndToIDCRLStartThis event is triggered when a consumer user clicks on the next button in an email page. This information helps Microsoft determine the time taken in this flow for performance comparison and make performance improvements as required. The following fields are collected:
Office.Android.AuthPerfIDCRLEndToSignInEndThis event is triggered when the consumer user clicks on the Next button on password page to sign in completion. This data helps Microsoft determine the time taken in this flow for performance comparison and make performance improvements as required. The following fields are collected:
Office.Android.AuthPerfOneAuthSignInInteractiveEndToSignInEndThis event is triggered when the sign-in interactive flow ends successfully with the status received by the app. This information helps Microsoft determine the time taken in this flow for performance comparison in Office Android apps and make improvements as needed. The following fields are collected:
Office.Android.AuthPerfSignInStartToHRDStartThis event is triggered when the user clicks on the sign-in button to the email page. This helps Microsoft determine the time taken in this flow for performance comparison and make performance improvements as required. The following fields are collected:
Office.Android.AuthPerfUnifiedSISUEndToADALStartThis event is triggered when an enterprise user clicks on the next button in First Run Experience (FRE) page to open the password page. This information helps Microsoft determine the time taken in this flow for performance comparison and make performance improvements as required. The following fields are collected:
Office.Android.AuthPerfUnifiedSISUEndToIDCRLStartThis event is triggered when the consumer user clicks on the Next button in the First Run Experience (FRE) page to generate the password page. This information helps Microsoft determine the time taken in this flow for performance comparison and make performance improvements as required. The following fields are collected:
Office.Android.AuthPerfUnifiedSISUEndToOneAuthSignInInteractiveStartThis event is triggered when the user clicks on the Next button in the First Run Experience (FRE) page to start the Sign-In Interactive flow. This helps Microsoft determine the time taken in this flow, to determine performance in authentication flows in Office Android apps, and make performance improvements as required. The following fields are collected:
Office.Android.CrashMetadataThis event is triggered when there is a crash, and the crash successfully uploads to crash collection service. This event is used to diagnose Android crashes and also monitor the health of the Android crash upload service. The following fields are collected:
Office.Android.DocsUI.Views.DimePurchaseFlowStateThis health event attempts to capture each state that a user goes through when the user is attempting to make a purchase through the in-app purchase flow hosted by Dime. The data is used to monitor and alert on the health of the purchase flow triggered from Office Mobile app when user opts to buy an Microsoft 365 subscription. The following fields are collected:
Office.Android.EarlyTelemetry.AdErrorEventThis event is triggered for ad related error scenario. This event does not collect any user related data from the online platform. The following fields are collected:
Office.Apple.Apple.AppBoot.MacThis event is collected for Office applications running under Apple platforms. The event is used to collect the time taken to boot the app, as well as some details on the type of boot done. This event helps us monitor our performance and provide performance improvements. The following fields are collected:
Office.Apple.DiskRuleResultSerializerErrorOnStreamOpThis event is collected for Office applications running under Apple platforms. The event is used to monitor the health of our telemetry infrastructure. This event denotes an error has occurred. The following fields are collected:
Office.Apple.MacBootResourceUsageThis event is collected for Office applications running under Apple platforms. This event is collected for Office applications running under Apple platforms. The event is used to collect multiple indicators around the resources being consumed during boot by Office apps. This event helps us monitor our performance and provide performance improvements. The following fields are collected:
Office.Apple.MAU.ValidationThis event is collected for Office applications running under Apple platforms. The event is used to monitor the health of the Microsoft Autoupdate component, which is used to distribute and install application updates. The data collected is used for detecting errors and investigating causes of failures. The following fields are collected:
Office.Apple.MbuInstrument.Hang.Detection.Spin.ControlThis event is collected for Office applications running under Apple platforms. The event is logged whenever an application appears to become non-responsive. This event helps us monitor our performance and provide performance improvements. The following fields are collected:
Office.Apple.MbuInstrument.VMOnDocumentCloseThis event is collected for Office applications running under Apple platforms. The event is used to collect a snapshot of the state of memory during document close. This event helps us monitor our performance and provide performance improvements. The following fields are collected:
Office.Apple.MbuInstrument.VMOnShutdownThis event is collected for Office applications running under Apple platforms. The event is used to collect a snapshot of the state of memory during application shutdown. This event helps us monitor our performance and provide performance improvements. The following fields are collected:
Office.Apple.MbuInstrument.VMOnStartThis event is collected for Office applications running under Apple platforms. The event is used to collect a snapshot of the state of memory during application start. This event helps us monitor our performance and provide performance improvements. The following fields are collected:
Office.Apple.MsoAppDelegate.BootPerfThis event is collected for Office applications running under Apple platforms. The event is used to collect time and memory consumed during boot by Office apps, as well as some details on the type of boot done. This event helps us monitor our performance and provide performance improvements. The following fields are collected:
Office.Apple.UngracefulAppExitHangsInPreviousSessionThis event is collected for Office applications running under Apple platforms. The event is used to monitor the health of our Office applications as well as for investigating causes of failures. We collect the number of times an application appeared to be unresponsive prior to hitting an ungraceful application exit. The following fields are collected:
Office.Apple.WhatsNewErrorAndWarningThis event is collected for Office applications running under Apple platforms. The event is used to monitor the health of the What's New feature. This event denotes that an error/warning occurred while parsing What's New content, pointing to potential content authoring issues. The following fields are collected:
Office.Extensibility.RichApiMethodInvocationWhen customer uses an Office Add-in and calls Rich API for providing service, this event will be triggered. Used to measure the service reliability, performance, and usage for Rich API method invocation. The following fields are collected:
Office.Manageability.Service.ApplyPolicyCritical telemetry to track failure\Success of applying cloud policy settings to registry. LastError tells why and where the Application of policy in registry failed. The following fields are collected:
Office.OfficeMobile.PdfViewer.PdfFileOpenMeasurements (on Android)This event is collected for the Office app for Android. It records when a file open operation takes place. We collect this data to ensure good performance for all file opens on the app. The following fields are collected:
Office.OfficeMobile.PdfViewer.PdfFileOpenMeasurements (on iOS)This event is collected for the Office app for iOS. It records when a file open operation takes place. We collect this data to ensure good performance for all file opens on the app. The following fields are collected:
Office.OneNote.Android.Sync.ProvisioningCompleted[This event was previously named OneNote.Sync.ProvisioningCompleted.] The critical signal used to ensure that after a user signs-into a OneNote Android App, notebooks are properly provisioned so that they can be easily accessed. This is used to ensure critical regression detection for OneNote app and service health The following fields are collected:
Office.OneNote.Android.Sync.ProvisioningErrorThe critical signal used to ensure that after a user signs-into a OneNote Android App, notebooks are properly provisioned so that they can be easily accessed. This is used to ensure critical regression detection for OneNote app and service health. The following fields are collected:
Office.OneNote.Android.Sync.ProvisioningStarted[This event was previously named OneNote.Sync.ProvisioningStarted.] The critical signal used to ensure that after a user signs into a OneNote Android App, notebooks are properly provisioned so that they can be easily accessed. This is used to ensure critical regression detection for OneNote app and service health The following fields are collected:
Office.OneNote.System.BootDialogs.SafeBootDialogPendingThe critical signal used to track when we decide to show user a safe boot dialog on next boot because we have been crashing on boot multiple times continuously. This is used to ensure critical regression detection for OneNote app and service health. If users are seeing the safe boot dialog, then we have a critical boot crash bug and this info will help us know how many users are facing this issue and how many users boot the app again to actually see the safe boot dialog vs how many don’t return. The following fields are collected:
Office.Outlook.Desktop.BootPerfMetricsCollects time taken to boot Outlook. The boot time of Outlook is actively monitored to detect and diagnose regressions. It is also used to diagnose customer escalations and improve boot performance over time. The following fields are collected:
Office.Outlook.Mac.BootPerfCollects time taken to boot Outlook. The boot time of Outlook is actively monitored to detect and diagnose regressions. It is also used to diagnose customer escalations and improve boot performance over time. The following fields are collected:
Office.Outlook.Mac.PerformanceUnresponsiveUsed to identify user impacting issues in Outlook that may manifest as degraded performance. The following fields are collected:
Office.Performance.BootCollected when an Office application is booted. Includes whether the boot was initiated by opening a file or launching via the Start menu, whether this was the first boot of the application, how much memory the application is using, and whether there was any blocking UI shown to the user. Used to measure how fast Office applications boot and how much memory they use when they start, to ensure there is an acceptable user experience. The following fields are collected:
Office.Performance.OPerfMon.HangDetectedCollected when an Office application experiences a hang of the user interface. The collected data is used to assess prevalence, impact, and assist in root cause analysis of hangs experienced by customers so that they can be addressed by the product team. The following fields are collected:
Office.Performance.OPerfMon.ProfileCollected when an Office application experiences unexpectedly poor performance in a critical end user feature, resulting in a poor user experience and/or hang of the user interface. The collected data is used to assess prevalence, impact, and assist in root cause analysis of hangs or poor performance experienced by customers so that they can be addressed by the product team. The following fields are collected:
Office.PowerPoint.PPT.Android.RehearseViewThis event is denoting that user has stopped the rehearsal session. In combination with Office.PowerPoint.PPT.Android.RehearseView.StartSession this will be the first indicator of any crashes or errors that user faces. The following fields are collected:
Office.PowerPoint.PPT.Android.RehearseView.RehearsalSummaryPageEvent triggered when summary page is loaded. This event helps us in capturing the performance of summary page. It tells how much time it takes for rehearsal summary service page to load on client. It is required to keep the feature performant. The following fields are collected:
Office.PowerPoint.PPT.Android.RehearseView.StartSessionEvent triggered when user clicks on start session. This event helps us in capturing how many users are using the feature of Presenter coach on Android. When combined with Office.PowerPoint.PPT.Android.RehearseView it will tell us how many users successfully completed the rehearsal session and how many couldn’t. This is our first indicator of crashes or errors in the feature. The following fields are collected:
Office.PowerPoint.PPT.Shared.RehearseView.Errors[This event was previously named Office.PowerPoint.PPT.Android.RehearseView.Errors] Event triggered when any error occurs. This event will help us know what errors that user has faced and will help keep the Presenter Coach performant on mobile. The following fields are collected:
Office.PowerPoint.Rehearsal.SessionMetricsEvent triggered when the speech session is stopped for Presenter Coach. This event helps us in capturing some metrics for a rehearsal session in Presenter Coach. It will help in maintaining a high quality of service for this feature. The following fields are collected:
Office.UX.OfficeInsider.CanShowOfficeInsiderSlabActivity tracking whether the Office Insider slab can be shown to the user on the Account tab in the Office Backstage UI. The following fields are collected:
Office.UX.OfficeInsider.RegisterCurrentInsiderCritical signal for tracking success or failure of registering users using Office Insider builds who weren't registered as Office Insiders before. Main scenario for this is current Office Insiders who joined Office Insider program before registration of Office Insiders was added. The following fields are collected:
Office.UX.OfficeInsider.ShowOfficeInsiderDlgCritical signal tracking user interaction with Join Office Insider dialog. It is used for identifying any issues in performing user-initiated changes such as joining or leaving Office Insider program and changing Office Insider level. The following fields are collected:
Office.Visio.Shared.VisioFileRenderThis event captures file render time. This event helps us keep file render performance in check. The following fields are collected:
Office.Visio.VisioFileOpenReliabilityThis event collects File open perf data for Visio Dev16. This event is used to monitor performance of File open and associates it with file properties like file size for Visio Dev16. File properties enable us to debug and root cause issues faster. The following fields are collected:
OneNote.App.SafeBootDialogActionTaken, Office.OneNote.Android.SafeBootDialogActionTaken, Office.Android.EarlyTelemetry.SafeBootDialogActionTakenThe critical signal used to track user response when a safe boot dialog is shown. Safe boot dialog is shown when we were unable to launch repeatedly. This is used to ensure critical regression detection for OneNote app and service health. User sees when they encounter critical boot crash bug. This info will help track if the crash cause has been resolved and the user can launch the app successfully. The following fields are collected:
perf.eventUsed for monitoring possible negative impact on performance of loading different parts of the app, for example to ensure when you first open the app, your inbox loads as quickly as possible. The following fields are collected:
performance.recordThis event collects performance metrics of the app. This allows us to detect and fix situations where the app memory usage and CPU usage becomes critically high or has other performance issues, which could cause your device to slow down. The following fields are collected:
wkwebview.terminateThis event is triggered when the user opens a conversation with a number of messages, and they put the app into background process for a while and then activate the app. This event will let us know what number of webview terminated during rendering and composing. The following fields are collected:
Application activity error subtypeErrors in functionality of a feature or user experience. assertionThis event lets us detect when critical app errors occurred that would cause your app to crash or experience serious issues like causing you to see empty rows in your inbox. The following fields are collected:
edit.contact.errorAllows us to detect and fix situations where errors were caused when you're trying to view or edit contacts through our app. The following fields are collected:
error.reportThis event lets us detect when critical app errors occurred so that we can prevent issues that could cause your app to crash or prevent you from reading email. The following fields are collected:
Office.AirSpace.Backend.Win32.GraphicsDriverSoftHangHelps Microsoft separate long video card driver hangs from short ones, which in turn helps make decisions about which video card drivers may be having problems. The user's video card driver has caused Office to hang, but the impact of the hang is not known yet The following fields are collected:
Office.Android.ADALSignInUIPromptsThis event denotes that sign-in prompt came to the user, for school or work account. This event helps in understanding the health of signed in state of our apps and take appropriate actions, when we notice unexpected sign-in re-prompts. The following fields are collected:
Office.Android.AndroidAppDocsFileOperationEndsCritical Docs Android Only (AppDocs) telemetry data for File New/Open/SaveAs end operations. This captures error codes for failures of these AppDocsOperations. Microsoft uses this to identify failures in various file operations and the exact layer at which the failure has occurred in Word, Excel, or PowerPoint. The following fields are collected:
Office.Android.AndroidAuthErrorThis event denotes core authentication failures during silent token refresh, loading sign in page from service and so on. This event helps in understanding the health of signed in state of our apps, sign in attempts that are made, and take appropriate actions, when we notice unexpected failures. The following fields are collected:
Office.Android.AndroidFileAsyncSaveStatusCaptures File async save status data and various error codes from different components. Microsoft uses this data to analyze if there is any user data loss in the app during saving of files in Word, Excel, or PowerPoint. The following fields are collected:
Office.Android.AndroidFileOpenReliabilityThis captures File open status data and various error codes to identify what file open failures are expected versus unexpected and which part of the code is reporting them. Microsoft uses this data to analyze the reasons for file open failures and calculate critical metric like file open success rate in Word, Excel, or PowerPoint. The following fields are collected:
Office.Android.AndroidFileSaveStatusCritical to capture File save status data and various error codes from different components. Microsoft uses this data to analyze if there is any user data loss in the app during saving of files in Word, Excel, or PowerPoint. The following fields are collected:
Office.Android.AndroidOfficeActivationLatencyCritical data to collect end-to-end file open time for all file opens in Windows, Excel, PowerPoint apps. This is used by Microsoft to find out the metric for file open performance of our apps The following fields are collected:
Office.Android.AppDocsFileOperationEndsCritical Docs Android Only (AppDocs) telemetry data for File New/Open/SaveAs end operations. This captures error codes for failures of these AppDocsOperations. Microsoft uses this to identify failures in various file operations and the exact layer at which the failure has occurred in Word, Excel, or PowerPoint. The following fields are collected:
Office.Android.AuthACEErrorsThis event uses the Microsoft Account (MSA) to determine which user is attempting to sign in to the app and during that which telemetry in discussion is getting triggered as part of an unsuccessful attempt. This event helps with MSA sign-in error distribution analysis, which helps in understanding reasons behind unsuccessful MSA sign-in flow end. The following fields are collected:
Office.Android.BCS.ErrorsBinary conversion Errors telemetry for Print and Share as PDF. Microsoft uses this to identify failure points during BCS conversions in Word, Excel, or PowerPoint. The following fields are collected:
Office.Android.ClientSideIAPCritical Error telemetry for Database Failure while file browsing and adds places. Microsoft uses this to identify DB corruption issues in the apps which might hinder user to add places or browse through them from within the app in Word, Excel, or PowerPoint. The following fields are collected:
Office.Android.DBFailureCauseCritical Error telemetry for Database Failure while file browsing and adds places. Microsoft uses this to identify DB corruption issues in the apps which might hinder user to add places or browse through them from within the app in Word, Excel, or PowerPoint. The following fields are collected:
Office.Android.EarlyTelemetry.ExpansionFilesErrorsAndroid Package Kit (APK) expansion files for the Office mobile app are supplementary resource files that Android app developers can publish along with their app. To make our Expansion files download mechanism more reliable, we are logging the cause of errors that occur either in downloading the expansion files or while reading the downloaded expansion files. The following fields are collected:
Office.Android.EarlyTelemetry.ExtractionErrorTo reduce the size of Office Android apps, we apply compression to the resources in the final package. At run time, we first extract these resources before using them. Sometimes there are unexpected errors while performing extractions, which leads to app crashes. Through this event we are collecting some diagnostic information related to extraction, like name of the resource being extracted, path where its extracted etc., free disk space available etc. This data is collected only when there are extraction errors. We use this data to understand the cause of extraction failures, and to improve the user experience of our apps. The following fields are collected:
Office.Android.EarlyTelemetry.RegistryErrorsThis event captures any errors faced during Android registry access. This event data helps us in understanding the user errors and making the registry feature more robust. The following fields are collected:
Office.Android.EarlyTelemetry.SharedLibraryLoadersearchAndloadLibraryErrorWe log this event in case there are errors while loading shared libraries. There can be library loading errors for two reasons 1) Installed Apk is incompatible with the device. 2) The library that we are trying to load may be corrupt, because of errors in extracting it due to low disk space, or low memory. The following fields are collected:
Office.Android.EarlyTelemetry.SharedPrefServiceDataFetchAsyncThis event is triggered when one Office Android app needs data from another Office Android app but fails to get the data. Microsoft uses this data to determine the reason for service failure and to maintain the health of the service. The following fields are collected:
Office.Android.EarlyTelemetry.SharedPrefServiceDataFetchSyncThis event is triggered when an error occurs, for example, timeout or invalid service error, when one Office Android app needs but is unable to get data from other Office Android app installed on the user's device. This data is used to find the reason for the service failure and to maintain the health of the service and office apps. The following fields are collected:
Office.Android.Intune.IntuneJavaCopyFailedAttemptsCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to save local copy of Intune protected Cloud documents. Microsoft uses this data to identify errors during and after Intune enrollment within the app, post signing into the app with a work account The following fields are collected:
Office.Android.Intune.IntuneJavaExceptionADALTokenForMAMCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to obtain the ADAL token for Intune resources. Microsoft uses this data to identify errors during Intune enrollment within the app, post signing into the app with a work account The following fields are collected:
Office.Android.Intune.IntuneJavaExceptionAppPolicyCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to call Intune APIs related to fetching policies for an identity for the current process. Microsoft uses this data to identify errors during and after Intune enrollment within the app, post signing into the app with a work account The following fields are collected:
Office.Android.Intune.IntuneJavaExceptionAppPolicyForContextCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to call Intune APIs related to fetching policies for an identity for the current activity. Microsoft uses this data to identify errors during and after Intune enrollment within the app, post signing into the app with a work account The following fields are collected:
Office.Android.Intune.IntuneJavaExceptionAuthenticationCallbackCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to call Intune APIs related to registering for authentication callbacks for managed accounts. Microsoft uses this data to identify errors during and after Intune enrollment within the app, post signing into the app with a work account The following fields are collected:
Office.Android.Intune.IntuneJavaExceptionGetAccountStateSyncCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to call Intune APIs related to managed account. Microsoft uses this data to identify errors during and after Intune enrollment within the app, post signing into the app with a work account The following fields are collected:
Office.Android.Intune.IntuneJavaExceptionGetIsSaveToLocationAllowedCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to fetch the policy related to save to local. Microsoft uses this data to identify errors during and after Intune enrollment within the app, post signing into the app with a work account The following fields are collected:
Office.Android.Intune.IntuneJavaExceptionGetPolicyForIdentityCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to call Intune APIs related to fetching policies for an identity. Microsoft uses this data to identify errors during and after Intune enrollment within the app, post signing into the app with a work account The following fields are collected:
Office.Android.Intune.IntuneJavaExceptionGetProtectionInfoFromDescriptorCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to call Intune APIs related to Protection Info. Microsoft uses this data to identify errors during and after Intune enrollment within the app, post signing into the app with a work account The following fields are collected:
Office.Android.Intune.IntuneJavaExceptionGetProtectionInfoFromPathCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to call Intune APIs related to Protection Info. Microsoft uses this data to identify errors during and after Intune enrollment within the app, post signing into the app with a work account The following fields are collected:
Office.Android.Intune.IntuneJavaExceptionGetUIPolicyIdentityCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to call Intune APIs related to fetching UI policies for a managed account. Microsoft uses this data to identify errors during and after Intune enrollment within the app, post signing into the app with a work account The following fields are collected:
Office.Android.Intune.IntuneJavaExceptionIsIdentityManagedCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to call Intune APIs related to identifying if an account is managed. Microsoft uses this data to identify errors during and after Intune enrollment within the app, post signing into the app with a work account. The following fields are collected:
Office.Android.Intune.IntuneJavaExceptionNullEnrollmentManagerCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to call Intune APIs related to registration of components for callback. Microsoft uses this data to identify errors during and after Intune enrollment within the app, post signing into the app with a work account The following fields are collected:
Office.Android.Intune.IntuneJavaExceptionProtectCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to call Intune APIs related to protecting a managed document. Microsoft uses this data to identify errors during and after Intune enrollment within the app, post signing into the app with a work account. The following fields are collected:
Office.Android.Intune.IntuneJavaExceptionProtectFromDescriptorIfRequiredCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to call Intune APIs related to protecting a managed document. Microsoft uses this data to identify errors during and after Intune enrollment within the app, post signing into the app with a work account The following fields are collected:
Office.Android.Intune.IntuneJavaExceptionRegisterAccountSyncCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to call Intune APIs related to registering account Intune Management. Microsoft uses this data to identify errors during and after Intune enrollment within the app, post signing into the app with a work account The following fields are collected:
Office.Android.Intune.IntuneJavaExceptionSetUIPolicyIdentitySyncCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to call Intune APIs related to setting policies for a managed account. Microsoft uses this data to identify errors during and after Intune enrollment within the app, post signing into the app with a work account The following fields are collected:
Office.Android.Intune.IntuneJavaExceptionUnregisterAccountSyncCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to call Intune APIs related to remote wipe scenarios for Intune Management. Microsoft uses this data to identify errors during and after Intune enrollment within the app, post signing into the app with a work account The following fields are collected:
Office.Android.Intune.IntuneJavaExceptionUpdateTokenCritical Error telemetry to track failures for individual Intune APIs; This telemetry gets logged in case of errors to call Intune APIs related to update authorization token for a managed account. Microsoft uses this data to identify errors during and after Intune enrollment within the app, post signing into the app with a work account The following fields are collected:
Office.Android.LicenseActivationFailureCritical Error telemetry to track failures to activate licenses for Office 365 accounts in Word, Excel, or PowerPoint. Microsoft uses this to analyze failures to activate a purchased Office 365 license. The following fields are collected:
Office.Android.MSASignInUIPromptsThis event denotes that sign-in prompt came to the user, for personal account. This event helps in understanding the health of signed in state of our apps and take appropriate actions, when we notice unexpected sign-in re-prompts. The following fields are collected:
Office.Apple.Licensing.Mac.DRActivationFailuresThis event is collected for Office applications running under Apple platforms. The event is used for capturing digital river activation failures (the event logs the key and product that was used to activate, and the error code received). This event is used for detecting and helping troubleshoot activation failures (Digital River issues). The following fields are collected:
Office.Apple.Licensing.Mac.GetMachineStatusErrorsThis event is collected for Office applications running under Apple platforms. The event collects the error code returned while periodically checking the validity of a subscription license. The error code can signify server unavailability but also license expiration, machine count limit, invalid hardware ID, etc. This event is used to monitor the health of the Office Licensing Service but also to investigate issues related to subscription machine management. The following fields are collected:
Office.Extensibility.Sandbox.ODPErrorNotificationTracks the various error notifications received from the sandbox. Used to detect the error scenarios in sandbox and there by fixing it, to improve productivity of the user The following fields are collected:
Office.FirstRun.Apple.MacONIOLKFirstRunStartedThis event is collected for Office applications running under Apple platforms. The event lets us know a user has entered first run experience. We use this event to figure out if the First-Run Experience (FRE) was started successfully. The following fields are collected:
Office.Graphics.ARCExceptionsThis exception reporting information is important for assessing the overall health of the graphics stack, as well as identifying parts of the code where failures are occurring at high frequency, in order to prioritize investigation. This exception reporting information is important for assessing the overall health of the graphics stack, and identifying parts of the code where failures are occurring at high frequency. This helps an engineer to determine which rendering failures are impacting the most users, enabling us to prioritize our investigations toward fixing issues that will have the greatest user benefit. The following fields are collected:
Office.OfficeMobile.PersonalizedCampaigning.ErrorsTo raise awareness about the features of Office mobile that users have not yet explored, Office mobile integrates with IRIS to support in-app and push notifications. In case of in-app notifications, it captures errors that happen while pulling or displaying notification and when user interactions with the notification as well as providing feedback to IRIS server. In case of push notifications, it captures errors that happen while displaying notification, and when user interacts with the notification. The following fields are collected:
Office.Outlook.Desktop.Calendar.AcceptCalShareNavigateToSharedFolder.ErrorCollects information when any failure occurs when while Navigation to shared Calendar. This data is used to monitor the health of the calendar sharing API and Outlooks interaction with shared calendars. The following fields are collected:
Office.Outlook.Desktop.EDP.EDPOpenStoreFailureSuccess or failure to open the Enterprise Data Protection protected mail store based on result of Windows API call to get the key to decrypt the store. We use this diagnose one of the top Enterprise Data Protection issues, which can prevent Outlook from booting. Primary cause of failure is Outlooks interaction with Windows APIs used to decrypt the store key. The following fields are collected:
Office.Outlook.Desktop.NdbCorruptionResultOffice.Outlook.Desktop.NdbCorruptionResult and Office.Outlook.Desktop.NDBCorruptStore.Warning are collected when we detect corruption in a user's PST/OST. When we detect corruption, Microsoft collects the format of the database, the place where detected it, and a small amount of context about the corruption. OST/PST corruption prevents users from accessing their emails. We actively monitor this data for anomalous activity. We aim to investigate and diagnose issues to limit loss of customer data. The following fields are collected:
Office.Outlook.Desktop.NDBCorruptStore.WarningOffice.Outlook.Desktop.NdbCorruptionResult and Office.Outlook.Desktop.NDBCorruptStore.Warning are collected when we detect corruption in a user's PST/OST. When we detect corruption, Microsoft collects the format of the database, the place where detected it, and a small amount of context about the corruption. OST/PST corruption prevents users from accessing their emails. We actively monitor this data for anomalous activity. We aim to investigate and diagnose issues to limit loss of customer data. The following fields are collected:
Office.Outlook.Desktop.OutlookCalendarUsageErr.MeetRcpt.ForwardActions.Rule.O16Collects success and failure of the Forward, Forward as Attachment, and Forward as iCalendar action for Single, Recurring, and Exceptional Meeting Responses in the Mail, Calendar, and Inspector Outlook view. The failure rate of the Forward, Forward as Attachment, and Forward as iCalendar actions are actively monitored for anomalies. Anomalous statistics indicate a failure Outlooks ability to conduct core calendar operations. This data is also used to diagnose other Calendar-related issues that may be detected. The following fields are collected:
Office.Outlook.Desktop.OutlookCalendarUsageErr.MeetRcpt.ReplyActions.Rule.O16Collects success and failure of the Reply, Reply All, Reply With IM, and Reply All with IM action for Single, Recurring, and Exception Meeting Responses in the Mail, Calendar, and Inspector Outlook view. The failure rate of the Reply, Reply All, Reply With IM, and Reply All with IM actions are actively monitored for anomalies. Anomalous statistics indicate a failure Outlooks ability to conduct core calendar operations. This data is also used to diagnose other Calendar-related issues that may be detected. The following fields are collected:
Office.Outlook.Desktop.OutlookPrivsDlgSingleUser.LoadFailThis rule collects Calendar Sharing errors when adding a new user (of type EX or SMTP) from the Address book. This data is used to diagnose and resolve issues detected in the Calendar Sharing dialog The following fields are collected:
Office.Outlook.Mac.MacOLKAssertsUsed to identify user impacting issues in Outlook that may manifest as crashes or degraded functionality. The following fields are collected:
Office.Outlook.Mac.MacOLKErrorsUsed to identify user impacting issues in Outlook that may manifest as crashes or degraded functionality. The following fields are collected:
Office.System.SystemHealthAssertsThe errors this event identifies help us understand when the customer experience is degrading. Many of these ShipAsserts lead to crashes and this information makes it possible to fix many of those. Collects ShipAsserts from the product, which helps to identify errors. The following fields are collected:
Office.System.SystemHealthErrorsEtwShimUsed to identify customer impacting issues within the running app that may manifest as crashes or degraded functionality. Records errors that occur during process run time. The following fields are collected:
Office.System.SystemHealthErrorsUlsAndAssertsUsed to identify customer impacting issues within the running app that may manifest as crashes or degraded functionality. Records errors that occur during process run time. The following fields are collected:
Office.System.SystemHealthErrorsUlsWorkaroundUsed to identify customer impacting issues within the running app that may manifest as crashes or degraded functionality. Records errors that occur during process runtime The following fields are collected:
Office.System.SystemHealthErrorsWithoutTagUsed to identify customer impacting issues within the running app that may manifest as crashes or degraded functionality. Records errors that occur during process runtime. The following fields are collected: Count - The count of each error
Office.System.SystemHealthErrorsWithTagUsed to identify customer impacting issues within the running app that may manifest as crashes or degraded functionality. Records errors that occur during process runtime. The following fields are collected:
RenewIdentityFailureCollected when a user attempts to open an IRM protected doc or apply IRM protections. It contains the information needed to be able to properly investigate and diagnose issues that happen when failed to renew user certificates. The following fields are collected:
save.errorAllows us to detect and fix situations where there was an error when you attempted to save a file. It tracks errors caused by failures to save a file, including a descriptive error message to help us resolve the issue. The following fields are collected:
wkwebview.errorThis event lets us detect when web view errors occurred when composing or reading email so that we can prevent issues that could cause your app can’t compose email or read email. The following fields are collected:
Device connectivity and configuration data eventsThe following are the data subtypes in this category:
Device connectivity and configuration subtypeNetwork connection state and device settings, such as memory. application.did.receive.memory.warningThis event is sent when Apple tells us that the application is running out of memory. It tells us that we have introduced an issue with memory management on your device. The following fields are collected:
conversation.memory.leakAllows us to detect situations where our email conversation view is causing us to use up more memory on your device that expected. The following fields are collected:
core.data.corruptionAllows us to detect situations where we cannot show you your email or calendar because where we store your email on your device has become corrupted. The following fields are collected:
core.data.corruption.user.resetAllows us to detect situations where you have deleted or reset your account in our app and it was caused by a corruption in email data we've stored on your device. The following fields are collected:
core.data.diagnosticsAllows us to detect and fix situations where our email storage is using up too much of your device storage space The following fields are collected:
general.properties.logThis event collects information that allows us to categorize and classify issues within the Outlook app that are related to accessibility and device settings. This categorization is necessary to prioritize the impact of issues on customers. The following fields are collected for iOS only:
The following fields are collected for Android only:
low.storage.warningThis is needed to monitor if our app suddenly takes up most of your device storage due to high memory usage by indicating when the device is low on storage The following fields are collected:
Office.AirSpace.AirSpaceLocalBlocklistDriverUpdatedUser has updated a video card driver that was previously causing Office crashes and thus no longer being used to render. Informs Microsoft that users who were once in a suboptimal rendering state are once again in the recommended rendering state. The following fields are collected:
Office.AirSpace.AirSpaceLocalBlocklistInfoDetails on the user's video card driver that has caused multiple recent crashes of Office applications. Office will not use this video card in this Office session (using software rendering instead) until the driver is updated. Informs Microsoft of video card drivers that are causing problems in Office so trends can be identified and the user of impact of such drivers can be analyzed. Tell Microsoft how many users are in this suboptimal state. The following fields are collected:
Office.AirSpace.AirSpaceWinCompIsEnabledWhether the latest Office low-level rendering platform based on Windows Composition is being used. As the latest Office low-level rendering platform is developed and begins to be released to customers, this allows Microsoft to see how many users are on each version to ensure the platform remains bug-free. The following fields are collected:
Office.AirSpace.Backend.Win32.GraphicsDriverHangDetectorBlocklistAppUser's video card has been detected as causing long or unrecoverable hangs. Office will not use this video card in this Office session (using software rendering instead) until the driver is updated. Informs Microsoft of video card drivers that are causing problems in Office so trends can be identified and the user of impact of such drivers can be analyzed. Also helps in informing how many users are in this suboptimal state. The following fields are collected:
Office.AirSpace.Backend.Win32.GraphicsDriverHangDetectorRegistryWriteOffice has identified that the user's video card driver has caused a hang that should be analyzed at the next Office application boot. Used to determine whether using a different video card driver or adapter would offer a better user experience. As patterns occur, Microsoft may make adjustments to keep the Office experience as smooth as possible. The following fields are collected:
Office.AirSpace.Backend.Win32.LocalBlocklistActivityDetails on the user's video card driver that has caused multiple recent crashes of Office applications. Office will not use this video card in this Office session (using software rendering instead) until the driver is updated. Informs Microsoft of video card drivers that are causing problems in Office so trends can be identified and the user of impact of such drivers can be analyzed. Tell Microsoft how many users are in this suboptimal state. The following fields are collected:
Office.AirSpace.Backend.Win32.LocalBlocklistDriverUpdatedActivityUser has updated a video card driver that was previously causing Office crashes and thus no longer being used to render. Informs Microsoft that users who were once in a suboptimal rendering state are once again in the recommended rendering state. The following fields are collected:
Office.Graphics.SpriteMemCorruptReports any errors detected in the sprite memory accounting telemetry. Critical for assessing health of the graphics memory usage telemetry. This information is needed to validate the correctness of our SpriteMem telemetry. The following fields are collected:
Office.PowerPoint.PPT.Shared.NoInternetConnectivityCollected whenever PowerPoint detects there is no internet connectivity. Microsoft uses this data to get diagnostic information about the user's internet connection to be able to understand how that impacts connectivity to Office services. The following fields are collected:
Office.ServiceabilityManager.OfficeSvcMgrProfileThis event is triggered when Office Serviceability Manager starts, and is critical for providing accurate insights related to Deployment Status and Application and Add-in crashes within customer's tenant by allowing us to generate insights for the IT Admin to be able to confidently roll out updates for their enterprise machines. The following fields are collected:
FeedbackSubmit and view feedback for What determines the accuracy and completeness of its data?scrubbing; a process that weeds out and fixes or discards inconsistent, incorrect, or incomplete information. determines the accuracy and completeness of its data.
What are categories of data are called?4 Types of Data: Nominal, Ordinal, Discrete, Continuous.
What is used to ensure that data is organized most efficiently in a database?A database is managed by a database management system (DBMS), a systems software that provides assistance in managing databases shared by many users. A DBMS: 1. Helps organize data for effective access by a variety of users with different access needs and for efficient storage.
What is a collection of related fields called?A record is a collection of related fields. An Employee record may contain a name field(s), address fields, birthdate field and so on. A file is a collection of related records. Tables are also called datasheets. Each table in a database holds data about a different, but related, subject.
|