Search results

KeyVault parameter in Workspace properties is required in API but not spec

ADOIssue is documented on MSFT ADO for internal trackingIssue is documented on MSFT ADO for internal tracking

bugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.

customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.

Machine Learning

ML-Workspace ManagementAreaPathAreaPath

questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Service AttentionWorkflow: This issue is responsible by Azure service team.Workflow: This issue is responsible by Azure service team.

Status: Open.

#15878 In Azure/azure-rest-api-specs;

· pierskarsenbarg opened on Sep 1, 2021

MachineLearningServices - Skus should have possible values defined in enum and <code>x-ms-enum</code>

ADOIssue is documented on MSFT ADO for internal trackingIssue is documented on MSFT ADO for internal tracking

feature-requestThis issue requires a new behavior in the product in order be resolved.This issue requires a new behavior in the product in order be resolved.

Machine Learning

ML-Workspace ManagementAreaPathAreaPath

Service AttentionWorkflow: This issue is responsible by Azure service team.Workflow: This issue is responsible by Azure service team.

Status: Open.

#13546 In Azure/azure-rest-api-specs;

· ArcturusZhang opened on Mar 22, 2021

<code>Microsoft.MachineLearningServices</code> associated resource IDs in workspace are not preserving proper casing

ADOIssue is documented on MSFT ADO for internal trackingIssue is documented on MSFT ADO for internal tracking

Machine Learning

ML-Workspace ManagementAreaPathAreaPath

Service AttentionWorkflow: This issue is responsible by Azure service team.Workflow: This issue is responsible by Azure service team.

Status: Open.

#8323 In Azure/azure-rest-api-specs;

· ArcturusZhang opened on Feb 6, 2020

MachineLearningService Workspaces_CreateOrUpdate returns 202 but the <code>responses</code> field only defines status code <code>200</code> and <code>201</code> as succeed

ADOIssue is documented on MSFT ADO for internal trackingIssue is documented on MSFT ADO for internal tracking

Machine Learning

MgmtThis issue is related to a management-plane library.This issue is related to a management-plane library.

ML-Workspace ManagementAreaPathAreaPath

questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Service AttentionWorkflow: This issue is responsible by Azure service team.Workflow: This issue is responsible by Azure service team.

Status: Open.

#8029 In Azure/azure-rest-api-specs;

· ArcturusZhang opened on Dec 25, 2019

MachineLearningService Workspaces_CreateOrUpdate is not long-running-operation but the rest api will return 202 with async polling URL

ADOIssue is documented on MSFT ADO for internal trackingIssue is documented on MSFT ADO for internal tracking

Machine Learning

MgmtThis issue is related to a management-plane library.This issue is related to a management-plane library.

ML-Workspace ManagementAreaPathAreaPath

Service AttentionWorkflow: This issue is responsible by Azure service team.Workflow: This issue is responsible by Azure service team.

Status: Open.

#8028 In Azure/azure-rest-api-specs;

· ArcturusZhang opened on Dec 24, 2019