> For the complete documentation index, see [llms.txt](https://docs.tminus365.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tminus365.com/security/azure-ad-entra/highly-privileged-accounts-shall-be-cloud-only.md).

# Highly privileged accounts shall be cloud-only

## Description

Assign users that need to perform highly privileged tasks to cloud-only Azure AD accounts to minimize the collateral damage of an on-premises identity compromise.

## Policy

* Users that need to be assigned to highly privileged Azure AD roles SHALL be provisioned cloud-only accounts that are separate from the on-premises directory or other federated identity providers.

## Licensing Considerations

• All Microsoft Licensing Models support this configuration.

## Set Up Instructions

1. Follow [these steps](https://learn.microsoft.com/en-us/azure/active-directory/roles/view-assignments) to review the administrative roles like Global Administrator
2. Ensure that these accounts are cloud only

## End-User Impact

{% hint style="info" %}
Level: <mark style="color:green;">None</mark>
{% endhint %}

There is no real end user impact here as you are establishing cloud only administrative accounts.

{% hint style="info" %}
Tips

Periodically review the privileged roles within the organization to ensure compliance with this policy.
{% endhint %}

## PowerShell Scripts

Getting Sync Status: [Listing Azure AD/Office 365 User Accounts with Directory Sync Status (practical365.com)](https://practical365.com/listing-azure-ad-office-365-user-accounts-directory-sync-status/)

[View Microsoft 365 user accounts with PowerShell - Microsoft 365 Enterprise | Microsoft Learn](https://learn.microsoft.com/en-us/microsoft-365/enterprise/view-user-accounts-with-microsoft-365-powershell?view=o365-worldwide#view-account-synchronization-status)

## Videos

• None Currently


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.tminus365.com/security/azure-ad-entra/highly-privileged-accounts-shall-be-cloud-only.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.