Bump azure-core from 1.30.0 to 1.38.0 in /Solutions/WithSecureElementsViaFunction/Data Connectors

[dependabot]

Bumps azure-core from 1.30.0 to 1.38.0.

Release notes

Sourced from azure-core's releases.

azure-ai-ml_1.35.0

1.35.0 (2026-09-08)

Bugs Fixed

• Simplified schedule validation errors so invalid local job paths report the relevant file error instead of errors from every supported job schema.
• Fixed internal pipeline Command node dropping node-level interactive services (SSH, JupyterLab, TensorBoard, VS Code, etc.) during serialization, which prevented interactive endpoints from being created for Singularity jobs. The services are now serialized into the pipeline REST request and round-tripped on deserialization, matching the public Command node behavior.
• Fixed MLClient.jobs.create_or_update, archive, and restore failing for previously-fetched jobs across all job types by routing metadata-only edits through the RunHistory PATCH endpoint.
• Fixed DeploymentTemplate.creation_context always being None when retrieved via get() or list(). The created/modified timestamps and identity returned by the service (as createdTime / modifiedTime / createdBy) are now populated on creation_context, making DeploymentTemplate consistent with Model and Environment.
• Fixed DeploymentTemplate.creation_context.last_modified_by always being None even after the service began returning the modifying identity. The service sends it as a flattened modifiedBy field (top-level for get(), nested under properties for list()) alongside a present-but-null lastModifiedBy; last_modified_by is now populated from modifiedBy, matching how created_by is read.
• Fixed deployment_templates.list(name=...) raising AttributeError: 'str' object has no attribute 'request_timeout'. In the list response, requestSettings / livenessProbe / readinessProbe arrive as stringified dicts nested under properties; these are now parsed before conversion, giving list() parity with models.list() / environments.list().
• Fixed deployment_templates.get(name) failing with a 404 (DeploymentTemplate {name}:latest not found) when no version was supplied, because the literal string "latest" was sent as the version. The latest version is now resolved client-side (the service exposes no latest label and no server-side ordering), and get() accepts a label keyword (label="latest" resolves to the latest version) mirroring models.get(). delete(name) resolves the latest version the same way.
• Fixed models.get(name, label="latest") returning a Model whose default_deployment_template / allowed_deployment_templates references had asset_id=None. Label resolution goes through the version list endpoint (top=1), whose items omit the deployment-template references; for registry models the resolved version is now re-fetched through the get endpoint, so the label path hydrates these references identically to the explicit version= path.
• Added MLClient.jobs.begin_delete(name) to delete a job.
• Fixed loading a registered MLTable data asset via mltable.load("azureml://.../data/<name>/versions/<version>") failing with AttributeError: 'DataVersionEntity' object has no attribute 'additional_properties'. When the dataset_dataplane client was migrated to the TypeSpec (hybrid) model, DataVersionEntity stopped exposing the msrest additional_properties attribute that the mltable package reads (isV2 / legacyDataflow) on the local resolution path. The attribute is now restored as a compatibility shim returning the un-modeled wire keys, so the on-the-wire contract is unchanged.

Other Changes

• Migrated SDK entities and their consumers off the per-version msrest REST clients onto the shared arm_ml_service hybrid client. This is an internal change; the on-the-wire request/response contract is unchanged.

Commits

• 6d2e643 update release date (#44609)
• ca2b965 [Core] Prep release (#44590)
• fb8cbea Introduce new version of continuation token (#44574)
• 6578a78 [Core] Increment version for core release (#44398)
• a69a3c2 add example to demo how to use truststore (#44343)
• 5ade108 Bumping the targeted httpx for azure-core-experimental dev reqs (#44328)
• cbb1db6 [core] add tests and fix backcompat functions (#44084)
• 4adcc52 [Core] Support timeout error in requests+aiohttp transports (#43201)
• fd70967 [Core] Increment version for core release (#43435)
• b52527c [Core] Update TypeHandlerRegistry typing (#43393)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[oplane-bot]

Oplane Security Review

Oplane identified security requirements relevant to this PR and checked the implementation against them, finding that 1 requirement needs attention. Push changes to rerun the review, update a status with a justification if needed, or review the generated threat model.

Status	Requirement	Severity	Action
🟠 Partially implemented	Dependency Supply Chain Security for azure-core Version Upgrade OPLANE_REQ-00234065	Low	Prompt · Claude · Cursor

---

Change comment settings · Fix unresolved requirements with the Oplane MCP and your agent · Workflow guidance for AI-agents