Home/Certifications/Microsoft/Microsoft AZ-104: Azure Policy Initiatives Cloud & ArchitectureUpdated October 10, 2026 · 7 min read An Azure Policy initiative is useful when several related controls serve one governance objective. It should make evaluation and remediation easier to manage without hiding what the individual policies do. An initiative groups policy definitions so the organization can report a coherent governance outcome. Useful design depends on scope, parameters, exemptions, enforcement effects, and the difference between detecting noncompliance and automatically changing a resource. A useful initiative should also let reviewers identify which individual policy…

Home/Certifications/Microsoft/Microsoft AZ-104: Monitor Data Collection Rules Cloud & ArchitectureUpdated October 10, 2026 · 6 min read Azure Monitor Data Collection Rules make telemetry routing and transformation explicit. A good DCR starts with the operational question the data must answer and ends with a test that proves the correct records reached the intended destination. Data Collection Rules define which telemetry Azure Monitor collects, transforms, and routes. If a source, association, destination, or transformation is wrong, a healthy workload can appear silent even while logs exist somewhere in the environment. On this…

Home/Certifications/Microsoft/Microsoft AZ-104: Load Balancer vs. App Gateway Cloud & ArchitectureUpdated October 10, 2026 · 7 min read Azure Load Balancer and Application Gateway solve different routing problems. The choice turns on transport versus HTTP awareness, required security features, health behavior, and where traffic enters the workload. A regional layer-seven entry point and a transport-level load balancer do different work. Compare protocol support, TLS handling, health evaluation, network placement, and failure behavior before deciding where application traffic should first be received. A choice that fits the protocol but ignores TLS, backend…

Home/Certifications/Microsoft/Microsoft AZ-104: Zones and Failure Domains Cloud & ArchitectureUpdated October 10, 2026 · 6 min read Azure availability zones and fault domains represent different infrastructure isolation concepts. The important design question is not which label appears in the portal, but which shared failure could interrupt the workload. Spreading instances across zones improves resilience only when the application and its dependencies can tolerate the loss of a zone. Storage, routing, state synchronization, and deployment configuration must agree with the failure model the architecture claims to address. On this pageThink about the…

Home/Certifications/Microsoft/Azure Well-Architected Design for Operations Cloud & ArchitectureUpdated October 10, 2026 · 7 min read Azure architecture quality cannot be reduced to a security score or uptime target. Operationally successful workloads balance reliability, security, cost, performance, and the ability to change them safely. A design review is incomplete if the application meets its immediate functional need but cannot be observed, maintained, or recovered. Translate reliability, security, cost, and operational-excellence principles into concrete administrative checks that can be repeated after deployment. On this pageEstablish what the workload must achieveDefine reliability as…

Service Graph Connectors are ServiceNow’s predefined integrations for bringing third-party infrastructure, cloud, endpoint, observability, security, and API-management data into the CMDB and related tables. Their value is not simply that they import records. The connectors are designed around ServiceNow’s CMDB data model, Common Service Data Model alignment, staging/transformation, and IRE-based identification and reconciliation so external tool data can contribute to shared configuration state without creating a separate source-specific CMDB. On this page Use connectors when a supported integration exists Preserve IRE as the identity boundary Monitor connector freshness and failures…

Application services—called service instances in current CSDM terminology—represent the operational reality of an application or service: the interconnected applications, hosts, databases, middleware, load balancers, and other CIs that deliver a service in a particular environment or context. They bridge high-level portfolio and service definitions with the technical graph that incident, change, service health, and automation need during real operations. Home/ServiceNow/ServiceNow CIS-DF: Modeling Application Services in CSDMServiceNowPublished October 7, 2026On this pageSeparate portfolio from operational instanceChoose the population method deliberatelyKeep relationships aligned to CSDMAssign owners at the correct layerUse the service-instance…

ServiceNow’s Identification and Reconciliation Engine solves two separate CMDB problems. Identification asks, “Does this incoming payload describe a CI that already exists?” Reconciliation asks, “If several sources know about the same CI, which source is allowed to update this attribute?” Treating these as one generic deduplication feature hides the architecture that keeps multi-source CMDB data trustworthy. On this page Understand identification first Test ambiguous and missing identifiers Use dynamic rules where the business requires them Model dependent CIs correctly Make IRE part of integration design Test same-CI identity and field…

Duplicate configuration items are rarely just a cleanup problem. They are evidence that one or more ingestion paths disagree about identity. Two records may represent the same server because Discovery and a connector used different identifiers, a transform bypassed IRE, a hostname changed, a cloud resource was recreated, or an identification rule was too weak. Manually merging the records fixes today’s symptom; fixing the identity architecture stops tomorrow’s duplicates. Home/ServiceNow/ServiceNow CIS-DF: Fixing Duplicate CIs in ServiceNowServiceNowPublished October 7, 2026On this pageConfirm that the records are truly duplicatesFind the ingestion paths…

ServiceNow Discovery is useful only when the data it collects improves the CMDB instead of creating a second stream of noisy infrastructure records. Discovery can scan IP ranges, use MID Servers and credentials, classify devices, run patterns or probes, identify configuration items, and update the CMDB on a schedule. The engineering challenge is making sure those observations land in the correct classes, match existing CIs, respect source authority, create useful relationships, and age out correctly when the underlying environment changes. Home/ServiceNow/ServiceNow CIS-DF: Discovery Data Into a Healthy CMDBServiceNowPublished October 7,…

ServiceNow’s Common Service Data Model is a prescriptive model for organizing service-related data so the Now Platform can use the same definitions across products and workflows. CSDM 5 extends that model and clarifies how business capabilities, business applications, services, service offerings, service instances/application services, and infrastructure configuration items relate to one another. It is not a separate product or SKU, and it is not an implementation process that replaces configuration management. On this page Think of CSDM as shared language Use business and technical services deliberately Follow current prescribed relationships…

CMDB health should answer whether ServiceNow contains enough accurate, governed, and relationally useful configuration data to support operations. A single “health score” can be convenient, but teams need to understand the components behind that score and which defects actually affect incident, change, service mapping, automation, and reporting. On this page Use Completeness for fields teams actually need Check compliance and relationship quality Set thresholds by class importance Watch trend and recurrence Use the dashboard as a starting point Diagnose correctness, compliance and relationship gaps Route meaningful remediation and measure progress…

CMDB governance fails when everyone can write data but nobody owns the meaning, quality, or lifecycle of what was written. ServiceNow CMDB spans infrastructure, applications, cloud resources, service modeling, ITSM, ITOM, asset management, security, enterprise architecture, and reporting. No single team has enough context to govern all of those domains alone. On this page Define the platform steward Assign source-system ownership Govern relationships separately Make health metrics actionable Measure governance by trust and throughput Assign decision rights and govern sensitive CMDB access Prioritize governance by critical service risk Maintain stewardship…

A clean ServiceNow CMDB begins with a disciplined data model: configuration items belong in the right classes, each class has a clear purpose and identifiers, authoritative sources are known, duplicate creation is controlled, relationships are consistent, and lifecycle rules remove records that no longer represent the environment. Cleaning data after every import is expensive; designing the model so bad data is harder to create is more scalable. Home/ServiceNow/ServiceNow CIS-DF: CMDB Data Models That Stay CleanServiceNowPublished October 7, 2026On this pageUse the existing class hierarchy firstUse IRE for identificationKeep identifiers stableDesign…

Configuration items become operationally useful when ServiceNow can show how they depend on one another and which services they support. A server record with perfect CPU, owner, and serial-number data can still be almost useless during an outage if nobody knows which application service depends on it. CI relationships turn the CMDB from an inventory into a model that can support impact analysis, change planning, troubleshooting, service health, and automation. Home/ServiceNow/ServiceNow CIS-DF: CI Relationships That Support OperationsServiceNowPublished October 7, 2026On this pageModel relationships that answer operational questionsPrefer platform-standard relationshipsConnect infrastructure…