Storage - Block OneDrive for Business Sync From Unmanaged Devices

By Ashwin Venugopal -

 





Summary

Users can sign in to their cloud tenant account via Microsoft OneDrive, and can start syncing selected folders or the entire contents of OneDrive to a local computer. By default, this includes any computer with OneDrive already installed, whether or not it is Azure Domain Joined or Active Directory Domain joined.

Reason

Since the security of unmanaged devices cannot be verified through existing policies, brokers or endpoint protection, they may become risky. If the users are allowed to sync data to these devices, then, this will take that data out of the control of the organization which in turn increases the risk of the data either being intentionally or accidentally leaked.

Note- However, this setting is only applicable to Active Directory domains when operating in a hybrid configuration and not to Azure AD domains. If you have devices which are only Azure AD joined, then, Conditional Access policy can be used instead.

What If?

If this feature is enabled, then, it will prevent the users from using the OneDrive for Business Sync client on devices that are not joined to the domains that were defined.

How to?

To block the sync client on unmanaged devices, use the Microsoft 365 Admin Center:
  1. Navigate to Microsoft 365 administration portal (https://admin.microsoft.com), click on All Admin centers and then Show All, then SharePoint.
  2. Now, click Settings followed by OneDrive - Sync
  3. Check the  Allow syncing only on computers joined to specific domains
  4. Use the Get-ADDomain PowerShell command to obtain the GUID from each domain then add them to the box.
  5. Click Save

To block the sync on unmanaged devices, you can also use SharePoint Online PowerShell:
  1. Connect to SharePoint Online using Connect-SPOService
  2. Now, run the following PowerShell command and provide the DomainGuids from the Get-AADomain command:

Set-SPOTenantSyncClientRestriction -Enable -DomainGuids "786548DD-877B-4760-A749-6B1EFBC1190A; 877564FF-877B-4760-A749-6B1EFBC1190A"

Note: Utilize the -BlockMacSync:$true parameter if conditional access is not being used, to ensure Macs cannot sync.

Monitor:

To verify sync settings on unmanaged devices, use the Microsoft 365 Admin Center:
  1. Navigate to Microsoft 365 administration portal (https://admin.microsoft.com), click on All Admin centers and then Show All, then SharePoint.
  2. Now, click Settings followed by OneDrive - Sync
  3. Verify that  Allow syncing only on computers joined to specific domains is checked
  4. Verify that the Active Directory domain GUIDs are listed in the box.
  • Use the Get-ADDomain PowerShell command to obtain the GUID for each on-premises domain

To verify sync settings on unmanaged devices, you can also use SharePoint Online PowerShell:
  1. Connect to SharePoint Online using Connect-SPOService
  2. Now, run the following PowerShell command:

Get-SPOTenantSyncClientRestriction | fl TenantRestrictionEnabled, AllowedDomainList

      3. Verify TenantRestrictionEnabled is set to True and AllowedDomainList is populated and valid.














































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