What steps would you take to set up a new user in Office 365 (Microsoft 365)?

What steps would you take to set up a new user in Office 365 (Microsoft 365)?

• A. Create the user in the admin center, assign appropriate licenses, add to security groups, configure mailbox and distribution lists, enable MFA, set password and password policy, and set admin roles if needed.
• B. Create the user but do not assign any licenses to ensure cost control.
• C. Create a local user on a PC and mimic cloud settings.
• D. Share a generic account to avoid individual credentials.

Answer: (A)

Setting up a new user in Microsoft 365 starts with provisioning the identity in the admin center so the tenant recognizes them as an account. From there, you assign licenses so the user can actually access cloud services like Exchange Online for email, Teams, SharePoint, and OneDrive. Without a license, the account may exist but nothing is accessible, which wastes onboarding time and creates confusion. Adding the user to the appropriate security groups helps apply the right permissions consistently and makes ongoing access management simpler. Configuring the mailbox and distribution lists ensures the user can receive and send email and participate in relevant group communications from the start. Enabling Multi-Factor Authentication adds an essential security layer beyond a password, reducing the risk of account compromise. Setting a strong initial password and enforcing a password policy that requires a change at first sign-in helps prevent weak or reused credentials from being used right away. Finally, assigning admin roles only when needed follows the least-privilege principle, limiting potential impact and helping maintain control over the environment. Skipping licensing, attempting to use a local PC account, or sharing a generic account would undermine access to cloud services, security, and accountability, respectively.

Setting up a new user in Microsoft 365 starts with provisioning the identity in the admin center so the tenant recognizes them as an account. From there, you assign licenses so the user can actually access cloud services like Exchange Online for email, Teams, SharePoint, and OneDrive. Without a license, the account may exist but nothing is accessible, which wastes onboarding time and creates confusion.

Adding the user to the appropriate security groups helps apply the right permissions consistently and makes ongoing access management simpler. Configuring the mailbox and distribution lists ensures the user can receive and send email and participate in relevant group communications from the start.

Enabling Multi-Factor Authentication adds an essential security layer beyond a password, reducing the risk of account compromise. Setting a strong initial password and enforcing a password policy that requires a change at first sign-in helps prevent weak or reused credentials from being used right away.

Finally, assigning admin roles only when needed follows the least-privilege principle, limiting potential impact and helping maintain control over the environment.

Skipping licensing, attempting to use a local PC account, or sharing a generic account would undermine access to cloud services, security, and accountability, respectively.