@raishin/vanguard-frontier-agentic 2.9.0 → 2.11.0

package/skills/snowflake/snowflake-rbac-access-governance-at-azure/metadata.json

@@ -0,0 +1,29 @@
+{
+  "id": "snowflake-rbac-access-governance-at-azure",
+  "name": "Snowflake RBAC Access Governance at Azure",
+  "type": "skill",
+  "provider": "snowflake",
+  "harnesses": [
+    "codex",
+    "claude-code",
+    "cursor",
+    "gemini",
+    "kiro",
+    "other"
+  ],
+  "summary": "Review Snowflake RBAC role hierarchies, privilege grants, managed-access schemas, network policies, MFA enforcement, and Entra ID External OAuth/SAML/SCIM integration for least-privilege and separation-of-duties compliance on Azure-hosted Snowflake accounts.",
+  "source_type": "original",
+  "official_docs": [
+    "https://docs.snowflake.com/en/user-guide/security-access-control-overview",
+    "https://docs.snowflake.com/en/user-guide/security-access-control-considerations",
+    "https://docs.snowflake.com/en/user-guide/network-policies",
+    "https://docs.snowflake.com/en/user-guide/oauth-azure",
+    "https://docs.snowflake.com/en/user-guide/scim-azure"
+  ],
+  "security_notes": "Static review only — never execute SQL against a live Snowflake account. Production role, grant, policy, or MFA changes are live-guard gated and require explicit approval before execution. Never request credentials, key-pair private keys, OAuth tokens, or tenant IDs.",
+  "last_verified": "2026-06-17",
+  "path": "skills/snowflake/snowflake-rbac-access-governance-at-azure",
+  "author": "github: Raishin",
+  "version": "0.1.0",
+  "companion_agents": ["snowflake-rbac-access-governance-at-azure-agent"]
+}

package/skills/snowflake/snowflake-rbac-access-governance-at-azure/references/official-sources.md

@@ -0,0 +1,33 @@
+# Official sources
+
+Use this reference only when you need source grounding for Snowflake service behavior or the detailed source list.
+
+## Snowflake documentation
+
+Use these as starting points, not as proof of the user's live Snowflake account state:
+- https://docs.snowflake.com/en/user-guide/security-access-control-overview
+- https://docs.snowflake.com/en/user-guide/security-access-control-considerations
+- https://docs.snowflake.com/en/user-guide/network-policies
+- https://docs.snowflake.com/en/user-guide/oauth-azure
+- https://docs.snowflake.com/en/user-guide/scim-azure
+
+## Grounding rule
+
+Official documentation explains Snowflake service behavior. It does not prove the user's current account, edition, role hierarchy, quota, resource configuration, or operational state. Prefer read-only Snowflake MCP or SQL evidence, repository evidence, or sanitized user-provided evidence for current-state claims.
+
+## Current documentation refresh (2026-06-17)
+
+Service facts from official docs:
+- ACCOUNTADMIN encapsulates SYSADMIN and SECURITYADMIN; it must have at minimum two active holders, MFA enforced on all, and must not be used for routine object creation or ETL workloads.
+- SECURITYADMIN holds MANAGE GRANTS; SYSADMIN holds object ownership. SoD requires these roles remain separate.
+- USERADMIN provides CREATE USER and CREATE ROLE without grant privileges; use for provisioning, not policy administration.
+- PUBLIC is automatically granted to every user and role; never assign sensitive object privileges to PUBLIC.
+- Network policies restrict inbound IP access at account, user, or security-integration level. On Azure, AZURELINKID-type rules restrict access to a specific Azure subscription ID.
+- MFA phased enforcement requires password-bearing users to enroll in MFA. Service accounts must use TYPE=SERVICE with key-pair or OAuth; password authentication is prohibited for service users.
+- Entra ID External OAuth (SECURITY INTEGRATION TYPE=OAUTH OAUTH_TYPE=AZURE_AD) issues tokens scoped to Snowflake role; token issuer must match the Entra ID tenant. Do not grant ACCOUNTADMIN to OAuth service principals.
+- SCIM provisioning uses the AAD_PROVISIONER system role (not ACCOUNTADMIN) to own provisioned users and groups. Default password for SCIM-provisioned users is unset when SAML SSO is active.
+
+Review implications:
+- Do not approve broad ACCOUNTADMIN grants from intent alone. Require justification, MFA evidence, minimum-holder audit, and break-glass exception documentation.
+- Do not approve PUBLIC grants for any non-trivial object. Require explicit object scope and business justification.
+- Documentation cannot prove the user's actual role hierarchy, network policy state, or MFA enrollment.

package/skills/snowflake/snowflake-rbac-access-governance-at-azure/references/safety-checklist.md

@@ -0,0 +1,26 @@
+# Safety checklist
+
+Use this reference before privileged, grant-changing, compliance-impacting, or production-impacting recommendations.
+
+## Non-negotiables
+
+- Never ask users to paste private keys, OAuth tokens, service principal secrets, tenant IDs, subscription IDs, account identifiers, or customer data into chat.
+- Use read-only Snowflake MCP or read-only SQL evidence for live state when available; otherwise use repository evidence, sanitized user evidence, or official documentation and label the evidence level.
+- Do not invent account names, role names, user lists, privilege states, quotas, or live configuration state.
+- Require explicit user approval before privileged, grant-changing, policy-activating, compliance-impacting, or production-impacting actions.
+- Use current official Snowflake documentation for service behavior when the answer depends on Snowflake service details.
+- Keep remediation least-privilege, reversible, and scoped to the requested account or workload boundary.
+- Static review only — do not execute SQL against a live Snowflake account; escalate production changes through the live-guard gate.
+
+## Stress checks
+
+- What role grants can expose sensitive data through the hierarchy?
+- What PUBLIC grants expose data without authentication controls?
+- What can escalate privilege through MANAGE GRANTS or ACCOUNTADMIN?
+- What can break production or block rollback?
+- What compliance or audit evidence is missing?
+- What rollback or validation path is unproven?
+
+## Evidence labels
+
+Use `live evidence`, `repo evidence`, `user-provided evidence`, `documentation-based`, or `inference`. Documentation alone never proves the user's live Snowflake account state.

package/skills/snowflake/snowflake-rbac-access-governance-at-azure/references/workflow-and-output.md

@@ -0,0 +1,61 @@
+# Workflow and output contract
+
+Use this reference only when performing the full review, implementation guidance, incident triage, or production-readiness pass.
+
+## Review domains
+
+Check these areas before giving a verdict:
+- System role holders and MFA enrollment; ACCOUNTADMIN count and break-glass procedure
+- Role hierarchy shape: custom roles rolling to SYSADMIN vs. ACCOUNTADMIN; SoD between SECURITYADMIN and SYSADMIN
+- Privilege grants: USAGE chain (database + schema), object privileges, future grants precedence, PUBLIC exposure
+- Managed-access schemas: centralized grant control, schema owner vs. SECURITYADMIN
+- Network policies: account vs. user vs. integration level, AZURELINKID rules, activation and precedence
+- MFA enforcement: policy scope, service user TYPE=SERVICE, key-pair vs. OAuth requirement
+- Entra ID integration: External OAuth token issuer alignment, SAML SSO configuration, SCIM AAD_PROVISIONER role
+
+## Safe workflow
+
+1. **Frame scope**
+   - Account name, Snowflake edition, and Azure region:
+   - Business criticality and owner:
+   - Data classification and compliance driver:
+   - Required outcome:
+   - Explicit non-goals:
+2. **Collect evidence**
+   - Prefer read-only Snowflake MCP or read-only SQL query evidence for current-state claims when available.
+   - Otherwise inspect repository IaC/config (Terraform, SnowSQL scripts), sanitized user evidence, or official Snowflake docs.
+   - Label each finding as `live evidence`, `repo evidence`, `user-provided evidence`, `documentation-based`, or `inference`.
+3. **Stress-test risk**
+   - What can expose data through over-privileged roles or PUBLIC grants?
+   - What can escalate privilege through the role hierarchy?
+   - What can break production or block rollback?
+   - What compliance or audit evidence is missing?
+   - What evidence is missing?
+4. **Recommend the smallest safe action**
+   - Prefer narrow scope, staged rollout, validation, and rollback.
+   - If the safest action is to stop and gather evidence, say that plainly.
+
+## Output contract
+
+Return this structure:
+```markdown
+# Snowflake RBAC Access Governance Review: <scope>
+## Executive verdict
+- Status: READY / READY WITH RISKS / NOT READY / NEEDS EVIDENCE
+- Biggest risk:
+- Evidence level:
+## Scope and assumptions
+- Confirmed:
+- Unknown:
+- Out of scope:
+## Findings
+| Severity | Finding | Evidence | Why it matters | Minimum safe action |
+|---|---|---|---|---|
+## Recommended actions
+1. <action> — owner: <owner>, validation: <check>, rollback: <rollback>
+## Validation
+- Queries or checks:
+- Expected result:
+## Residual risk
+- <risk or explicit none>
+```

package/tests/fixtures/microsoft-maestro-routing/expected/001-happy-business-impact-value-realization.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "microsoft-business-impact-value-realization-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/002-happy-copilot-governance-maestro.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "copilot-governance-maestro-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/003-happy-copilot-studio-agent-governance-alm.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "copilot-studio-agent-governance-alm-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/004-happy-d365-commerce.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "d365-commerce-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/005-happy-d365-customer-insights-journeys.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "d365-customer-insights-journeys-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/006-happy-d365-customer-service-contact-center.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "d365-customer-service-contact-center-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/007-happy-d365-data-migration-cutover.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "d365-data-migration-cutover-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/008-happy-d365-field-service-to-cash.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "d365-field-service-to-cash-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/009-happy-d365-finance-close-to-report.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "d365-finance-close-to-report-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/010-happy-d365-fno-developer-extension.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "d365-fno-developer-extension-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/011-happy-d365-integration-dual-write.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "d365-integration-dual-write-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/012-happy-d365-maestro.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "d365-maestro-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/013-happy-d365-project-operations.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "d365-project-operations-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/014-happy-d365-sales-revenue-operations.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "d365-sales-revenue-operations-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/015-happy-d365-security-sod-governance.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "d365-security-sod-governance-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/016-happy-d365-success-by-design-governance.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "d365-success-by-design-governance-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/017-happy-d365-supply-chain-plan-to-produce.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "d365-supply-chain-plan-to-produce-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/018-happy-fabric-analytics-engineering.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "fabric-analytics-engineering-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/019-happy-fabric-data-engineering.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "fabric-data-engineering-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/020-happy-fabric-power-bi-business-insights-governance.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "fabric-power-bi-business-insights-governance-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/021-happy-m365-backup-bcdr-data-resilience.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "m365-backup-bcdr-data-resilience-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/022-happy-m365-copilot-readiness-governance.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "m365-copilot-readiness-governance-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/023-happy-m365-defender-xdr-security-operations.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "m365-defender-xdr-security-operations-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/024-happy-m365-exchange-sharepoint-information-governance.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "m365-exchange-sharepoint-information-governance-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/025-happy-m365-identity-zero-trust.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "m365-identity-zero-trust-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/026-happy-m365-intune-endpoint-management.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "m365-intune-endpoint-management-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/027-happy-m365-licensing-ea-optimization.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "m365-licensing-ea-optimization-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/028-happy-m365-maestro.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "m365-maestro-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/029-happy-m365-purview-data-security-compliance.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "m365-purview-data-security-compliance-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/030-happy-m365-teams-collaboration-governance.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "m365-teams-collaboration-governance-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/031-happy-m365-tenant-governance.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "m365-tenant-governance-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/032-happy-power-automate-automation-risk-review.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "power-automate-automation-risk-review-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/033-happy-power-platform-alm-pipelines.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "power-platform-alm-pipelines-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/034-happy-power-platform-governance-dataverse-security.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "power-platform-governance-dataverse-security-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/035-happy-power-platform-maestro.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "power-platform-maestro-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/adv-ambiguous.json

@@ -0,0 +1,4 @@
+{
+  "route": [],
+  "mode": "unclassified"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/adv-instruction-injection.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "microsoft-business-impact-value-realization-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/adv-liveguard-01-d365-live-record-field-update-guard.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "d365-live-record-field-update-guard-agent"
+  ],
+  "mode": "live-guard-gate"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/adv-liveguard-02-d365-live-security-role-guard.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "d365-live-security-role-guard-agent"
+  ],
+  "mode": "live-guard-gate"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/adv-liveguard-03-m365-live-identity-posture-guard.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "m365-live-identity-posture-guard-agent"
+  ],
+  "mode": "live-guard-gate"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/adv-liveguard-04-m365-live-sensitivity-label-apply-guard.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "m365-live-sensitivity-label-apply-guard-agent"
+  ],
+  "mode": "live-guard-gate"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/adv-persona-replacement.json

@@ -0,0 +1,9 @@
+{
+  "route": [
+    "copilot-governance-maestro-agent",
+    "d365-maestro-agent",
+    "m365-maestro-agent",
+    "microsoft-business-impact-value-realization-agent"
+  ],
+  "mode": "parallel (4)"
+}

package/tests/fixtures/microsoft-maestro-routing/expected/adv-secrets-bait.json

@@ -0,0 +1,6 @@
+{
+  "route": [
+    "microsoft-business-impact-value-realization-agent"
+  ],
+  "mode": "single"
+}

package/tests/fixtures/microsoft-maestro-routing/inputs/001-happy-business-impact-value-realization.json

@@ -0,0 +1,7 @@
+{
+  "name": "001-happy-business-impact-value-realization",
+  "task": "Review our microsoft impact value realization configuration.",
+  "tags": [
+    "happy-path"
+  ]
+}

package/tests/fixtures/microsoft-maestro-routing/inputs/002-happy-copilot-governance-maestro.json

@@ -0,0 +1,7 @@
+{
+  "name": "002-happy-copilot-governance-maestro",
+  "task": "Review our microsoft Microsoft Copilot Copilot Studio configuration.",
+  "tags": [
+    "happy-path"
+  ]
+}

package/tests/fixtures/microsoft-maestro-routing/inputs/003-happy-copilot-studio-agent-governance-alm.json

@@ -0,0 +1,7 @@
+{
+  "name": "003-happy-copilot-studio-agent-governance-alm",
+  "task": "Review our microsoft studio copilot-studio agent-governance configuration.",
+  "tags": [
+    "happy-path"
+  ]
+}

package/tests/fixtures/microsoft-maestro-routing/inputs/004-happy-d365-commerce.json

@@ -0,0 +1,7 @@
+{
+  "name": "004-happy-d365-commerce",
+  "task": "Review our microsoft commerce d365-commerce Store Commerce POS configuration.",
+  "tags": [
+    "happy-path"
+  ]
+}

package/tests/fixtures/microsoft-maestro-routing/inputs/005-happy-d365-customer-insights-journeys.json

@@ -0,0 +1,7 @@
+{
+  "name": "005-happy-d365-customer-insights-journeys",
+  "task": "Review our microsoft journeys insights-journeys Customer Insights configuration.",
+  "tags": [
+    "happy-path"
+  ]
+}

package/tests/fixtures/microsoft-maestro-routing/inputs/006-happy-d365-customer-service-contact-center.json

@@ -0,0 +1,7 @@
+{
+  "name": "006-happy-d365-customer-service-contact-center",
+  "task": "Review our microsoft contact center service-contact configuration.",
+  "tags": [
+    "happy-path"
+  ]
+}

package/tests/fixtures/microsoft-maestro-routing/inputs/007-happy-d365-data-migration-cutover.json

@@ -0,0 +1,7 @@
+{
+  "name": "007-happy-d365-data-migration-cutover",
+  "task": "Review our microsoft migration cutover d365-data configuration.",
+  "tags": [
+    "happy-path"
+  ]
+}

package/tests/fixtures/microsoft-maestro-routing/inputs/008-happy-d365-field-service-to-cash.json

@@ -0,0 +1,7 @@
+{
+  "name": "008-happy-d365-field-service-to-cash",
+  "task": "Review our microsoft field cash d365-field configuration.",
+  "tags": [
+    "happy-path"
+  ]
+}

package/tests/fixtures/microsoft-maestro-routing/inputs/009-happy-d365-finance-close-to-report.json

@@ -0,0 +1,7 @@
+{
+  "name": "009-happy-d365-finance-close-to-report",
+  "task": "Review our microsoft close report d365-finance configuration.",
+  "tags": [
+    "happy-path"
+  ]
+}

package/tests/fixtures/microsoft-maestro-routing/inputs/010-happy-d365-fno-developer-extension.json

@@ -0,0 +1,7 @@
+{
+  "name": "010-happy-d365-fno-developer-extension",
+  "task": "Review our microsoft fno extension d365-fno configuration.",
+  "tags": [
+    "happy-path"
+  ]
+}

package/tests/fixtures/microsoft-maestro-routing/inputs/011-happy-d365-integration-dual-write.json

@@ -0,0 +1,7 @@
+{
+  "name": "011-happy-d365-integration-dual-write",
+  "task": "Review our microsoft integration dual write configuration.",
+  "tags": [
+    "happy-path"
+  ]
+}

package/tests/fixtures/microsoft-maestro-routing/inputs/012-happy-d365-maestro.json

@@ -0,0 +1,7 @@
+{
+  "name": "012-happy-d365-maestro",
+  "task": "Review our microsoft Covers Finance Supply Chain Business Central configuration.",
+  "tags": [
+    "happy-path"
+  ]
+}

package/tests/fixtures/microsoft-maestro-routing/inputs/013-happy-d365-project-operations.json

@@ -0,0 +1,7 @@
+{
+  "name": "013-happy-d365-project-operations",
+  "task": "Review our microsoft project d365-project Project Operations configuration.",
+  "tags": [
+    "happy-path"
+  ]
+}

package/tests/fixtures/microsoft-maestro-routing/inputs/014-happy-d365-sales-revenue-operations.json

@@ -0,0 +1,7 @@
+{
+  "name": "014-happy-d365-sales-revenue-operations",
+  "task": "Review our microsoft sales revenue d365-sales configuration.",
+  "tags": [
+    "happy-path"
+  ]
+}

package/tests/fixtures/microsoft-maestro-routing/inputs/015-happy-d365-security-sod-governance.json

@@ -0,0 +1,7 @@
+{
+  "name": "015-happy-d365-security-sod-governance",
+  "task": "Review our microsoft sod d365-security sod-governance configuration.",
+  "tags": [
+    "happy-path"
+  ]
+}