mlflow/mlflow
Vedi su GitHub[FR] mlflow login extend backend options to azure entra ID.
Open
#16.474 aperta il 27 giu 2025
area/server-infraenhancementhelp wantedintegrations/azure
Metriche repository
- Star
- (17.127 star)
- Metriche merge PR
- (Merge medio 2g 9h) (246 PR mergiate in 30 g)
Descrizione
Willingness to contribute
No. I cannot contribute this feature at this time.
Proposal Summary
Hi All,
Thanks for the great work on MLFlow. I was eager to know whether it is possible to extend the backend options for the mlflow.login() function to include Azure Entra ID.
Motivation
What is the use case for this feature?
Why is this use case valuable to support for MLflow users in general?
Why is this use case valuable to support for your project(s) or organization?
Why is it currently difficult to achieve this use case?
Details
No response
What component(s) does this bug affect?
-
area/artifacts: Artifact stores and artifact logging -
area/build: Build and test infrastructure for MLflow -
area/deployments: MLflow Deployments client APIs, server, and third-party Deployments integrations -
area/docs: MLflow documentation pages -
area/examples: Example code -
area/model-registry: Model Registry service, APIs, and the fluent client calls for Model Registry -
area/models: MLmodel format, model serialization/deserialization, flavors -
area/projects: MLproject format, project running backends -
area/scoring: MLflow Model server, model deployment tools, Spark UDFs -
area/server-infra: MLflow Tracking server backend -
area/tracking: Tracking Service, tracking client APIs, autologging
What interface(s) does this bug affect?
-
area/uiux: Front-end, user experience, plotting, JavaScript, JavaScript dev server -
area/docker: Docker use across MLflow's components, such as MLflow Projects and MLflow Models -
area/sqlalchemy: Use of SQLAlchemy in the Tracking Service or Model Registry -
area/windows: Windows support
What language(s) does this bug affect?
-
language/r: R APIs and clients -
language/java: Java APIs and clients -
language/new: Proposals for new client languages
What integration(s) does this bug affect?
-
integrations/azure: Azure and Azure ML integrations -
integrations/sagemaker: SageMaker integrations -
integrations/databricks: Databricks integrations