-You might need to change someone's email address and display name if, for example, they get married and their last name changes.

-1. You'll see a warning that you're about to change the person's sign-in information. Select **Save changes**, then **Close**.

- - Their new username. They'll need it to sign in to Microsoft 365.

-A person's previous primary email address is retained as an additional email address. **We strongly recommend that you don't remove the old email address.**

-This is due to the Microsoft Online Email Routing Address (MOERA). The MOERA is constructed from the person's _userPrincipalName_ attribute in Active Directory and is automatically assigned to the cloud account during the initial sync and once created, it can't be modified or removed in Microsoft 365. You can subsequently change the username in the Active Directory, but it doesn't change the MOERA and you might run into issues displaying the newly changed name in the Global Address List.

-When a user requests a new password, you'll receive a password reset request in email. Follow these steps to reset the password.

-3. Follow the instructions on the **Reset password** page to auto-generate a new password for the user or create one for them, and then select **Reset password**.

-3. Follow the instructions on the **Reset password** page to auto-generate a new password for the user or create one for them, and then select **Reset password**.

-4. Follow the instructions on the **Reset password** page, and select **Reset password**. If you opted for auto-generating the passwords, the new temporary passwords will be displayed.

-When you restore a user account within 30 days after deleting it, the account and all associated data are restored. The user can sign in with the same work or school account. Their mailbox will be fully restored. To find out how much time remains before a specific user account can no longer be restored, [contact us](../../business-video/get-help-support.md).

-After you've restored a user, make sure you notify them that their password changed and you follow up with them.

-A user name conflict occurs when you delete a user account, create a new user account with the same user name (either for the same user or another user with a similar name), and later try to restore the deleted account.

-To fix this, replace the active user account with the one that you are restoring. Or, assign a different user name to the account that you are restoring so that there aren't two accounts with the same user name. Here are the steps.

-A proxy address conflict occurs when you delete a user account that contains a proxy address, assign the same proxy address to another account, and then try to restore the deleted account. Follow the steps below to fix this issue.

-You must have [admin permissions](about-admin-roles.md) in Microsoft 365 to do this.

-3. On the **Restore** page, follow the instructions to set the password and select **Restore**. Any conflicting proxy addresses are automatically removed from the user you are restoring.

-By providing feedback to Microsoft, you agree that you'll uphold this Code of Conduct. You're responsible for all activities and content you post and upload.

-Microsoft reserves the right, at its sole discretion and without any obligation to do so, to review and remove user-created services and content at will and without notice and delete content and accounts. Microsoft reserves the right, at its sole discretion, to permanently ban participants or terminate access to the feedback community. Microsoft further reserves the right to decommission its feedback experiences at any time in the future.

-Microsoft values your feedback, and every day we look at feedback from users across our diverse products and services on all platforms. By providing clear feedback, you can make the greatest impact on the products and features you'd like to see or improve.

-There are many places you can provide feedback to Microsoft. Within an application, you may be able to enter the Help or Feedback menu and find Send feedback button, which will open a form to provide your feedback to Microsoft.

-Depending on the platform and application, you may be able to submit additional logs and screenshots. These are helpful for the product teams at Microsoft to understand your feedback, so please include screenshots and logs when possible.

-If you're using [Feedback](https://feedbackportal.microsoft.com/), you can provide feedback directly within the web portal. Community feedback allows you to browse or vote on feedback from the community. Community feedback is publicly displayed within different forums. Your user name will be displayed by feedback you submit publicly or comments you provide.

-Selecting a forum allows you to see all feedback related to that product, and you can upvote or comment on feedback that matches yours. If you don't see feedback that is similar to your own, you can submit new feedback through the portal itself.

-If you're using Windows Feedback Hub, you can provide feedback from within the Feedback Hub application. For more details on using Feedback Hub, you can [read this article](/windows-insider/feedback). Feedback Hub allows you to also view feedback from other users in the community directly from your Windows device. You may also browse, upvote, or comment on existing feedback, or submit your own using the new feedback form to provide bug reports or feature suggestions.

-If you submitted feedback publicly on the Feedback web portal that you wish to delete, you can remove it by navigating to your My Feedback section. Then, select the feedback item you wish to delete, and select ΓÇ£Delete.ΓÇ¥ You'll be presented with a warning that deleting feedback is irreversible, and that by removing your feedback it will remove all comments, votes, flags, and follows associated with it.

-Once your feedback is sent to Microsoft, it's routed to the relevant product teams who can review it. We look at new feedback that comes in to evaluate if other users have reported similar feedback, and we try to group these similar feedback reports together to surface the most impactful issues and help prioritize future work.

-Through Windows Feedback Hub and the Feedback web portal, Microsoft has the ability to update the status of your feedback and respond to it. We canΓÇÖt promise to respond to every single feedback report, but we do try to evaluate all feedback that comes in to help prioritize product changes.

-You'll see each feedback card on the feedback portal tagged with one of the statuses below. You can find this status tag as shown in the screenshot below.

-Your feedback will move to this status when itΓÇÖs in the process of being addressed and the product team is actively working on it.

-Your feedback will move to this status when we canΓÇÖt take any next steps with it because it was irrelevant to our products or violates our code of conduct. Typically the Microsoft response will clarify why it was closed.

-Your feedback would move to this status when the product team has reviewed your feedback and determined that there's either a workaround to the issue you're facing or your request is already implemented in the product. Typically the Microsoft response will contain more information on what you can do to self-help.

-When the product team has made improvements related to the feedback you provided, your feedback would move to this status. The improvements may address your feedback entirely or partially but the good news is you helped improve the product.

-When the product team has implemented and has released or is releasing a new build with the fix for the issues you reported, your feedback would move to this status. Typically the Microsoft response would contain relevant instructions on how to access updates with the fix(es).

-Moderation of community feedback may be performed by Microsoft employees or approved vendors. Feedback that violates the Feedback Code of Conduct may be hidden from the public view, but Microsoft won't delete this data outside of our data retention policies.

-We understand that when you use Microsoft products and services, youΓÇÖre entrusting us with one of your most valuable assets: your data. We make sure the feedback we receive is stored and handled under Microsoft governance rules, and that it can only be accessed for approved uses. We donΓÇÖt use your email, chat, files, or other personal content to target ads to you. When we collect data, we use it to make your experiences better. Thank you for being a part of our community!

-2. On the **You've selected Microsoft 365 Apps for business** page, enter an email address that you already use. This can be any address you want Microsoft to use to communicate with you during setup. It is also the address where we'll send you information about your bill and renewals. Then select, **Set up account**.

-4. Help us make sure this is you. Enter a number that we can use to reach you and select **Send Verification Code**. You'll receive a text. Enter your code and select **Verify**.

-5. Decide how you'll sign in to Microsoft 365. You can [sign in with your current personal email](#option-1-sign-in-with-your-outlook-hotmail-yahoo-gmail-or-other-email-account) or [create a new account](#option-2-add-a-domain) by adding a domain.

-When signing up for Microsoft 365 Apps for Business, you have 2 options for how to get started. Evaluate three key factors to choose which best meets your needs:

-Learn how to move the files stored in your Microsoft 365 personal account to your Microsoft 365 business account. With both OneDrive accounts synced to your device, you can easily drag and drop the files between two OneDrive folders. For the steps, check out [Migrate your OneDrive files](https://support.microsoft.com/office/7fb28cad-7e25-451f-8b4b-2d1a71e5c0e9).

-Learn how to set up Outlook for the first time or migrate your email, contacts and calendar items. Check out the following topics:

-When you start using Teams with your new work account your data wonΓÇÖt be migrated over. The best way to see your old chats is to open your old Teams account and new work account side by side. You can do this by selecting the ME icon on the top right of Teams and choosing the accountΓÇÖs youΓÇÖd like to open. You can start using Teams with your new work account with your colleagues. Make sure to tell other users you chat with to start contacting you using your new Teams for work account.

-Once you have your new Microsoft Teams account for work set up, you can recreate your meetings in the Teams calendar. Remember to delete the original meetings in your old Teams account. This will allow you to access richer functionality - for example, calendar availability when scheduling, and the ability to record meetings. You can only delete meetings from your own Teams calendar, so make sure you let people who you have meetings with know that youΓÇÖll be recreating your meetings. As you transition to use your new Teams account for your meetings, if people who should be in your meetings are missing, contact them to make sure they havenΓÇÖt joined old meeting link.

-When youΓÇÖre already using Microsoft 365 Business with a Gmail, Outlook, Yahoo (or similar) email address, someone (for example your administrator or business owner) may invite you to upgrade Microsoft 365 to start using professional branded email. In this scenario, youΓÇÖll be switching email address and learning how to upgrade.

-If youΓÇÖre an admin of an organization where users are still using Gmail, Outlook, Yahoo or similar email addresses, and youΓÇÖre looking how to set up branded email, check out these steps instead: [Add a domain to Microsoft 365](../setup/add-domain.md) and [Set up your organization with email and cloud storage](../setup/setup-business-standard.md#finish-setting-up).

-2. Before you can sign in to your new business account, you'll have to set it up with your existing user account. Select **Sign in** to log into your existing user account.

-Follow the steps in the [Migrate data to my Microsoft 365 for business subscription](migrate-data-business-standard.md) to move your OneDrive, Outlook and Teams data.

-Your data will remain in your old account, nothing will be deleted. You will be still able to sign in to your old Gmail, Outlook, Yahoo, or other email account like you did before. You should now move your work files to your new work account. Learn how to do that here: [Migrate data to my Microsoft 365 for business subscription](migrate-data-business-standard.md).

-No it doesnΓÇÖt, you can still login the same way as before.

-When you launch Microsoft Outlook using your new business account, your new mailbox will be automatically set up for you.

-After you have completed the basic setup process for [Microsoft 365 Business Premium](m365-business-premium-setup.md) (or [Microsoft 365 for Campaigns](m365-campaigns-setup.md)), your next step is to set up and configure your security protection. Microsoft 365 Business Premium includes security, compliance, identity, and management capabilities to help protect user accounts, email, files, and devices. Use this guidance to complete the following tasks:

-description: This article provides information for Global or SharePoint admins about enabling SharePoint Multi-Geo in satellite geo locations.

-# Enabling SharePoint Multi-Geo in your satellite geo location

-This article is for Global or SharePoint administrators who created a Multi-Geo satellite location **before** SharePoint Multi-Geo capabilities became generally available on March 27, 2019, and who didn't enable SharePoint Multi-Geo in their satellite geo locations.

-> [!NOTE]

-> If you have added a new geo location **after March 27th, 2019**, you do not need to perform these instructions, as your new geo location will already be enabled for OneDrive and SharePoint Multi-Geo.

-These instructions allow you to enable SharePoint in your satellite location, so your Multi-Geo satellite users can take advantage of both OneDrive and SharePoint Multi-Geo capabilities in O365.

-> [!IMPORTANT]

-> Please note that this is a one way enablement. Once you set SPO mode, you will not be able to revert your tenant to OneDrive only Multi-Geo mode without an escalation with support.

-## To set a geo location into SPO Mode

-To set a geo location into SPO mode, connect to the geo location you want to set in SPO Mode:

-1. Open your SharePoint Online Management Shell and run the following commands:

-2. `Connect-SPOService -URL "https://$tenantGeo-admin.sharepoint.com" -Credential Get-Credential`

-3. `Set-SPOMultiGeoExperience`</br></br>

-

-4. This operation usually takes about an hour while we perform various publish backs in the service and re-stamp your tenant. After at least 1 hour, perform a `Get-SPOMultiGeoExperience`. This shows you whether this geo location is in SPO mode.</br></br>

-

-> [!NOTE]

-> Certain caches in the service update every 24 hours, so it is possible that for a period of up to 24 hours, your satellite geo may intermittently behave as if it was still in ODB mode. This does not cause any technical issues.

-For additional information regarding SharePoint Multi-Geo, refer to [aka.ms/sharepointmultigeo](multi-geo-capabilities-in-onedrive-and-sharepoint-online-in-microsoft-365.md)

-description: "Summary: Use PowerShell for Microsoft 365 to assign per-user communication settings with Skype for Business Online policies."

-# Assign per-user Skype for Business Online policies with PowerShell for Microsoft 365

-*This article applies to both Microsoft 365 Enterprise and Office 365 Enterprise.*

-Using PowerShell for Microsoft 365 is an efficient way to assign per-user communication settings with Skype for Business Online policies.

-

-## Prepare to run the PowerShell commands

-Use these instructions to get set up to run the commands (skip the steps you have already completed):

-

- > [!Note]

- > Skype for Business Online Connector is currently part of the latest Teams PowerShell module. If you're using the latest Teams PowerShell public release, you don't need to install the Skype for Business Online Connector.

-1. Install the [Teams PowerShell module](/microsoftteams/teams-powershell-install).

-

-2. Open a Windows PowerShell command prompt and run the following commands:

-

- ```powershell

- Import-Module MicrosoftTeams

- Connect-MicrosoftTeams

- ```

- When prompted, enter your Skype for Business Online administrator account name and password.

-

-## Updating external communication settings for a user account

-Suppose you want to change external communication settings on a user account. For example, you want to allow Alex to communicate with federated users (EnableFederationAccess is equal to True) but not with Windows Live users (EnablePublicCloudAccess equals False). To do that, you need to do two things:

-

-1. Find an external access policy that meets our criteria.

-

-2. Assign that external access policy to Alex.

-

-How do you determine which external access policy to assign Alex? The following command returns all the external access policies where EnableFederationAccess is set to True and EnablePublicCloudAccess is set to False:

-

-```powershell

-Get-CsExternalAccessPolicy -Include All| Where-Object {$_.EnableFederationAccess -eq $True -and $_.EnablePublicCloudAccess -eq $False}

-```

-Unless you have created any custom instances of ExternalAccessPolicy, that command returns one policy that meets our criteria (FederationOnly). Here's an example:

-

-```powershell

-Identity : Tag:FederationOnly

-Description :

-EnableFederationAccess : True

-EnableXmppAccess : False

-EnablePublicCloudAccess : False

-EnablePublicCloudAudioVideoAccess : False

-EnableOutsideAccess : True

-```

-Now that you know which policy to assign to Alex, we can assign that policy by using the [Grant-CsExternalAccessPolicy](/powershell/module/skype/Get-CsExternalAccessPolicy) cmdlet. Here's an example:

-

-```powershell

-Grant-CsExternalAccessPolicy -Identity "Alex Darrow" -PolicyName "FederationOnly"

-```

-Assigning a policy is simple: you can specify the Identity of the user and the name of the policy to be assigned.

-

-And when it comes to policies and policy assignments, you're not limited to working with user accounts one a time. For example, suppose you need a list of all the users who are allowed to communicate with federated partners and with Windows Live users. We already know that those users have been assigned the external user access policy FederationAndPICDefault. Because we know that, you can display a list of all those users by running one simple command. Here's the command:

-

-```powershell

-Get-CsOnlineUser -Filter {ExternalAccessPolicy -eq "FederationAndPICDefault"} | Select-Object DisplayName

-```

-In other words, show us all the users where the ExternalAccessPolicy property is set to FederationAndPICDefault. (And, in order to limit the amount of information that appears onscreen, use the Select-Object cmdlet to display show us only each user's display name.)

-

-To configure all our user accounts to use that same policy, use this command:

-

-```powershell

-Get-CsOnlineUser | Grant-CsExternalAccessPolicy "FederationAndPICDefault"

-```

-This command uses Get-CsOnlineUser to return a collection of all the users who have been enabled for Lync, then sends all that information to Grant-CsExternalAccessPolicy, which assigns the FederationAndPICDefault policy to each and every user in the collection.

-

-As an additional example, suppose you've previously assigned Alex the FederationAndPICDefault policy, and now you've changed your mind and would like him to be managed by the global external access policy. You can't explicitly assign the global policy to anyone. Instead, the global policy is used for a given user if no per-user policy is assigned to that user. Therefore, if we want Alex to be managed by the global policy, you need to *unassign* any per-user policy previously assigned to him. Here's an example command:

-

-```powershell

-Grant-CsExternalAccessPolicy -Identity "Alex Darrow" -PolicyName $Null

-```

-This command sets the name of the external access policy assigned to Alex to a null value ($Null). Null means "nothing". In other words, no external access policy is assigned to Alex. When no external access policy is assigned to a user, that user then gets managed by the global policy.

-## Managing large numbers of users

-To manage large numbers of users (1000 or more), you need to batch the commands via a script block using the [Invoke-Command](/powershell/module/microsoft.powershell.core/invoke-command) cmdlet. In previous examples, each time a cmdlet is executed, it must set up the call and then wait for the result before sending it back. When using a script block, this allows the cmdlets to be executed remotely, and once completed, send the data back.

-```powershell

-$s = Get-PSSession | Where-Object { ($.ComputerName -like '*.online.lync.com' -or $.Computername -eq 'api.interfaces.records.teams.microsoft.com') -and $.State -eq 'Opened' -and $.Availability -eq 'Available' }

-$users = Get-CsOnlineUser -Filter { ClientPolicy -eq $null } -ResultSize 500

-$batch = 50

-$filter = ''

-$total = $users.Count

-$count = 0

- $users | ForEach-Object {

- $upn = $_.UserPrincipalName

- $filter += "(UserPrincipalName -eq '$upn')"

- $batch--

- $count++

- if (($batch -eq 0) -or ($count -eq $total)) {

- $filterSB=[ScriptBlock]::Create($filter)

- Invoke-Command -Session $s -ScriptBlock {param($f) Get-CsOnlineUser -filter $f | Grant-CsClientPolicy -PolicyName "ClientPolicyNoIMURL" -Passthru | Grant-CsExternalAccessPolicy -PolicyName "FederationAndPICDefault"} -ArgumentList $filterSB

- # Reset

- $batch = 50

- $filter = ''

- } else {

- $filter += " -or "

- }

-}

-```

-This finds 500 users at a time who don't have a client policy. It grants them the client policy "ClientPolicyNoIMURL" and the external access policy "FederationAndPicDefault". The results are batched into groups of 50 and each batch of 50 is then sent to the remote machine.

-

-## See also

-[Manage Skype for Business Online with PowerShell](manage-skype-for-business-online-with-microsoft-365-powershell.md)

-

-[Manage Microsoft 365 with PowerShell](manage-microsoft-365-with-microsoft-365-powershell.md)

-

-[Getting started with PowerShell for Microsoft 365](getting-started-with-microsoft-365-powershell.md)

-|Microsoft Viva Skills | [skills.cloud.microsoft](https://skills.cloud.microsoft)|

-description: How an organization that deploys the latest release uses channels for Windows 10 and Microsoft 365 apps.

-# Example of broad deployment for the latest releases

-This channel configuration example is for an organization that uses rapid deployment of the latest releases to fit these business priorities:

-These goals translate to the IT task of finding the balance between rapid production deployment and early vetting with a representative subset of users and devices to validate functionally before broad deployment.

-Our example organization has 5,000 employees in buildings across the world in Europe, Africa, Asia, and the Americas. Seventy percent of the employees use Microsoft 365 E3 and the rest of the organization uses Microsoft 365 E5.

->[!Note]

->This example is designed to show you how you can use deployment stages and groups, which can work for organizations of many types and sizes.

->

-This organization's IT infrastructure:

-## Deployment and update stages

-Based on rapid deployment goals of the latest release, this example organization uses a two-step deployment process.

-1. **Use a preview or pilot deployment:** Validate and iterate with early adopters, IT staff, users with representative configurations, and training staff.

- The early adopters, IT staff, users with representative configurations can validate functionality with other apps and on devices before the new features roll out to the rest of the organization.

- Change managers have an early peek at the new features before widespread rollout and can plan messaging and rollout.

- Training staff can plan new internal courses or update existing courses for the new features before widespread rollout.

-2. **Production deployment:** Roll out to all remaining users by region, department, or other deployment method.

-## Deployment configuration for Windows 10

-The overall goal is to perform a broad deployment of the latest Semi-Annual Channel release after validation of Release Preview Channel changes by a group of representative users and their devices.

-See [Windows 10 deployment](/windows/deployment/) for more information on Windows 10 deployment methods and strategies.

-| Stage | Channel | Deployment group |

-|:-|:-|:--|

-| Pilot | **Release Preview Channel** <ul><li>Purpose: Deployment of feature updates to IT staff and early adopters for validation on representative devices and configurations (languages, 3rd party apps). </li><li> State: Fully compliant and supported for commercial customers and it doesn't count against your support agreements. </li></ul> | **Win10ReleasePreviewChannel** (example name) <br><br> Members are groups containing: <ul><li> Windows enthusiasts across departments and locations </li><li> Staff with configurations that need validation </li><li> IT admins and IT deployment staff </li><li> Change managers </li><li> Internal training staff </li></ul> |

-| Production | **Semi-Annual Channel** <ul><li>Purpose: Broad deployment of the latest feature updates to the rest of the organization. </li><li> State: Fully compliant and supported. </li></ul> | **Win10SemiAnnualChannel** (example name) <br><br> Members are all users that aren't in the Win10ReleasePreviewChannel group. |

-||||

-This organization uses the best practice of deploying the Release Preview Channel payload in the same way as they deploy Semi-Annual Channel releases, such as Windows Update or Windows Server Update Services, and that they apply the same policies for both channel updates.

-Ongoing updates process:

-1. Release Preview Channel changes are deployed to the Win10ReleasePreviewChannel (example name) deployment group.

-2. Win10ReleasePreviewChannel group members confirm that Release Preview Channel changes are working to IT deployment staff, who can provide feedback to Microsoft and wait for the next Release Preview Channel changes for additional validation.

-3. Semi-Annual Channel feature changes are deployed to the Win10SemiAnnualChannel deployment group.

->[!Note]

->While the Semi-Annual Channel is the recommended channel, your IT department should utilize their management tools and determine when to deploy the latest Semi-Annual Channel release within their organization and then roll it out in waves.

->

-## Deployment configuration for Microsoft 365 Apps

-The overall goal is to perform a broad deployment of the latest Current Channel release after validation of Current Channel (Preview) changes by a group of representative users.

-See [Microsoft 365 Apps deployment](/deployoffice/plan-office-365-proplus) for more information on Microsoft 365 Apps deployment methods and strategies.

-| Stage | Channel | Deployment group |

-|:-|:-|:--|

-| Pilot | **Current Channel (Preview)** <ul><li> Purpose: {give a group of representative users a sneak peek of new Microsoft 365 Apps features} Deployment of feature updates as soon as they're tested with Current Channel (Preview) users and are production-ready. </li><li> State: Fully compliant and supported.</li><li> How often: Updates 2-3 times each month. </li></ul> | **AppsCurrentChannelPreview** (example name) <br><br> Members are groups containing: <ul><li> Office apps enthusiasts across departments and locations </li><li> Staff with configurations that need validation </li><li> IT admins and IT deployment staff </li><li> Change managers </li><li> Internal training staff </li></ul>|

-| Production | **Current Channel** <ul><li> Purpose: Broad deployment of the latest feature updates to the rest of the organization. </li><li> State: Fully compliant and supported. </li></ul> | **AppsCurrentChannel** (example name) <br><br> Members are all users that aren't in the AppsCurrentChannelPreview group. |

-|||

-Ongoing updates process:

-1. Current Channel (Preview) changes are deployed to the AppsCurrentChannelPreview deployment group.

-2. AppsCurrentChannelPreview group members confirm that Current Channel (Preview) changes are working to IT deployment staff, who can provide feedback to Microsoft and wait for the next Current Channel (Preview) release for additional validation.

-3. Current Channel changes are deployed to the AppsCurrentChannel deployment group.

-## Visual summary

-Here are the products, their channels, and the deployment groups used by this example organization.

-

-## See also

-[Deployment and update channel example configurations](deploy-update-channels-examples.md)

-[Microsoft 365 for enterprise overview](microsoft-365-overview.md)

-[Test lab guides](m365-enterprise-test-lab-guides.md)

-Choosing which update channels to use for Windows 10 and Microsoft 365 Apps can depend on your type of organization and where on the development cycle you want to be deploying and using new features and capabilities. Find the prerelease and production channels that best fit your needs.

-|Customer/Channel Offering|Windows 10|Microsoft 365 Apps for Enterprise (Windows 10)|

-|Customer/Channel Offering|Windows 10|Microsoft 365 Apps for Enterprise (Windows 10)|Example|

-|Right for customers who want the latest releases as soon as they're ready.|Semi-Annual Enterprise Channel|[Current Channel](/deployoffice/overview-update-channels#current-channel-overview)|[Latest releases](deploy-update-channels-examples-rapid-deploy.md)|

-[Test lab guides](m365-enterprise-test-lab-guides.md)

-You'll need to [register your generated phone number in this form](https://forms.office.com/pages/responsepage.aspx?id=v4j5cvGGr0GRqy180BHbR0NW3g8C-tRNlyVpwWkCiS1UOEFCVTRHSFMwRk9BVTg3MVdZQlVCNEI4SS4u). This ensures none of your SMS messages will be blocked when sent to US phone numbers.

-> These steps must be completed by the Microsoft 365 global admin in your organization.

-To view the report, you must be a Teams admin, Global reader, Report reader, or Global admin.

-You must be a Global admin to turn on this setting.

-You must be a Microsoft 365 global admin or a Shifts connector admin to complete the steps in this article.

-To learn more, see [Create and assign a custom role in Microsoft Entra ID](/azure/active-directory/roles/custom-create) and [Assign Microsoft Entra roles to users](/azure/active-directory/roles/manage-roles-portal). Keep in mind that it can take up to 24 hours for the role to be created and applied to a user.

-> In order to target only a group of users in your organization to be able to create and view Loop content in workspaces, create a second group that targets All users, set this group to Disabled, and make it a lower priority than your target group that is set to Enabled. This will override the default Not Configured state to Disabled for all users but your target group.