{"id":8889,"date":"2024-11-09T09:02:51","date_gmt":"2024-11-09T00:02:51","guid":{"rendered":"https:\/\/m365jp.net\/?p=8889"},"modified":"2024-11-09T09:07:18","modified_gmt":"2024-11-09T00:07:18","slug":"mc909164-updated-microsoft-exchange-online-new-fields-for-exchange-mailbox-schema","status":"publish","type":"post","link":"https:\/\/m365jp.net\/index.php\/2024-11-09-mc909164-updated-microsoft-exchange-online-new-fields-for-exchange-mailbox-schema","title":{"rendered":"MC909164 | (Updated) Microsoft Exchange Online: New fields for Exchange mailbox schema"},"content":{"rendered":"
\n
\n
\n\n\n\n
MC909164 | (Updated) Microsoft Exchange Online: New fields for Exchange mailbox schema<\/th>\n<\/tr>\n<\/tbody>\n<\/table>\n
\n\n\n\n\n\n\n\n\n
Classification<\/th>\nplanForChange<\/td>\n<\/tr>\n
Last Updated<\/th>\n11\/08\/2024 23:27:39<\/td>\n<\/tr>\n
Start Time<\/th>\n10\/11\/2024 22:54:19<\/td>\n<\/tr>\n
End Time<\/th>\n01\/31\/2025 08:00:00<\/td>\n<\/tr>\n
Message Content<\/th>\n\n

Updated November 8, 2024: We have updated the rollout timeline below. Thank you for your patience. <\/p>\n

<\/p>\n

Coming soon to Microsoft Exchange Online: A significant rollout that introduces two new subfields under AppAccessContext<\/code> for improved field consistency and enhanced telemetry in other Exchange APIs: <\/p>\n

    \n
  • ClientAppId<\/code> <\/li>\n
  • APIId<\/code> <\/li>\n<\/ul>\n

    [When this will happen:] <\/p>\n

    General Availability (Worldwide): We will begin rolling out early November 2024 (previously late October) and expect to complete by mid-November 2024. <\/p>\n

    General Availability (GCC, GCC High): We will begin rolling out late November 2024 and expect to complete by late November 2024. <\/p>\n

    General Availability (DoD): We will begin rolling out early December 2024 and expect to complete by early December 2024. <\/p>\n

    [How this will affect your organization:] <\/p>\n

    Before this rollout: The ClientAppId<\/code> and AppAccessContext<\/code> fields exist across previous schemas outside of the Microsoft Exchange Web Service (EWS) schema. <\/p>\n

    After this rollout: The AppAccessContext<\/code> field, which serves a similar purpose to the ClientAppId<\/code> field, will be in EWS schema with two new subfields: ClientAppId<\/code> and APIId<\/code>. This update is on by default. The ClientAppId<\/code> field and the ClientAppId<\/code> subfield under the AppAccessContext<\/code> field will both be populated more consistently and robustly with a new fallback. <\/p>\n

    Field definitions
    <\/i><\/p>\n

      \n
    • AppAccessContext<\/code>: Used to provide additional information about the application context in which an event or action occurs. This field helps in tracking and auditing purposes by identifying the specific application or service involved in each operation.
      \n
        \n
      • ClientAppId<\/code>: The original field used to identify the application that initiated a particular action or event. After this rollout, this subfield will have a new fallback to enhance capabilities. <\/li>\n
      • APIId<\/code>: Used to uniquely identify an API endpoint or service. This subfield is particularly useful in scenarios where admins need to filter or track activities specific to certain APIs, such as the Microsoft Exchange Web Service (EWS). <\/li>\n<\/ul>\n<\/li>\n<\/ul>\n

        [What you need to do to prepare:] <\/p>\n

        This rollout will happen automatically by the specified date with no admin action required before the rollout. <\/p>\n

        After the rollout, we recommend admins review and update your workflows to accommodate both the ClientAppId<\/code>and AppAccessContext<\/code> fields. This will ensure that your operations continue seamlessly and leverage the new features effectively. <\/p>\n

        Accessing and using the new fields
        <\/i><\/p>\n

          \n
        1. Navigate to the admin center:<\/i> Start by logging into the Microsoft 365 admin center. <\/li>\n
        2. Access the audit logs:<\/i> Go to the section where audit logs are managed. This is typically found under the Security & Compliance<\/i> section or the Microsoft Purview<\/i> section. <\/li>\n
        3. Search for relevant logs:<\/i> Use the search to filter logs that include the AppAccessContext<\/code> and ClientAppId<\/code> fields. You may need to specify the event types or actions that involve these fields. <\/li>\n
        4. View and analyze logs:<\/i> After the logs are filtered, you can view the details, which will include the AppAccessContext<\/code> and ClientAppId<\/code> fields. These fields provide additional information about the application context and the client application involved in each operation. <\/li>\n<\/ol>\n

          Learn more<\/i> <\/p>\n

Machine Translation<\/th>\n\n

2024\u5e7411\u67088\u65e5\u66f4\u65b0:\u4ee5\u4e0b\u306e\u30ed\u30fc\u30eb\u30a2\u30a6\u30c8\u30bf\u30a4\u30e0\u30e9\u30a4\u30f3\u3092\u66f4\u65b0\u3057\u307e\u3057\u305f\u3002\u3054\u7406\u89e3\u3044\u305f\u3060\u304d\u3042\u308a\u304c\u3068\u3046\u3054\u3056\u3044\u307e\u3059\u3002<\/p>\n

<\/p>\n

Microsoft Exchange Online \u3078\u306e\u8fd1\u65e5\u516c\u958b\u4e88\u5b9a: \u4ed6\u306e Exchange API \u306e\u30d5\u30a3\u30fc\u30eb\u30c9\u306e\u4e00\u8cab\u6027\u3068\u30c6\u30ec\u30e1\u30c8\u30ea\u3092\u5f37\u5316\u3059\u308b\u305f\u3081\u306b\u3001 AppAccessContext<\/code> \u306e\u4e0b\u306b 2 \u3064\u306e\u65b0\u3057\u3044\u30b5\u30d6\u30d5\u30a3\u30fc\u30eb\u30c9\u3092\u5c0e\u5165\u3059\u308b\u5927\u5e45\u306a\u30ed\u30fc\u30eb\u30a2\u30a6\u30c8\u3002<\/p>\n