vRealize Automation 8.1 Initial Configuration – Part 1

In last blog, I had covered deployment of vRealize Automation 8.1. You can follow below link to look at deployment. Complete blog series links:

But, true fun begins after deployment while configuring vRealize Automation. There are multiple configuration steps, needs to be followed and sometime they can become overwhelming if coming from vRA 7.x environment. So, i have tried to create guide around initial configuration post deployment. It will cover configuration starting from Identity and Access Management, going to Cloud Assembly and then Service Broker for catalog. I will try to map key terms with their counterparts in vRA 7.x. Without further wait, let’s get started with part 1.


Architecture of vRealize Automation 8.1 has changed from 7.x. There are no more Windows IaaS Manager, IaaS web Servers. We now have 5 different services to manage vRealize Automation environment:

  1. Identity and Access Management – User, Group and Access Management.
  2. Cloud Assembly – Add and maintain your infrastructure, Create application cloud templates, and manage deployments.
  3. Service Broker – Provide the cloud templates and other templates to consumers in a catalog. Consumers can manage their deployments. Create and apply policies.
  4. Code Stream – Create and manage continuous integration and continuous delivery of software.
  5. vRealize Orchestrator – Design workflows that can turn anything into a service.

We will start with Identity and Access Management, integrate Active Directory, import users/groups from AD for granular access management, assign roles to users as per their role function.

Configuring Identity and Access Management

  1. Login into vRealize Automation system credentials which were specified during deployment.
    • You will notice three tabs:
      • Services: To configure vRA services
      • Identity And Access Management: To manage Users/Groups
      • Branding: To change company name, banner color etc. for vRA portal
    • In order to configure Active Directory, we need to go to vRLCM.
  1. Go to vRealize Suite Lifecycle Manager and Click on Identity and Tenant Management.
  1. Go to Directory Management > Directories/
  1. You can add directories in two ways
    • Active Directory over LDAP – You configure AD as LDAP services by providing bind user and server for authentication
    • Active Directory over IWA – If vIDM appliance is joined to AD, AD authentication can happen via machine account.
  1. I am using AD over LDAP method, so provide following details:
    • Directory Name – Name to identify AD Directory in vIDM
    • Select Connector – vIDM connector created to connect to Active Directory and sync users, default connector is created automatically during deployment
    • Directory Search Attribute – AD attribute to identify user name, default is sAMAccountName
    • Server Location – If DNS service records to locate AD domains
    • Certificate – Require if AD requires STARTTLS encryption
    • Bind User Details – User information to connect and sync users from AD
      • Base DN – Base location in AD from where users search with begin
      • Bind DN – complete distinguished name for bind user name
      • Bind Password – Password for Bind user
  2. Click on Test Connection to ensure connection to AD is successful.
  1. Select the Active Directory domains, from where users needs to be synced.
  1. Select User attributes needs to be synced with vIDM from Active Directory. Please note that lastname, username, email and firstname are required parameters. If any user, doesn’t have these parameters set in AD, they will not be synced with vIDM.
  1. Provide the group DN to search and select groups from Active Directory. You can use Select All option to select all groups.
  1. Similarly, provide base DN for users to search and sync users from Active Directory to vIDM.
  1. Once on last step for Dry Run, it will provide you summary about how many users/group with be added to vIDM or removed from vIDM.
  1. If you are happy with results, click on Save and Sync and Active Directory will be added under Directory Management to assign roles to AD Users/Group in vRA.
  1. Go back to vRealize Automation Portal and Click on Identity and Access Management.
    • Click on Enterprise Groups.
    • Search for desired AD Group, you would like to add, in my case it was Domain Admins.
  1. Here, is the interesting part. There are two permissions in vRA 8.x.
    • Organization Roles – These are Organization Wide roles and every user needs to be assign these roles. This will provide login access to users to vRA portal. If you didn’t assign Organization Roles, then login will not work.
    • Service Roles – These are roles for specific services such as Service Broker, Cloud assembly etc.
  1. Assign the appropriate Organization Role:
    • Member – Users will not have access to Identity and Access Management
    • Owner – Users have will have access to Identity and Access Management and they can manage access for other users.

16. Assign the appropriate service roles and click Assign.

  1. At this point, log out from vRA portal. Once you back to login page, it will prompt you to select desired domain.


In this blog, we have covered how to configure Active Directory with vRealize Automation. This will allow us to import Users/Groups from Active Directory to vRA and assign them roles and access. This allows central management of Role based access control.

In next blog, I will cover how to manage infrastructure, integrate it with vRealize Automation, create template with help of Cloud Assembly.

5 thoughts on “vRealize Automation 8.1 Initial Configuration – Part 1

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.