Access Management
All about AEM
Azure DevOps
Environments, Deployments and Security
100

Is a powerful tool for managing network resources, ensuring security, and providing a centralized platform for user management. Its various components and tools make it an essential part of IT infrastructure in many organizations.
We normally use this in managing AZDO and CyberArk Access

Active Directory

100

This admin role allows users to create and manage Adobe support tickets.

Support Administrator

100

Stores secrets used for pipelines. Our team used it for retrieving credentials used for GitSync process

AzureKeyVault

100

This platform/tool is what we used to log and track service request, incidents and change requests.

ServiceNow

200

An AZDO group is required for administering work items, repos, pipelines, and test cases in AzDO.

ProjectAdministrators

200

Support admin role allows users to create and manage Adobe support tickets - which type of ID should be used for this access? 

EID/ Enterprise ID

200

Refers to aligning development (or other) branches with the release or master branch, including deleting the branch in the Adobe repository to ensure accurate synchronization.

Branch Refresh Activity

200
Our production pipeline in Adobe deploys our codes in master branch in Stage and Production Environments. 

(Yes or No)

Yes

300

For Admin Console requests, this document states that System Admin, Product Admin, and Product Profile admin access require this prerequisite type of account. 

ADS Account

300

Is a cloud service that automates the deployment, testing, and management of Adobe Experience Manager (AEM) applications both in and out of the cloud. It provides a CI/CD pipeline, environment management, and performance monitoring, ensuring optimal performance and stability.

Cloud Manager

300

Are a set of rules and automated controls that govern how code changes are managed, reviewed, and merged within a version control system.

Branch policies

300

An essential item used for managing configurations across different environments (e.g., development, staging, production). They allow developers to separate code from configuration, enhance security, and adapt application behavior dynamically without requiring code changes or redeployments. - Clue this has a limit of 200 for each environment

Environment variables

400

What tool is used to manage users, groups, and roles for Adobe Experience Manager

Admin Console

400

Is an optional feature that enables you to create and automatically run Custom UI tests for your applications.

Custom UI testing

400

A proposal to merge a set of changes from one branch into another.

Pull Request (often referred to as “PR”)

400

Is the security practice of regularly changing passwords for user accounts, service accounts, or application credentials to reduce the risk of unauthorized access if a password is exposed or compromised.

PAM or Password Rotation Activity

500

We can provide Adobe Experience Manager / AEM Author access to Adobe Resources if there is a need for investigation purpose? 

YES

500

Type of instances of AEM Environment

Author and Publish - (Bonus for Preview)

500

Securely links your pipelines to external services like AzureKeyVault, GitHub, Docker, AWS Services or Kubernetes. It stores authentication details and permissions so pipelines can deploy or interact with these resources without exposing credentials.

Service Connection

500

The corresponding pipeline in Adobe for Dispatcher? 

Web-Tier