User Accounts & Roles (part 3)

By Ashwin Venugopal -

 






To read part 1, please click here
To read part 2, please click here







Administrator Roles

An administrator's main role is to assign specific administrative functions to users and provide permissions to the people in your organization to perform specific tasks in the Microsoft 365 admin center. Roles like Compliance Administrator and Company Administrator can be managed with the help of either Office 365 Security & Compliance admin center or Windows PowerShell. 

Although all the admin roles aren't mutually exclusive, but they can be combined by assigning one or more admin role to a user like the Exchange admin, SharePoint admin, and User Management administrator roles.

Assign Admin Roles within Microsoft 365

To achieve this task, you have to login with the help of a Global admin account and perform following steps:
  1. Select Users and then Active Users in the Admin center.
  2. Now choose the user whose role you want to change on the Active users page after which the properties page for the user will open.
  3. Next to Roles, select Manage Roles.
  4. On the Manage roles page, you can either choose User (no administrator access) or Admin center access.
  5. The Admin center access will help you to choose a particular type of admin role you want to assign for the selected user.
  6. After successfully assigning the roles, you can select Save changes.

Groups

Office 365 groups is a foundational membership service to drive all teamwork across Microsoft 365 and helps you to permit a group of people access to a collection of collaboration resources for those people to share. Those resources includes:
  1. A Shared Outlook inbox 
  2. A Shared calendar
  3. A SharePoint document library
  4. A Planner
  5. Power BI
  6. Yammer (if the group was created from Yammer)
  7. A Team (if the group was created from Teams)
  8. Roadmap (if you have Projects for the web)
Assigning permissions to each of these resources is not mandatory with Office 365 group, as adding people to the group automatically grant them the required permissions to the tools offered by the group.

Groups have the following roles:
  • Owners- Group owners can easily add or remove members and have unique permissions such as the ability to delete conversations from the shared inbox or change different settings about the group. They can also rename the group, update the description or picture, and whatnot. 

  • Members- Although they can access everything in group, but they can't change group settings. By default, they invite guests to join your group, but you can control that setting too.

  • Guests- As the name suggests, they are the members from outside your organization.  

Hence, as per the understanding, only global admins, user admins, and groups admins can create as well as manage groups in Microsoft 365 admin center and you can't be a delegated admin like a consultant who can be an admin on behalf of the original one. 













To read part 1, please click here
To read part 2, please click here






















Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning...
Read more