1.8.1 (2025-09-17)

Bugs Fixed

• Fixed version pinned for opentelemetry-sdk to resolve dependency conflicts.
  (#43012)
• Modified ordering of dependencies in setup.py to avoid dependency conflicts in future.
  (#43023)

1.0.0b42 (2025-09-17)

Features Added

• Customer Facing Statsbeat: Added remaining drop codes to base
  (#42382)
• Refactored the put methods in storage.py for LocalFileBlob and LocalFileStorage
  (#42502)
• Customer Facing Statsbeat: Refactored logic for tracking dropped items from storage
  (#42542)
• Customer Facing SDKStats: Added the export interval env var for customer sdkstats
  (#42551)
• Rename Customer Statsbeat to Customer SDKStats as per [Spec] - https://github.com/aep-health-and-standards/Telemetry-Collection-Spec/pull/581
  (#42573)
• Customer Facing SDKStats: Exception categorization as per [Spec] - https://github.com/aep-health-and-standards/Telemetry-Collection-Spec/blob/main/ApplicationInsights/sdkstats/customer_facing_sdk_stats.md
  (#42695)
• Customer Facing SDKStats: Added logic for race conditions and updated the implementation to use a global instance for customer SDKStats metrics
  (#42655)
• Customer Facing SDKStats: Added telemetry_success field to dropped items as per [Spec] - https://github.com/aep-health-and-standards/Telemetry-Collection-Spec/pull/606
  (#42846)
• Customer Facing SDKStats: Refactor to use Manager and Singleton pattern
  (#42969)

Other Changes

• Configuration manager/worker fetch via OneSettings part 1 - Change detection
  ([#42360] #42360)
• Configuration manager/worker fetch via OneSettings part 2 - Concurrency and refactoring of _ConfigurationManager
  ([#42508] #42508)
• Refactoring of statsbeat to use StatsbeatManager
  ([#42716] #42716)
• Support sdk stats dynamic change on OneSettings config change
  ([#42877] #42877)

1.2.0b4 (2025-09-12)

Features Added

• Added Computer Use Preview tool for use with the computer-use-preview model
• ToolSet now supports adding multiple McpTool instances and OpenApiTool instances.
• Added static functions get_tool_resources and get_tool_definitions in azure.ai.agents.models to simplify extracting tool resources and definitions from collections of tools, making it easier to configure agents with multiple tool instances.

Bugs Fixed

• Fix issue with tracing an Agent message, when the message has "in progress" status (related to GitHub Issue 42645).
• Fix issue with tracing RunStepOpenAPIToolCall (GitHub issues 42645 and 42864).
• Fix issue when .threads.create(messages=[ThreadMessageOptions(...]) is called on the AgentsClient, when tracing is enabled (GitHub issue 42805)
• Fix an issue in the code where, when tracing is enabled and the function AgentsClient.runs.create_and_process is used, the span "start_thread_run" appears twice in trace, once as a parent and once as a child span. The parent span name has been changed to "process_thread_run". Note that the semantic conventions used in the traces (including spans and attributes) are still subject to change.

Sample updates

• Added sample demonstrating multiple McpTool instance usage.
• Added sample_agents_mcp_stream_eventhandler.py demonstrating how to use MCP tools with streaming and event handlers for real-time processing.
• Added sample_agents_mcp_stream_iteration.py showing MCP tool usage with streaming iteration for step-by-step response handling.
• Added sample_agents_multiple_mcp.py illustrating how to configure and use multiple MCP tool.

1.25.0 (2025-09-11)

Features Added

• AzureDeveloperCliCredential now supports claims in get_token and get_token_info. (#42568)
• Added new keyword argument require_envvar to DefaultAzureCredential to enforce the presence of the AZURE_TOKEN_CREDENTIALS environment variable. (#42660)

Bugs Fixed

• Fixed an issue where AzureDeveloperCliCredential would time out during token requests when azd prompts for user interaction. This issue commonly occurred in environments where the AZD_DEBUG environment variable was set, causing the Azure Developer CLI to display additional prompts that interfered with automated token acquisition. (#42535)
• Fixed an issue where credentials configured with a default tenant ID of "organizations" (such as InteractiveBrowserCredential and DeviceCodeCredential) would fail authentication when a specific tenant ID was provided in get_token or get_token_info method calls. (#42721)

Other Changes

• Updated SharedTokenCacheCredential to raise CredentialUnavailableError instead of ClientAuthenticationError during token refresh failures when within the context of DefaultAzureCredential. (#42934)

2.0.0b1 (2025-08-21)

Features Added

• Model FleetProperties added property mode
• Model FleetProperties added property capacity_type
• Model FleetProperties added property zone_allocation_policy
• Enum ManagedServiceIdentityType added member SYSTEM_ASSIGNED_USER_ASSIGNED
• Model VirtualMachineScaleSet added property name
• Added enum CapacityType
• Added enum FleetMode
• Added enum VMOperationStatus
• Added model VirtualMachine
• Added model ZoneAllocationPolicy
• Added enum ZoneDistributionStrategy
• Added model ZonePreference
• Operation group FleetsOperations added method begin_cancel
• Operation group FleetsOperations added method list_virtual_machines

Breaking Changes

• Deleted or renamed enum value ManagedServiceIdentityType.SYSTEM_AND_USER_ASSIGNED

6.0.0b1 (2025-09-11)

This version of the client library defaults to the service API version 2025-05-15-preview.

Features Added

• Added Value Exclusion, synonyms, and new entity types to the detection of Personally Identifiable Information (PII).

Breaking Changes

• Removed begin_abstract_summaryfor abstracting text summarization, added function begin_analyze_text_job with AbstractiveSummarizationOperationAction for this purpose.
• Removed begin_analyze_healthcare_entitiesfor analyzing healthcare entities, added function begin_analyze_text_job with HealthcareLROTask for this purpose.
• Removed analyze_sentimentfor analyzing sentiment, added function analyze_text with TextSentimentAnalysisInput for this purpose.
• Removed detect_languagefor detecting language, added function analyze_text with LanguageDetectionTextInput for this purpose.
• Removed extract_key_phrasesfor extracting key phrases, added function analyze_text with TextKeyPhraseExtractionInput for this purpose.
• Removed begin_multi_label_classifyfor classifying documents into multiple custom categories, added function begin_analyze_text_job with CustomMultiLabelClassificationActionContent for this purpose.
• Removed begin_recognize_custom_entitiesfor recognizing custom entities in documents, added function begin_analyze_text_job with CustomEntitiesLROTask for this purpose.
• Removed recognize_entitiesfor recognizing named entities in a batch of documents, added function analyze_text with TextEntityRecognitionInput for this purpose.
• Removed recognize_linked_entitiesfor detecting linked entities in a batch of documents, added function analyze_text with TextEntityLinkingInput for this purpose.
• Removed recognize_pii_entitiesfor recognizing personally identifiable information in a batch of documents, added function analyze_text with TextPiiEntitiesRecognitionInput for this purpose.
• Removed begin_single_label_classifyfor classifying documents into a single custom category, added function begin_analyze_text_job with CustomSingleLabelClassificationOperationAction for this purpose.

Other Changes

• Added custom poller AnalyzeTextLROPoller and AnalyzeTextAsyncLROPoller to customize the return type of begin_analyze_text_job to be AnalyzeTextLROPoller[ItemPaged["TextActions"]] and AnalyzeTextAsyncLROPoller[AsyncItemPaged["TextActions"]]

1.1.0b4 (2025-09-12)

Bugs Fixed

• Fix getting secret keys for connections of type "Custom Keys" (GitHub issue 52355)

1.35.1 (2025-09-11)

Bugs Fixed

• Fixed an issue where the retry_backoff_max parameter in RetryPolicy and AsyncRetryPolicy constructors was being ignored, causing retry operations to use default maximum backoff values instead of the user-specified limits. #42444

Other Changes

• BearerTokenCredentialPolicy and AsyncBearerTokenCredentialPolicy will now properly surface credential exceptions when handling claims challenges. Previously, exceptions from credential token requests were suppressed; now they are raised and chained with the original 401 HttpResponseError response for better debugging visibility. #42536

4.0.0b23 (2025-09-10)

Features Added

• Added operation DatabasesOperations.list_metric_definitions
• Added operation DatabasesOperations.list_metrics
• Added operation ElasticPoolsOperations.list_metric_definitions
• Added operation ElasticPoolsOperations.list_metrics
• Added operation GeoBackupPoliciesOperations.list_by_database
• Added operation group ElasticPoolActivitiesOperations
• Added operation group ElasticPoolDatabaseActivitiesOperations
• Added operation group ServerCommunicationLinksOperations
• Added operation group ServiceObjectivesOperations
• Model ManagedInstanceEditionCapability has a new parameter zone_redundant
• Model ServerUsage has a new parameter next_reset_time
• Model ServerUsage has a new parameter resource_name

Breaking Changes

• Model DataMaskingRuleListResult no longer has parameter next_link
• Model DatabaseExtensions no longer has parameter administrator_login
• Model DatabaseExtensions no longer has parameter administrator_login_password
• Model DatabaseExtensions no longer has parameter authentication_type
• Model DatabaseExtensions no longer has parameter database_edition
• Model DatabaseExtensions no longer has parameter max_size_bytes
• Model DatabaseExtensions no longer has parameter network_isolation
• Model DatabaseExtensions no longer has parameter service_objective_name
• Model DatabaseKey no longer has parameter key_version
• Model EditionCapability no longer has parameter zone_pinning
• Model ElasticPool no longer has parameter auto_pause_delay
• Model ElasticPoolEditionCapability no longer has parameter zone_pinning
• Model ElasticPoolPerDatabaseSettings no longer has parameter auto_pause_delay
• Model ElasticPoolPerformanceLevelCapability no longer has parameter supported_auto_pause_delay
• Model ElasticPoolPerformanceLevelCapability no longer has parameter supported_min_capacities
• Model ElasticPoolPerformanceLevelCapability no longer has parameter supported_per_database_auto_pause_delay
• Model ElasticPoolPerformanceLevelCapability no longer has parameter supported_zones
• Model ElasticPoolUpdate no longer has parameter auto_pause_delay
• Model EncryptionProtector no longer has parameter key_version
• Model GeoBackupPolicyListResult no longer has parameter next_link
• Model ImportExportExtensionsOperationResult no longer has parameter blob_uri
• Model ImportExportExtensionsOperationResult no longer has parameter private_endpoint_connections
• Model ImportExportExtensionsOperationResult no longer has parameter queued_time
• Model JobAgent no longer has parameter identity
• Model JobAgentUpdate no longer has parameter identity
• Model JobAgentUpdate no longer has parameter sku
• Model LocationCapabilities no longer has parameter is_zone_resilient_provisioning_allowed
• Model LocationCapabilities no longer has parameter supported_job_agent_versions
• Model LogicalDatabaseTransparentDataEncryption no longer has parameter scan_state
• Model ManagedDatabase no longer has parameter extended_accessibility_info
• Model ManagedDatabaseUpdate no longer has parameter extended_accessibility_info
• Model ManagedInstance no longer has parameter memory_size_in_gb
• Model ManagedInstance no longer has parameter requested_logical_availability_zone
• Model ManagedInstanceEditionCapability no longer has parameter is_general_purpose_v2
• Model ManagedInstanceFamilyCapability no longer has parameter zone_redundant
• Model ManagedInstanceLongTermRetentionBackup no longer has parameter backup_storage_access_tier
• Model ManagedInstanceLongTermRetentionPolicy no longer has parameter backup_storage_access_tier
• Model ManagedInstancePrivateLinkProperties no longer has parameter required_zone_names
• Model ManagedInstanceUpdate no longer has parameter memory_size_in_gb
• Model ManagedInstanceUpdate no longer has parameter requested_logical_availability_zone
• Model ManagedInstanceVcoresCapability no longer has parameter included_storage_i_ops
• Model ManagedInstanceVcoresCapability no longer has parameter included_storage_throughput_m_bps
• Model ManagedInstanceVcoresCapability no longer has parameter iops_included_value_override_factor_per_selected_storage_gb
• Model ManagedInstanceVcoresCapability no longer has parameter iops_min_value_override_factor_per_selected_storage_gb
• Model ManagedInstanceVcoresCapability no longer has parameter supported_memory_sizes_in_gb
• Model ManagedInstanceVcoresCapability no longer has parameter supported_storage_i_ops
• Model ManagedInstanceVcoresCapability no longer has parameter supported_storage_throughput_m_bps
• Model ManagedInstanceVcoresCapability no longer has parameter throughput_m_bps_included_value_override_factor_per_selected_storage_gb
• Model ManagedInstanceVcoresCapability no longer has parameter throughput_m_bps_min_value_override_factor_per_selected_storage_gb
• Model SensitivityLabel no longer has parameter client_classification_source
• Model ServerKey no longer has parameter key_version
• Model ServerUsage no longer has parameter id
• Model ServerUsage no longer has parameter type
• Model ServerUsageListResult no longer has parameter next_link
• Model ServiceObjectiveCapability no longer has parameter supported_free_limit_exhaustion_behaviors
• Model ServiceObjectiveCapability no longer has parameter supported_zones
• Model ServiceObjectiveCapability no longer has parameter zone_pinning
• Operation DataMaskingPoliciesOperations.create_or_update no longer has parameter data_masking_policy_name
• Operation DataMaskingPoliciesOperations.get no longer has parameter data_masking_policy_name
• Operation DataMaskingRulesOperations.create_or_update no longer has parameter data_masking_policy_name
• Operation DataMaskingRulesOperations.list_by_database no longer has parameter data_masking_policy_name
• Operation LongTermRetentionManagedInstanceBackupsOperations.list_by_location no longer has parameter filter
• Operation LongTermRetentionManagedInstanceBackupsOperations.list_by_location no longer has parameter skip
• Operation LongTermRetentionManagedInstanceBackupsOperations.list_by_location no longer has parameter top
• Operation LongTermRetentionManagedInstanceBackupsOperations.list_by_resource_group_location no longer has parameter filter
• Operation LongTermRetentionManagedInstanceBackupsOperations.list_by_resource_group_location no longer has parameter skip
• Operation LongTermRetentionManagedInstanceBackupsOperations.list_by_resource_group_location no longer has parameter top
• Operation OutboundFirewallRulesOperations.begin_create_or_update has a new required parameter parameters
• Parameter administrator_login_password of model ExportDatabaseDefinition is now required
• Parameter administrator_login_password of model ImportExistingDatabaseDefinition is now required
• Parameter credential of model JobStepOutput is now required
• Parameter state of model GeoBackupPolicy is now required
• Parameter value of model ServerUsageListResult is now required
• Removed operation GeoBackupPoliciesOperations.list
• Removed operation ManagedDatabaseSensitivityLabelsOperations.list_by_database
• Removed operation ManagedDatabasesOperations.begin_reevaluate_inaccessible_database_state
• Removed operation ManagedInstanceLongTermRetentionPoliciesOperations.begin_delete
• Removed operation ManagedInstancesOperations.begin_reevaluate_inaccessible_database_state
• Removed operation ManagedInstancesOperations.begin_validate_azure_key_vault_encryption_key
• Removed operation SensitivityLabelsOperations.list_by_database
• Removed operation TransparentDataEncryptionsOperations.begin_resume
• Removed operation TransparentDataEncryptionsOperations.begin_suspend
• Removed operation VirtualClustersOperations.begin_create_or_update
• Removed operation group InstancePoolOperationsOperations
• Removed operation group NetworkSecurityPerimeterConfigurationsOperations

4.14.0b4 (2025-09-11)

Bugs Fixed

• Fixed bug where client provided session token was not respected when client-side session management was disabled. See PR 42965