I suggest you ...

Prevent Creation of Classic Machine Learning Web Services so Tags can be Enforced

Prevent Creation of Legacy Machine Learning Workspace Commitment Plans and classic web services so Tags can be Enforced.

Our organization sets a Tag policy on resource groups so that newly created resources within that resource group will inherit tags. The main tag is 'Department Code', and is used for Chargeback for resource usage. Any Machine Learning 'classic' web services, that were created using the Machine Learning Studio portal will be created outside of the standard tagged resource group and thus, will not inherit standard tags used for Chargeback.

We also need a migration method for existing classic web services to be migrated to ARM web services, which is currently not supported by Microsoft. We will need to delete deployed instances from classic web services and deploy web services instead of classic web service from ML studio, and this has to be done one experiment at a time.

37 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Stephanie shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base