--- sourceDocument: Australia IT Service Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-service-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Service Management ft:clusterId : - itsm bundleId : - itsm workflow : - Technology --- # Exploring DevOps Config # Exploring DevOps Config {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Exploring DevOps Config DevOps Config provides a centralized platform to store, manage, and validate configuration data as a single source of truth. It helps ServiceNow customers prevent and resolve configuration-related issues such as unintended changes or "drift" by validating config data before deployment and enabling rollback to previous states if necessary. While it remains supported, starting with the Washington D.C. release, DevOps Config is being prepared for future deprecation and will no longer be activated by default on new instances. Show full answer Show less ## Key Features * **Centralized Configuration Management:** Consolidates and secures configuration data from multiple sources with role-based access control, ensuring data integrity and security. * **Pre-Deployment Validation:** Automatically validates configuration data against customizable policies before deployment to prevent risky or non-compliant changes. * **Conflict Resolution and Root Cause Analysis:** Facilitates comparison of current and past config versions linked to change requests, enabling quick identification and resolution of configuration drift. * **Integration with CI/CD Pipelines:** Supports automated gates that can halt deployments if configuration changes are deemed risky or non-compliant, improving release safety and speed. * **App Containerization:** Organizes configuration data within application containers that connect DevOps Config with other ServiceNow products like DevOps Change Velocity. * **Powered by CDM and PaCE:** Utilizes Configuration Data Management and Policy as Code Engine to enforce configuration policies effectively. ## Practical Benefits for ServiceNow Customers * **Faster, Safer Deployments:** DevOps teams can confidently release changes faster, knowing that configuration data complies with company policies and standards. * **Reduced Configuration-Related Outages:** Early detection and prevention of non-compliant changes reduce the risk of outages caused by configuration errors. * **Seamless Integration:** DevOps Config integrates smoothly with existing tools and workflows, requiring no new tools or major process changes for app engineers or infrastructure owners. * **Visibility and Control:** By linking with DevOps Change Velocity, customers gain comprehensive visibility across the deployment lifecycle while maintaining strict control over configuration data. ## What to Expect ServiceNow customers using DevOps Config can expect a unified, policy-driven approach to configuration management that improves compliance, reduces risk, and accelerates deployment velocity. While the tool continues to be supported, customers should be aware of its planned deprecation in future releases and plan accordingly. Use DevOps Config to store and manage all of your config data as a single source of truth. You can also use DevOps Config to validate your config data before deployment, and resolve conflicts in deployed config data. Important: Starting with the Washington D.C. release, DevOps Config is being prepared for future deprecation. It will be hidden and no longer activated on new instances but will continue to be supported. Use root cause analysis of configuration-related outages or alerts to quickly identify and resolve unintended config data changes, also known as configuration "drift." Compare current and past versions of intended config data changes attached to change requests, and roll back to the desired state when needed. For more information, see [Investigate config change alerts](https://www.servicenow.com/docs/u3OyJU61GCMKCi6UfQ464w "A high percentage of alerts occur due to errors in config data. If the chain of events that resulted in an alert includes a change request that involves the same CI as the alert, then you can use a variety of tools to isolate the config changes that might have caused the alert."). ## Manage your configuration data {#devops-config-getting-started__section_vzx_l4w_2pb} DevOps Config becomes the single source of truth for your configuration data, rather than the source tool. A consolidated model manages and secures config data across multiple sources with role-based access control. Although DevOps Config prevents non-compliant changes by validating your configuration data before deployment, security of the configuration data can't be enforced if the data is kept at the source and not stored in DevOps Config. * WorkflowDevOps Config manages all your data in one location, validates it as it's written, and exports, when needed. * DevOps Engineer personaUse DevOps Config and DevOps Config API to manage and validate configuration data. Thus, enabling DevOps teams to release at a faster speed, ensuring that no risky or non-compliant changes are introduced in production. Use automated gates in a CI/CD pipeline or deployment script so that a deployment is stopped if any change to the application or infrastructure configuration is deemed risky or non-compliant. Manage DevOps Config as more policies are added and more exporters are defined. {#devops-config-getting-started__ul_mmd_3mq_25b} ## Validate your configuration data {#devops-config-getting-started__section_ufq_bhg_3pb} DevOps Config acts as a test tool by automatically validating your configuration data before deployment to prevent non-compliant changes, while ensuring adherence to policy frameworks. Validation before deployment occurs by executing policies on the configuration data. The DevOps Config Policy content pack includes generic policies that check for standard issues, but can be customized based on use case. * WorkflowWhen configuration data is changed or added, DevOps Config runs policies on the configuration data that's stored across multiple sources, validates it, and returns the outcome. In the pipeline, the decision on whether to deploy is made, and the configuration data is retrieved from the source (Git, for example) to deploy. * App Engineer (or IT infrastructure owner) personaUse DevOps Config to validate configuration data. Thus, making sure no risks are introduced and that all changes are compliant with company policies before any changes are applied in a production environment. Since the tool integrates with the existing toolset, there's no change to the way work is done and there are no new tools to learn. Changes made to configuration data are validated in the background, and when the outcome is reported, action can be taken. {#devops-config-getting-started__ul_ahs_2mq_25b} * **[DevOps Config and DevOps Change Velocity](https://www.servicenow.com/docs/OHbxDSCer4~p7kyrseiV6w)** DevOps Change Velocity collects data from all of your DevOps tools, providing visibility across the entire lifecycle of deployment, while DevOps Config manages and validates your DevOps configuration data. * **[Using an app in DevOps Config](https://www.servicenow.com/docs/EECjH4KHXhRhlv_ceYTCDg)** When you create an app in DevOps Config, not only is it the container for the config data of the application, but the application model you choose links DevOps Config with other ServiceNow products, including DevOps Change Velocity. * **[DevOps Config powered by CDM and PaCE](https://www.servicenow.com/docs/__Wno1iJ97s_C0mmcalyZw)** DevOps Config uses Configuration Data Management and Policy as Code Engine platform capabilities to manage configuration data and policies. * **[DevOps Config terms](https://www.servicenow.com/docs/ohdWv3DuRv5AM3iUikiEOg)** These are some of the common DevOps Config terms.