How to block users from adding Microsoft accounts to Windows 10

On the new Windows 10 operating system, managing users is now simple and it also gives you more options so you can control the user's Microsoft account. You can use more than one Microsoft account on a Windows 10 device.

It's fine if you're using a personal computer, but if you do use it, you will sometimes see another Microsoft account logged into your Windows 10 operating system. It is also no problem but you have to log out and log in to your account to use. If you want to manage the use of Microsoft account, you can follow the instructions in the article below.

Instructions to block users from adding Microsoft accounts to Windows 10

Step 1: First click on Start , then scroll down and select Windows Administrator Tools , select Local Security Policy.

How to block users from adding Microsoft accounts to Windows 10

Step 2: In the Local Security Policy table, select Local Policies> Security Options , in the Policy pane on the right, double-click Account: Block Microsoft Accounts.

How to block users from adding Microsoft accounts to Windows 10

Step 3: In the Accounts selection box : Block Microsoft accounts Properties . You will have two options:

  • Users can not add Microsoft accounts: Users can not add Microsoft account
  • User can'ts add or log on with Microsoft accounts: Users cannot add or login with Microsoft accounts.

Details of these two options are below.

How to block users from adding Microsoft accounts to Windows 10

1. Block User to add Microsoft Windows 10 account

This is the Users can't add Microsoft accounts option in the Accounts table : Block Microsoft accounts Properties when you select this option, you will have the following features.

  • Prevent User from adding new Microsoft account on the computer when using the old Microsoft account.
  • User cannot transfer Local Account (local account) to Microsoft account.
  • The user will not be able to connect an account currently in use in the organization to a Microsoft account.

2. Block User from adding or logging in to Microsoft Windows 10 account

Corresponding to the option, Users can't add or log on with Microsoft accounts: This option will have the following features:

  • Prevent User from adding new Microsoft account on the computer when using the old Microsoft account.
  • Users will not be able to transfer Local accounts (local accounts) to Microsoft accounts.
  • The user will not be able to connect an account currently in use in the organization to a Microsoft account.
  • Existing Microsoft account users will not be able to log into Windows.
  • An administrator (User using a Microsoft account) will not be able to log into Windows 10 systems.

Based on the features available on the two options, you should choose the first option (Users can't add Microsoft accounts) to prevent users from adding Microsoft accounts to your Windows 10. Then click Apply and OK to finish.

Some computers have additional Microsoft account errors due to the above settings, so if you encounter errors, please check the settings in this custom.

Leave a Comment

Enable FIPS Mode on SLES 15 and Verify the Boot State

Enable FIPS Mode on SLES 15 and Verify the Boot State

Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.

Set Up a LUKS-Encrypted Data Volume on SLES

Set Up a LUKS-Encrypted Data Volume on SLES

Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.

Build a Custom AppArmor Profile on SUSE Linux

Build a Custom AppArmor Profile on SUSE Linux

Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.

Build a Local SUSE Update Server with RMT on SLES 15

Build a Local SUSE Update Server with RMT on SLES 15

Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.

Join SLES 15 to Active Directory with SSSD in YaST

Join SLES 15 to Active Directory with SSSD in YaST

Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.

Enable SLES Live Patching and Verify a Kernel Fix

Enable SLES Live Patching and Verify a Kernel Fix

Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.

Install and Sign Custom Kernel Modules on SLES 15 Secure Boot

Install and Sign Custom Kernel Modules on SLES 15 Secure Boot

Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.

Keep Services Available During a SLES 15 SP5 to SP6 Upgrade

Keep Services Available During a SLES 15 SP5 to SP6 Upgrade

SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.

Apply the SLES 15 STIG Safely with OpenSCAP

Apply the SLES 15 STIG Safely with OpenSCAP

Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.

Restore Cockpit Access to SUSE Linux Enterprise Server

Restore Cockpit Access to SUSE Linux Enterprise Server

Trace a failed Cockpit connection through DNS, port 9090, the systemd socket, firewalld, TLS, and login settings using current SUSE guidance.