Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Traditional premise-based Active Directory solutions are not specifically designed to handle identity and access control for the multitude of cloud-based services that may exist in a given organization. For example in traditional AD we have an "organization", that contains "groups", that contain "people". Today's multi-dimensional world requires a more flexible hierarchy.  Azure Active Directory (Azure AD) was designed specifically to meet cloud requirements, and SoftNAS Cloud® SoftNAS® is fully compatible with both traditional and Azure AD.

...

Widget Connector
urlhttps://www.youtube.com/watch?v=DGEZ8TWeoAU

Configuring a Network on the Classic Portal

The first step in planning your Azure AD configuration is to determine and create your virtual network.

Configuring A Network on Azure's Classic Portal

Configuring Azure Active Directory

Azure Active Directory is configured from the classic Azure management portal.  It is a simple and straightforward process, provided virtual networks are configured.

Configuring Azure Active Directory

Creating a User

 A user is required to authenticate access to your Azure AD configuration. Of course, any number of users and groups can be created, with whatever access level is deemed necessary. However, for the purposes of connecting SoftNAS instances to Azure AD, you will need one account with the appropriate rights.

Creating A User to connect Azure AD

Set up Network Peering

To ensure network connectivity for your Azure AD configuration, you will need to peer a standard Azure virtual network with a classic Azure virtual network. The primary considerations for this to work are that they must both be in the same region, and both under the same subscription.

...