| Category | Microsoft Docs article | Related commit history on GitHub | Change details |
|---|---|---|---|
| microsoft-365-copilot-overview | Microsoft 365 Copilot Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/copilot/microsoft-365-copilot-overview.md | |
| microsoft-365-copilot-requirements | Microsoft 365 Copilot Requirements | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/copilot/microsoft-365-copilot-requirements.md | |
| admin | Change A User Name And Email Address | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/add-users/change-a-user-name-and-email-address.md | -description: "Learn how a Microsoft 365 global admin can change a user's email address and display name." +description: "Learn how you can change a user's email address and display name." # Change a user name and email address You might need to change someone's email address and display name if, for exampl ## Before you begin -You must be a [global admin](about-admin-roles.md) to complete these steps. +You must be a [user administrator](/microsoft-365/admin/add-users/about-admin-roles?view=o365-worldwide#commonly-used-microsoft-365-admin-center-roles&preserve-view=true). ## Watch: Change a user's email address, display name or email alias If you found this video helpful, check out the [complete training series for sma ## Change a user's email address -You must be a [global admin](about-admin-roles.md) to complete these steps. +You must be a [user administrator](/microsoft-365/admin/add-users/about-admin-roles?view=o365-worldwide#commonly-used-microsoft-365-admin-center-roles&preserve-view=true). ::: moniker range="o365-worldwide" You must be a [global admin](about-admin-roles.md) to complete these steps. ## Change a user's display name -You must be a [global admin](about-admin-roles.md) to complete these steps. +You must be a [user administrator](/microsoft-365/admin/add-users/about-admin-roles?view=o365-worldwide#commonly-used-microsoft-365-admin-center-roles&preserve-view=true). ::: moniker range="o365-worldwide" For more information on adding an email alias, see [Add another email alias for ## Set the primary email address +You must be an [Exchange administrator](about-exchange-online-admin-role.md). + ::: moniker range="o365-worldwide" 1. In the admin center, go to the **Users** \> <a href="https://go.microsoft.com/fwlink/p/?linkid=834822" target="_blank">Active users</a> page. For more information on adding an email alias, see [Add another email alias for ::: moniker-end -1. Select the user's name, and then on the **Account** tab select **Manage username and email**. +1. Select the user's name, and then on the **Account** tab select **Manage email aliases**. -1. If you're adding a new email address, under **Aliases**, in the blank box, type the first part of the new email address. If you added your own domain to Microsoft 365, choose the domain for the new email alias by using the drop-down list. +1. If you're adding a new email address, under **Aliases**, in the blank box, type the first part of the new email address. If you added your own domain to Microsoft 365, choose the domain for the new email alias by using the drop-down list and select **Add**. 1. Under **Aliases**, select the ellipses (...) next to the desired alias and then select **Change to primary email** for the email address that you want to set as the primary email address for that person. > [!IMPORTANT] > You won't see this option to **Change to primary email** if you purchased Microsoft 365 from GoDaddy or another Partner service that provides a management console. Instead, sign in to the GoDaddy / partner's management console to set the primary alias. >- > Also, you'll only see this option if you're a global admin. If you don't see the option, you don't have permissions to change a user's name and primary email address. + > If you don't see the option, you don't have permissions to change a user's name and primary email address. -1. You see a warning that you're about to change the person's sign-in information. Select **Save changes**, then **Close**. +1. Select **Save changes**, then **Close**. 1. Give the person the following information: If you get the error message " **A parameter cannot be found that matches parame ### "We're sorry, the user couldn't be edited. Review the user information and try again" -If you get the error message " **We're sorry, the user couldn't be edited. Review the user information and try again**." it means you aren't a global admin and you don't have permissions to change the user name. Find the global admin in your business and ask them to make the change. +If you get the error message " **We're sorry, the user couldn't be edited. Review the user information and try again**." it means you aren't a member of the correct admin role and you don't have permissions to change the user name. ### What if the person's offline address book won't sync with the Global Address List? |
| admin | Delete A User | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/add-users/delete-a-user.md | description: "Learn how to delete a Microsoft 365 user account, what to do with ## Before you begin -- You need User management permissions for the business or school to delete user accounts.+- You need to be a [user administrator](/microsoft-365/admin/add-users/about-admin-roles?view=o365-worldwide#commonly-used-microsoft-365-admin-center-roles&preserve-view=true) for the business or school to delete user accounts. - You have 30 days to [restore](restore-user.md) the account before the user's data is permanently deleted. - If you want to keep the user's OneDrive data, move it to a different location. You can even move the data up to 30 days after deleting the account. See [Get access to and back up a former user's data](get-access-to-and-back-up-a-former-user-s-data.md). You don't need to move their SharePoint files; you'll still have access to them. - If you want to keep the user's email, **BEFORE** you delete the account, move the email to a different location. If you've already deleted the account: if it's been less than 30 days you can restore it, then move the email data, then delete the account. See [Get access to and back up a former user's data](remove-former-employee-step-5.md). - If you have an Enterprise subscription like Office 365 Enterprise E3, you can preserve the mailbox data of a deleted user account by turning it into an *inactive mailbox*. To learn more, see [Manage inactive mailboxes in Exchange Online](../../compliance/inactive-mailboxes-in-office-365.md). -## Global admin: Stop paying for their license, and choose what to do with their email and OneDrive content +## Stop paying for their license, and choose what to do with their email and OneDrive content -If you are a global administrator, when you delete a user you can also give another user access to their email, and choose what to do with their OneDrive content. +If you are a [user administrator, SharePoint administrator and an Exchange online administrator](about-admin-roles.md), when you delete a user you can give another user access to their email and choose what to do with their OneDrive content. ### Things to consider |
| admin | Remove Former Employee Step 1 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/add-users/remove-former-employee-step-1.md | -description: "Global administrators can block a former employee from logging in and block their access to Microsoft 365 services." +description: "Block a former employee from logging in and block their access to Microsoft 365 services." # Step 1 - Prevent a former employee from logging in and block access to Microsoft 365 services |
| admin | Remove Former Employee | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/add-users/remove-former-employee.md | A question we often get is, "What should I do to secure data and protect access ## Before you begin -You need to be a global administrator to complete the steps in this solution. - To complete the steps in this series, you use these Microsoft 365 capabilities and features. |Product or component|Capability or feature| |
| admin | Add Another Email Alias For A User | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/email/add-another-email-alias-for-a-user.md | If you want multiple people to manage email sent to a single email address like ## Before you begin -You must be a member of the Global admin role to add email aliases to a user. For more info, see [About admin roles in the Microsoft 365 admin center](../add-users/about-admin-roles.md). +You must be a member of the user administrator role to add email aliases to a user. For more info, see [About admin roles in the Microsoft 365 admin center](../add-users/about-admin-roles.md). ## Add email aliases to a user 1. In the admin center, go to the **Users** \> <a href="https://go.microsoft.com/fwlink/p/?linkid=834822" target="_blank">Active users</a> page. -2. On the **Active Users** page, select the user > **Manage username and email**. You won't see this option if the person doesn't have a license assigned to them. +2. On the **Active Users** page, select the user > **Manage email aliases**. You won't see this option if the person doesn't have a license assigned to them. -3. Add the new name in the **Username** field, select a domain and choose **Add**. +3. Under **Aliases**, add the new name in the **Username** field, select a domain and choose **Add**. > [!TIP] > The email alias must end with a domain from the drop-down list. To add another domain name to the list, see [Add a domain to Microsoft 365](../setup/add-domain.md). |
| admin | Release Options In Office 365 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/manage/release-options-in-office-365.md | Title: "Set up the Standard or Targeted release options" f1.keywords: - CSH--++ Last updated 09/14/2023 audience: Admin |
| admin | Set Password Expiration Policy | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/manage/set-password-expiration-policy.md | Current research strongly indicates that mandated password changes do more harm ## Before you begin -You must be a [global admin](../add-users/about-admin-roles.md) to perform these steps. +You must be a [user administrator](../add-users/about-admin-roles.md) to perform these steps. > [!TIP] > If you need help with the steps in this topic, consider [working with a Microsoft small business specialist](https://go.microsoft.com/fwlink/?linkid=2186871). With Business Assist, you and your employees get around-the-clock access to small business specialists as you grow your business, from onboarding to everyday use. |
| admin | Setup Business Standard | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/admin/setup/setup-business-standard.md | In this article, we'll walk you through the steps of adding an existing domain y ## Before you begin -To add, modify or remove domains you must be a global administrator. For more info, see [About admin roles](../add-users/about-admin-roles.md). +To add, modify or remove domains you must be a [domain name administrator](/entra/identity/role-based-access-control/permissions-reference). > [!IMPORTANT] > The person who signs up for Microsoft 365 for business (usually the business owner) automatically becomes the technical administrator of the organization. You can add other people as admins if you want help managing your Microsoft 365 services. Check out [Assign admin roles](../add-users/assign-admin-roles.md) for more info. |
| enterprise | Configure Exchange Server For Hybrid Modern Authentication | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/configure-exchange-server-for-hybrid-modern-authentication.md | In this section, we provide information and steps that need to be done to succes ### Exchange Server specific prerequisites -Your Exchange servers must fulfill the following requirements before Hybrid Modern Authentication can be configured and enabled. In case you have a hybrid configuration, you must run the latest Cumulative Update (CU) to be in a supported state. You can find the supported Exchange Server versions and build in the [Exchange Server supportability matrix](/exchange/plan-and-deploy/supportability-matrix#supported-versions-and-builds). +Your Exchange servers must fulfill the following requirements before Hybrid Modern Authentication can be configured and enabled. In case you have a hybrid configuration, you must run the latest Cumulative Update (CU) to be in a supported state. You can find the supported Exchange Server versions and build in the [Exchange Server supportability matrix](/exchange/plan-and-deploy/supportability-matrix#supported-versions-and-builds). Hybrid Modern Authentication must be configured uniformly across all Exchange servers within your organization. Partial implementation, where HMA is enabled on only a subset of servers, is not supported. - Make sure that there are no end-of-life Exchange servers in the organization. - Exchange Server 2016 must be running CU8 or later. |
| enterprise | Deploy Identity Solution Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/deploy-identity-solution-overview.md | |
| enterprise | Manage Folders And Rules Feature | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/enterprise/manage-folders-and-rules-feature.md | Title: "Manage Folders and Rules feature in Microsoft 365 Groups" Previously updated : 08/18/2022 Last updated : 09/04/2024 audience: Admin description: In this article, learn how to manage folders and rules feature in M # Manage Folders and Rules feature in Microsoft 365 Groups -Users can organize groups emails effectively by creating folders and setting rules inside groups mailbox. Once the folders are created in groups mailbox, users can move and copy messages to different folders manually as well as using **Rules**. +Users can organize groups emails effectively by creating folders and setting rules inside Microsoft 365 Groups. Once the folders are created in group mailboxes, users can move and copy messages to different folders manually and using **Rules**. -This capability is currently available only in Outlook Web Application. +> [!TIP] +> Currently, this capability is available only in Outlook on the web (formerly known as Outlook Web App or OWA). ## Enable Folders and Rules feature for Microsoft 365 Groups in Outlook -Admin can enable the feature with the help of cmdlet `Set-OrganizationConfig -IsGroupFoldersAndRulesEnabled`. +By default, the Folders and Rules feature is turned off in the organization. Admins can view the current status of the feature, and turn it off or turn it on. +- To view the current status of the Folders and Rules feature in the organization, [connect to Exchange Online PowerShell](/powershell/exchange/connect-to-exchange-online-powershell) and run the following command: - The `IsGroupFoldersAndRulesEnabled` parameter specifies whether Folders and Rules feature is enabled for the tenant. + ```powershell + Get-OrganizationConfig | Format-List IsGroupFoldersAndRulesEnabled + ``` - Possible values: true/false +- To turn on the Folders and Rules feature in the organization, run the following command: - Default Value: false + ```powershell + Set-OrganizationConfig -IsGroupFoldersAndRulesEnabled $true + ``` - Regardless of whether the `IsGroupFoldersAndRulesEnabled` parameter is turned off, the **Inbox** and **Deleted items** folders will still be shown, if there are any deleted items in the group. + - By default, after you turn on the feature, only group owners have permission to create folders, rename folders, and to move and copy messages between folders in group mailboxes. To give group members permission, see the [Enable member permission option](#enable-member-permission-option) section. + - To prevent group owners or group members from moving messages between folders, see the [Block "Move message" capability](#block-move-message-capability) section. -> [!NOTE] -> Once the `IsGroupFoldersAndRulesEnabled` parameter is turned off after creating some folder and rules, - > - > - Existing Folders and Rules will keep getting rendered. - > - > - Existing rules will keep on executing. - > - > - Folder Creation/Updation/Deletion will be blocked. - > - > - Message level actions Copy/Move will be blocked. +- To turn off the Folders and Rules feature in the organization, run the following command: -To enable the **Folders and Rules** feature for Microsoft 365 Groups in Outlook, you can use the following cmdlet: + ```powershell + Set-OrganizationConfig -IsGroupFoldersAndRulesEnabled $false + ``` -```powershell -Set-OrganizationConfig -IsGroupFoldersAndRulesEnabled $true -``` + If you turn off the feature after folders and rules have already been created in a group mailbox, the following actions occur: ++ - Existing folders and rules are still rendered. + - Existing rules continue to run. + - Creating, deleting, or updating folders is blocked. + - Moving or copying messages is blocked. ++> [!TIP] +> Regardless of the value of the _IsGroupFoldersAndRulesEnabled_ parameter, the **Inbox** folder is always shown and the **Deleted Items** folder is also shown if there are any deleted items in the group mailbox. -Once the feature is enabled, by default, only the group owner has permission to create folders, rename folders, and move and copy messages across folders. - ## Enable member permission option -If there's a need for members in the group to create folders and triage messages in groups mailbox, then member permission to edit groups content has to be enabled by the admin at tenant level and group owner at group level respectively. +To allow group members to create folders and triage messages in group mailboxes, you need to enable permissions at the following levels: -By default, this setting is set **off** at tenant level and group level - -Admin can enable the member permission to the tenant using the cmdlet `IsGroupMemberAllowedToEditContent`. +- In the organization (admins). +- In the group (group owners). +By default, permission is turned off at both levels. - The `IsGroupMemberAllowedToEditContent` parameter specifies whether group owner can grant permission to members for Folders and Rules feature content edit. +- To view the current status of permissions in the organization, [connect to Exchange Online PowerShell](/powershell/exchange/connect-to-exchange-online-powershell) and run the following command: - Possible values: True/False + ```powershell + Get-OrganizationConfig | Format-List IsGroupMemberAllowedToEditContent + ``` - Default value: false +- To turn on permission in the organization, run the following command: -To enable the **Enable member permission** option, you can use the following cmdlet: + ```powershell + Set-OrganizationConfig -IsGroupMemberAllowedToEditContent $true + ``` -```powershell -Set-OrganizationConfig -IsGroupMemberAllowedToEditContent $true -``` +After you turn on permission at the organization level, group owners can enable permissions on groups mailboxes they own so group members can do the following actions: -Once this option is enabled, group owners can provide group members with the ability to create folders, rename folders, and copy, move, and delete messages by navigating to the group from Outlook > **Settings** > **Edit Group** > and selecting the option **All members will be able to create, edit, move, copy, and delete mail folders and rules within the group**. Group-level member permission is handled by group owners. +- Create folders. +- Rename folders. +- Move and delete messages. -> [!NOTE] -> Admins can see the current value of the settings using `Get-OrganizationConfig` cmdlet. +Group owners can enable these permissions in their Microsoft 365 Groups using the following steps in Outlook on the web: -## Block ΓÇ£MoveΓÇ¥ message capability +1. While signed in as the group owner, go to <https://outlook.office.com/groups/home>. +1. On the groups page that opens, select the Microsoft 365 Group. +1. On the group details page that opens, select :::image type="icon" source="../media/content-understanding/settings-icon.png" border="false"::: **Settings**. +1. In the **Group settings** flyout that opens, select **Edit group**. +1. In the **Edit group** page that opens, select **All members will be able to create, edit, move, copy and delete mail folders and rules within the group** in the **Permissions** section. -Admins can block the **Move** message option for all Microsoft 365 groups within a tenant using the cmdlet `Set-OrganizationConfig -BlockMoveMessagesForGroupFold`. + :::image type="content" source="../media/folders-and-rules-group-members-enabled.png" alt-text="The All members will be able to create, edit, move, copy and delete mail folders and rules within the group setting selected in the properties of the Microsoft 365 Group in Outlook on the web." lightbox="../media/folders-and-rules-group-members-enabled.png"::: + When you're finished on the **Edit group** page, select **Save**. - The `BlockMoveMessagesForGroupFolders` parameter specifies whether message the **Move** action is disabled. +## Block "Move message" capability - Possible values: True/False +Admins can block the **Move message** option for all group mailboxes in an organization. - Default value: false +> [!TIP] +> Blocking the ability to move messages in group mailboxes is useful in organizations that use both Outlook on the web and Outlook Desktop App, because folders aren't available in group mailboxes in Outlook Desktop App (they get messages from the Inbox folder only). +> +> Blocking the ability to move messages in group mailboxes also prevents creating Inbox rules that move messages in group mailboxes. -To block the **Move message** capability, you can use the following cmdlet: +- To view the current status of **Move message** capability in group mailboxes in the organization, [connect to Exchange Online PowerShell](/powershell/exchange/connect-to-exchange-online-powershell) and run the following command: -```powershell -Set-OrganizationConfig -BlockMoveMessagesForGroupFolders $true -``` + ```powershell + Get-OrganizationConfig | Format-List BlockMoveMessagesForGroupFolders + ``` -> [!NOTE] -> Creation of the **Move** rule is also disabled when `BlockMoveMessagesForGroupFolders` is enabled. +- To block **Move message** capability in group mailboxes in the organization, run the following command: -> [!NOTE] -> This is useful if there are mixed set of users using Outlook on Web and Outlook Desktop App. For users on Outlook Desktop App where folders are not available, they can get the messages from group inbox. - - - + ```powershell + Set-OrganizationConfig -BlockMoveMessagesForGroupFolders $true + ``` |
| frontline | Flw Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/flw-overview.md | |
| frontline | Teams For Financial Services | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/teams-for-financial-services.md | Title: Microsoft 365 for Financial Services description: Learn about the admin resources available to manage and get the most out of Teams for your frontline financial services workforce.-+ |
| frontline | Teams For Manufacturing | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/teams-for-manufacturing.md | Title: Microsoft 365 for Manufacturing description: Learn about the admin resources available to manage and get the most out of Teams for your frontline manufacturing workforce.-+ |
| frontline | Teams For Retail Landing Page | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/teams-for-retail-landing-page.md | Title: Microsoft 365 for retail organizations description: Learn about the admin resources available to manage and get the most out of Teams for your retail stores and workforce.-+ |
| frontline | Teams In Hc | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/frontline/teams-in-hc.md | |
| includes | Office 365 U.S. Government Dod Endpoints | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/includes/office-365-u.s.-government-dod-endpoints.md | <!--THIS FILE IS AUTOMATICALLY GENERATED. MANUAL CHANGES WILL BE OVERWRITTEN.--> <!--Please contact the Office 365 Endpoints team with any questions.--> -<!--USGovDoD endpoints version 2024073100--> -<!--File generated 2024-08-06 11:00:08.8334--> +<!--USGovDoD endpoints version 2024090200--> +<!--File generated 2024-09-04 08:00:06.5518--> ## Exchange Online ID | Category | ER | Addresses | Ports 18 | Default<BR>Required | No | `cdn.odc.officeapps.live.com, mrodevicemgr.officeapps.live.com, odc.officeapps.live.com, officeclient.microsoft.com` | **TCP:** 443, 80 24 | Default<BR>Required | No | `lpcres.delve.office.com` | **TCP:** 443 25 | Default<BR>Required | No | `*.cdn.office.net` | **TCP:** 443-26 | Allow<BR>Required | Yes | `*.compliance.apps.mil, *.security.apps.mil, compliance.apps.mil, scc.protection.apps.mil, security.apps.mil`<BR>`23.103.204.0/22, 52.127.72.0/21` | **TCP:** 443, 80 +26 | Allow<BR>Required | Yes | `*.compliance.apps.mil, *.security.apps.mil, compliance.apps.mil, purview.apps.mil, scc.protection.apps.mil, security.apps.mil`<BR>`23.103.204.0/22, 52.127.72.0/21` | **TCP:** 443, 80 28 | Default<BR>Required | No | `activity.windows.com, dod.activity.windows.us` | **TCP:** 443 29 | Default<BR>Required | No | `dod-mtis.cortana.ai` | **TCP:** 443 30 | Default<BR>Required | No | `*.aadrm.us, *.informationprotection.azure.us` | **TCP:** 443 |
| includes | Office 365 U.S. Government Gcc High Endpoints | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/includes/office-365-u.s.-government-gcc-high-endpoints.md | <!--THIS FILE IS AUTOMATICALLY GENERATED. MANUAL CHANGES WILL BE OVERWRITTEN.--> <!--Please contact the Office 365 Endpoints team with any questions.--> -<!--USGovGCCHigh endpoints version 2024073100--> -<!--File generated 2024-08-06 11:00:01.6373--> +<!--USGovGCCHigh endpoints version 2024090200--> +<!--File generated 2024-09-04 08:00:03.1410--> ## Exchange Online ID | Category | ER | Addresses | Ports 23 | Default<BR>Required | No | `*.office365.us` | **TCP:** 443, 80 24 | Default<BR>Required | No | `lpcres.delve.office.com` | **TCP:** 443 25 | Default<BR>Required | No | `*.cdn.office.net` | **TCP:** 443-26 | Allow<BR>Required | Yes | `*.compliance.microsoft.us, *.security.microsoft.us, compliance.microsoft.us, scc.office365.us, security.microsoft.us`<BR>`52.127.240.0/20, 52.227.182.149/32, 52.244.65.13/32, 195.134.252.0/24, 2001:489a:2209::/49` | **TCP:** 443, 80 +26 | Allow<BR>Required | Yes | `*.compliance.microsoft.us, *.security.microsoft.us, compliance.microsoft.us, purview.microsoft.us, scc.office365.us, security.microsoft.us`<BR>`20.158.112.0/21, 52.127.240.0/20, 2001:489a:2209::/49` | **TCP:** 443, 80 28 | Default<BR>Required | No | `activity.windows.com, gcc-high.activity.windows.us` | **TCP:** 443 29 | Default<BR>Required | No | `gcch-mtis.cortana.ai` | **TCP:** 443 30 | Default<BR>Required | No | `*.aadrm.us, *.informationprotection.azure.us` | **TCP:** 443 |
| includes | Office 365 Worldwide Endpoints | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/includes/office-365-worldwide-endpoints.md | <!--THIS FILE IS AUTOMATICALLY GENERATED. MANUAL CHANGES WILL BE OVERWRITTEN.--> <!--Please contact the Office 365 Endpoints team with any questions.--> -<!--Worldwide endpoints version 2024073100--> -<!--File generated 2024-08-06 11:00:07.2575--> +<!--Worldwide endpoints version 2024090200--> +<!--File generated 2024-09-04 08:00:04.7933--> ## Exchange Online ID | Category | ER | Addresses | Ports 53 | Default<BR>Required | No | `ajax.aspnetcdn.com, apis.live.net, officeapps.live.com, www.onedrive.com` | **TCP:** 443 56 | Allow<BR>Required | Yes | `*.auth.microsoft.com, *.msftidentity.com, *.msidentity.com, account.activedirectory.windowsazure.com, accounts.accesscontrol.windows.net, adminwebservice.microsoftonline.com, api.passwordreset.microsoftonline.com, autologon.microsoftazuread-sso.com, becws.microsoftonline.com, ccs.login.microsoftonline.com, clientconfig.microsoftonline-p.net, companymanager.microsoftonline.com, device.login.microsoftonline.com, graph.microsoft.com, graph.windows.net, login-us.microsoftonline.com, login.microsoft.com, login.microsoftonline-p.com, login.microsoftonline.com, login.windows.net, logincert.microsoftonline.com, loginex.microsoftonline.com, nexus.microsoftonline-p.com, passwordreset.microsoftonline.com, provisioningapi.microsoftonline.com`<BR>`20.20.32.0/19, 20.190.128.0/18, 20.231.128.0/19, 40.126.0.0/18, 2603:1006:2000::/48, 2603:1007:200::/48, 2603:1016:1400::/48, 2603:1017::/48, 2603:1026:3000::/48, 2603:1027:1::/48, 2603:1036:3000::/48, 2603:1037:1::/48, 2603:1046:2000::/48, 2603:1047:1::/48, 2603:1056:2000::/48, 2603:1057:2::/48` | **TCP:** 443, 80 59 | Default<BR>Required | No | `*.hip.live.com, *.microsoftonline-p.com, *.microsoftonline.com, *.msauth.net, *.msauthimages.net, *.msecnd.net, *.msftauth.net, *.msftauthimages.net, *.phonefactor.net, enterpriseregistration.windows.net, policykeyservice.dc.ad.msft.net` | **TCP:** 443, 80-64 | Allow<BR>Required | Yes | `*.compliance.microsoft.com, *.protection.office.com, *.security.microsoft.com, compliance.microsoft.com, defender.microsoft.com, protection.office.com, security.microsoft.com`<BR>`13.107.6.192/32, 13.107.9.192/32, 52.108.0.0/14, 2620:1ec:4::192/128, 2620:1ec:a92::192/128` | **TCP:** 443 +64 | Allow<BR>Required | Yes | `*.compliance.microsoft.com, *.protection.office.com, *.security.microsoft.com, compliance.microsoft.com, defender.microsoft.com, protection.office.com, purview.microsoft.com, security.microsoft.com`<BR>`13.107.6.192/32, 13.107.9.192/32, 2620:1ec:4::192/128, 2620:1ec:a92::192/128` | **TCP:** 443 66 | Default<BR>Required | No | `*.portal.cloudappsecurity.com` | **TCP:** 443-67 | Default<BR>Optional<BR>**Notes:** Security and Compliance Center eDiscovery export | No | `*.blob.core.windows.net` | **TCP:** 443 68 | Default<BR>Optional<BR>**Notes:** Portal and shared: 3rd party office integration. (including CDNs) | No | `firstpartyapps.oaspapps.com, prod.firstpartyapps.oaspapps.com.akadns.net, telemetryservice.firstpartyapps.oaspapps.com, wus-firstpartyapps.oaspapps.com` | **TCP:** 443 69 | Default<BR>Required | No | `*.aria.microsoft.com, *.events.data.microsoft.com` | **TCP:** 443 70 | Default<BR>Required | No | `*.o365weve.com, amp.azure.net, appsforoffice.microsoft.com, assets.onestore.ms, auth.gfx.ms, c1.microsoft.com, dgps.support.microsoft.com, docs.microsoft.com, msdn.microsoft.com, platform.linkedin.com, prod.msocdn.com, shellprod.msocdn.com, support.microsoft.com, technet.microsoft.com` | **TCP:** 443 |
| solutions | Data Privacy Protection Assess | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/data-privacy-protection-assess.md | f1.keywords: Last updated 01/03/2024 audience: ITPro-+ ms.localizationpriority: medium |
| solutions | Data Privacy Protection Protect Govern | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/data-privacy-protection-protect-govern.md | f1.keywords: Last updated 01/03/2024 audience: ITPro-+ ms.localizationpriority: medium |
| solutions | Data Privacy Protection Regulations | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/data-privacy-protection-regulations.md | f1.keywords: Last updated 01/03/2024 audience: ITPro-+ ms.localizationpriority: medium |
| solutions | Data Privacy Protection Respond Requests | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/data-privacy-protection-respond-requests.md | f1.keywords: Last updated 01/03/2024 audience: ITPro-+ ms.localizationpriority: medium |
| solutions | Data Privacy Protection | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/data-privacy-protection.md | f1.keywords: Last updated 01/03/2024 audience: ITPro-+ ms.localizationpriority: medium |
| solutions | Deploy Voice | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/deploy-voice.md | |
| solutions | Tenant Management Overview | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/solutions/tenant-management-overview.md | |
| syntex | Solution Manage Contracts In Microsoft 365 | https://github.com/MicrosoftDocs/microsoft-365-docs/commits/public/microsoft-365/syntex/solution-manage-contracts-in-microsoft-365.md | This contract management solution guidance includes four components of Microsoft  -1. Documents are uploaded to a SharePoint document library. A Syntex unstructured document processing model has been applied to the document library. It checks each file to see if any match a "contract" content type it's trained to look for. If it finds a match, it classifies the file as a "contract" and updates the content type for the document. +1. Documents are uploaded to a SharePoint document library. A Microsoft Syntex unstructured document processing model has been applied to the document library. It checks each file to see if any match a "contract" content type it's trained to look for. If it finds a match, it classifies the file as a "contract" and updates the content type for the document. 2. The model also pulls out specific data from each contract file that stakeholders are interested in seeing, such as the *Client*, *Contractor*, and *Fee amount*. This solution relies on the following functionality, all available as part of a - Microsoft Teams - Power Automate -### Learn how to use Syntex +### Learn how to use Microsoft Syntex -New to Microsoft Syntex? Learn how to use Syntex to manage content using AI. +New to Microsoft Syntex? Learn how to use Microsoft Syntex to manage content using AI. The [Introduction to Microsoft Syntex](/training/modules/syntex-intro) learning path teaches how you can use unstructured, freeform, and unstructured document processing models to classify documents, extract text, and label your documents for quick and easy knowledge management. |