User settings
This page describes the configuration of user settings within Microsoft Entra ID associated with systems built according to the guidance provided by ASD's Blueprint for Secure Cloud.
Estimated reading time: 2 minutes
Instruction
The below tables outline the as built configuration for ASD’s Blueprint for Secure Cloud (the Blueprint) for the Microsoft Entra admin portal at the following URL:
The settings described on these pages provide a baseline implementation for a system configured using the Blueprint. Any implementation implied by these pages should not be considered as prescriptive as to how an organisation must scope, build, document, or assess a system.
Implementation of the guidance provided by the Blueprint will differ depending on an organisation’s operating context and organisational culture. Organisations should implement the Blueprint in alignment with their existing change management, business processes and frameworks.
Placeholders such as <ORGANISATION.GOV.AU>, <BLUEPRINT.GOV.AU> and <TENANT-NAME> should be replaced with the relevant details as required.
Default user role permissions
| Item | Value |
|---|---|
| User can register application | No |
| Restrict non-admin users from creating tenants | Yes |
| Users can create security groups | No |
Guest user access
| Item | Value |
|---|---|
| Guest user access restrictions | Guest user access is restricted to properties and memberships of their own directory objects (most restrictive) |
Administration center
| Item | Value |
|---|---|
| Restrict access to Microsoft Entra admin centre | Yes |
LinkedIn account connections
| Item | Value |
|---|---|
| Allow users to connect their work or school account with LinkedIn | No |
Show keep user signed in
| Item | Value |
|---|---|
| Show keep user signed in | Yes |
User features
Related information
Security & Governance
- Multi-factor Authentication
- Authentication Hardening
- Essential Eight - Restrict Administrative Privileges