The `azure-mgmt-scheduler` library is the Microsoft Azure Scheduler Management Client Library for Python. It provides programmatic access to manage Azure Scheduler resources. While the library's current version is 7.0.0, the underlying Azure Scheduler service has been retired by Microsoft. This package received security fixes until January 31, 2022, and is no longer actively maintained for new features or non-security bug fixes.
pip install azure-mgmt-schedulerVerified import paths — ran on the pinned version, not inferred.
This quickstart demonstrates how to instantiate the `SchedulerManagementClient` using `azure.identity.DefaultAzureCredential`. It's crucial to note that the Azure Scheduler service has been retired, so most operations will fail. This example serves primarily to show the client initialization pattern.
Migrate existing schedules to Azure Logic Apps, which is the recommended replacement. Use the `azure-mgmt-logic` library for programmatic management of Logic Apps.
Update your authentication code to use classes like `DefaultAzureCredential` from `azure.identity`. Pass the credential object directly to the client constructor, e.g., `SchedulerManagementClient(credential, subscription_id)`.
Do not use this library for active schedule management. For any lingering archival or diagnostic needs, be prepared for consistent API failures.
Update code to use `begin_` prefixed methods for long-running operations and handle `azure.core.exceptions.HttpResponseError` for general API errors. Adjust polling logic as per `azure.core` patterns.
Migrate your scheduling logic to Azure Logic Apps, which is the recommended replacement service. Do not use `azure-mgmt-scheduler` for active schedule management.
Update your authentication code to use classes like `DefaultAzureCredential` from `azure.identity`. Pass the credential object directly using the `credential` parameter: `SchedulerManagementClient(credential, subscription_id)`.
Install the package using pip: `pip install azure-mgmt-scheduler` or ensure your virtual environment is activated and correctly configured.
While the service is retired, if attempting to access historical information (which may still fail), ensure you are on `azure-mgmt-scheduler` version 7.0.0 and refer to the latest SDK documentation for the correct client methods and properties, if any are still functional for diagnostic purposes. For active scheduling, migrate to Azure Logic Apps and use `azure-mgmt-logic`.