SPF (Sender Policy Framework), DKIM (Domain Keys Identified Mail) and DMARC (Domain based Message Authentication, Reporting and Conformance) are used to check email messages. In combination, the three procedures achieve a high level of security with regard to the authenticity of the sender and content of an email.
This guide sets up SPF, DKIM and DMARC for Exchange Online.
Azure Resource Locks can be used to easily and effectively protect Azure subscriptions, resource groups or individual resources from accidental deletion. The lock overrides any user permissions.
This guide shows how to enable Azure Resource Locks and which properties can be configured.
The Azure Naming Tool is a free tool for docker container that always generates the correct name for an Azure resource based on best practices.
Microsoft has provided guidance on the various phases in the cloud adoption strategy in the Cloud Adoption Framework. These guides also include best practices for naming Azure resources. Naming is extremely important, but it is also very extensive. As a result, many ambiguities or errors can arise when naming resources.
This guide describes the installation and configuration of Azure Naming Tool step-by-step on a Docker container.
Passwordless Sign In with a FIDO2-enabled security key such as a YubiKey in conjunction with Azure AD provides high security while maintaining ease of use. There is no longer any need to enter a username and password.
For users with private mobile devices who do not want to install the Microsoft Authenticator app, a security key from YubiKey offers a good alternative.
This tutorial sets up a YubiKey 5 security key for passwordless sign in to Microsoft Azure and Microsoft 365 services.
Microsoft offers with Azure AD B2B Direct Connect for shared channels in Microsoft Teams a feature that simplifies management for collaboration with external partners in teams.
Until the release of Azure AD B2B Direct Connect, an external partner was invited to the tenant as a guest and authorized in Microsoft Teams (Azure AD B2B Collaboration). The external partner then received an email with instructions for further steps.
When looking in to the own Azure Active Directory everyone notes: each external user gets a guest account in our own Azure Active Directory. Whether the guest account is still in use or not, it will always remain in Azure Active Directory until it is manually deleted.
Powered by WordPress & Theme by Anders Norén