[azure_functions] enable agentless deployment

[jakubgalecki0]

Proposed commit message

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[github-actions]

✅ Vale Linting Results

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[github-actions]

TL;DR

Buildkite failed before any repo tests ran: the agent environment hook could not fetch the GitHub token from Vault (github/token/elastic-integrations-pipeline) during the Upload Pipeline step. This is a CI configuration/secret-access issue, not a code regression in this PR.

Remediation

• Restore/fix Vault access for github/token/elastic-integrations-pipeline (secret exists, role/path permissions valid for pipeline integrations).
• Re-run the Buildkite build after Vault token access is fixed.

Investigation details

Root Cause

The build fails in the initial Buildkite agent environment hook, before pipeline upload and before package tests. The hook retries Vault reads 5 times and exits non-zero because the token path is missing/inaccessible.

Relevant repository context:

• .buildkite/pipeline.yml:1 is the pipeline file being uploaded by the failed step (buildkite-agent pipeline upload .buildkite/pipeline.yml).
• The failure occurs prior to executing repo scripts (agent hook stage), so PR code changes are not implicated by the observed error.

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/42409
• Job/step: :pipeline::arrow_up: Upload Pipeline: .buildkite/pipeline.yml
• Key log excerpt (/tmp/gh-aw/buildkite-logs/integrations-pipelinearrow_up-upload-pipeline-buildkitepipelineyml.txt):

Attempting to retrieve GitHub token from Vault at path: github/token/elastic-integrations-pipeline
No value found at github/token/elastic-integrations-pipeline
Retry 5/5 exited 2, no more retries left.
Error setting up job executor: running "agent environment" shell hook: The agent environment hook exited with status 1

Verification

• Not run: repository tests/build steps did not execute because the failure happened during agent environment initialization.

Follow-up

If this PR comes from a fork, confirm whether this pipeline is expected to have Vault-backed token access for fork-origin runs; if not, run from a trusted context or adjust CI policy accordingly.

Note

🔒 Integrity filter blocked 2 items

The following items were blocked because they don't meet the GitHub integrity level.

• #18851 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• [azure_functions] enable agentless deployment #18851 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[elastic-vault-github-plugin-prod]

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 03bdfb7

History

• 💚 Build #42633 succeeded 4974cd7
• 💚 Build #42528 succeeded e9599c2
• 💔 Build #42409 failed 0c9c178
• 💔 Build #42407 failed 408d85d

[elastic-vault-github-plugin-prod]

Package azure_functions - 0.13.0 containing this change is available at https://epr.elastic.co/package/azure_functions/0.13.0/