You need to resolve the issue of the sales department users. What should you configure for the Azure AD tenant?
In Microsoft Entra ID (Azure AD), the per-user device cap is controlled in Devices > Device settings. The SC-300 materials describe that administrators can configure ''Users may join devices to Azure AD'' and the ''Maximum number of devices per user''. The guide notes that this limit defaults to five and is used to ''control how many devices a user can join or register in Azure AD''; when users reach the limit, ''they cannot add additional devices until the limit is increased or an existing device is removed.'' For scenarios like field or sales staff who use multiple devices, the study content recommends adjusting this value to meet business needs. Because A. Datum's sales users hit the current cap and a requirement states ''Increase the maximum number of devices that can be joined or registered to Azure AD to 10,'' the fix is to change the tenant's Device settings---not User settings, Access reviews, or Security defaults. This aligns with the exam objective to configure device settings for Azure AD join and registration and addresses the precise symptom reported by users.
Your network contains an Active Directory forest named contoso.com that is linked to an Azure Active Directory
(Azure AD) tenant named contoso.com by using Azure AD Connect.
You need to prevent the synchronization of users who have the extensionAttribute15 attribute set to
NoSync.
What should you do in Azure AD Connect?
In Azure AD Connect, filtering which users synchronize is achieved via synchronization rules. The SC-300 study content explains that to exclude objects based on an on-premises attribute (for example, extensionAttribute15=NoSync), you create an inbound rule on the Active Directory Domain Services (AD DS) connector. Inbound rules control the flow of data from AD DS into the metaverse, where you can use a scoping filter to mark objects as filtered (often via the cloudFiltered projection), preventing them from being provisioned to Azure AD. The official guidance highlights that inbound rules on the AD DS connector are used for attribute-based filtering and that export or run profiles (Full Import/Export) do not define logic; they only execute the configured rules. Therefore, to stop users with extensionAttribute15=NoSync from syncing, you create an inbound synchronization rule on the AD DS connector with a condition on that attribute to exclude those users from synchronization.
You have a Microsoft Exchange organization that uses an SMTP address space of contoso.com.
Several users use their contoso.com email address for self-service sign-up to 1 Microsoft Entra.
You gain global administrator privileges to the Microsoft Entra tenant that contains the self-signed users.
You need to prevent the users from creating user accounts in the contoso.com 2 Microsoft Entra tenant for self-service sign-up to Microsoft 365 services.
Which PowerShell cmdlet should you run?
According to the Microsoft SC-300 Study Guide and Microsoft Learn module: ''Manage Microsoft Entra domains and custom domain names'', when users perform self-service sign-up (email verified users) using a public domain such as contoso.com, Microsoft Entra creates a shadow tenant that you can later claim ownership of by verifying the DNS domain.
Once you become the Global Administrator of the verified tenant, you can control domain behavior, including blocking self-service sign-up using that domain. To disable further self-service creation of accounts for that domain, you must modify the domain configuration using the Update-MgDomain PowerShell cmdlet.
The cmdlet Update-MgDomain allows you to change properties of the domain, such as IsDefault, IsVerified, and crucially, blocking self-service sign-ups.
Example:
Update-MgDomain -DomainId contoso.com -IsAdminManaged $true
This action prevents external or unverified users from using @contoso.com email addresses for new self-service sign-ups.
Other options like Update-MgPolicyAuthorizationPolicy, Update-MgPolicyPermissionGrantPolicyExclude, and Update-MgDomainFederationConfiguration are used for tenant-wide access, permission grants, or federated authentication but not to block self-service domain registration.
You have a Microsoft Entra tenant that contains the devices shown in the following table.

You plan to configure Microsoft Entra Private Access. You deploy the Global Secure Access client to compatible devices. From which devices can you use Private Access?
You have a Microsoft 365 E5 subscription.
Users authorize third-party cloud apps to access their data.
You need to configure an alert that will be triggered when an app requires high permissions and is authorized by more than 20 users.
Which type of policy should you create in the Microsoft Defender for Cloud Apps portal?
According to Microsoft Defender for Cloud Apps documentation and the SC-300 study guide, an OAuth app policy monitors third-party applications that request access to Microsoft 365 data through Microsoft Graph API permissions. These apps can request delegated or application permissions. When an app is authorized by many users and requests high permissions such as Calendars.ReadWrite, it can introduce security risks.
Defender for Cloud Apps allows administrators to create OAuth app policies to generate alerts when an app:
Requires high permissions (e.g., read/write to mailboxes, calendars, or files).
Is authorized by more than a specified number of users (for example, more than 20).
This matches the requirement in the question exactly. Other policy types (anomaly detection, access, or activity) monitor user or session behavior, not app consent behavior.
As per Microsoft's documentation:
''Use OAuth app policies to detect risky OAuth apps, monitor application permissions, and alert when apps are authorized by an unusual number of users or request excessive permissions.''
Angela Howard
9 days agoWilliam Scott
30 days agoJessica Rogers
1 month agoBetty Stewart
2 months agoKimberly Robinson
2 months agoRebecca Jones
3 months agoNancy Miller
3 months agoLisa Parker
3 months agoChristopher Evans
3 months agoMichelle Nguyen
3 months agoMelissa Robinson
2 months agoRonald Lewis
3 months agoCorrina
4 months agoMabel
4 months agoTommy
4 months agoAlberto
5 months agoVerda
5 months agoHobert
5 months agoClarinda
5 months agoTiffiny
6 months agoShanda
6 months agoLuann
6 months agoFrederica
6 months agoEvangelina
7 months agoTheola
7 months agoLilli
7 months agoVilma
7 months agoValentin
8 months agoJin
8 months agoBonita
8 months agoBuck
8 months agoDick
9 months agoMarshall
9 months agoMarjory
9 months agoEric
9 months agoFausto
10 months agoErinn
10 months agoBrent
10 months agoTerrilyn
10 months agoArgelia
10 months agoOdelia
11 months agoEliz
11 months agoStephaine
1 year agoTarra
1 year agoCarlton
1 year agoArminda
1 year agoElli
1 year agoMari
2 years agoSusy
2 years agoSharen
2 years agoMona
2 years agoAn
2 years agoAntione
2 years agoLilli
2 years agoGertude
2 years agoAllene
2 years agoMattie
2 years agoJacqueline
2 years agoEden
2 years agoJuan
2 years agoCherilyn
2 years agoMatthew
2 years agoEladia
2 years agoShaunna
2 years agoHyman
2 years agoFanny
2 years agoArtie
2 years agoRoyce
2 years agoIesha
2 years agoLorriane
2 years ago