<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="https://www.w3.org/2005/Atom" xmlns:sy="https://purl.org/rss/1.0/modules/syndication/" xmlns:dc="https://purl.org/dc/elements/1.1/" xmlns:content="https://purl.org/rss/1.0/modules/content/" xmlns:wfw="https://wellformedweb.org/CommentAPI/" xmlns:slash="https://purl.org/rss/1.0/modules/slash/"
  version="2.0">
  <channel>
    <title>Microsoft Azure Machine Learning  support team blog</title>
    <atom:link
      href="https://docs.microsoft.com/archive/blogs/azuremlsupport/feed.xml"
      rel="self"
      type="application/rss+xml" />
    <link>https://docs.microsoft.com/archive/blogs/azuremlsupport/feed.xml</link>
    <description />
    <lastBuildDate>Wed, 17 Apr 2019 03:24:14 GMT</lastBuildDate>
    <language>en-US</language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <item>
      <title>ML workspace creation fails with error: "The location constraint is not valid"</title>
      <link>https://docs.microsoft.com/archive/blogs/azuremlsupport/ml-workspace-creation-fails-with-error-the-location-constraint-is-not-valid</link>
      <pubDate>Tue, 12 Jan 2016 01:12:03 GMT</pubDate>
      <dc:creator><![CDATA[Gert Christen - MSFT]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.technet.microsoft.com/azuremlsupport/2016/01/12/ml-workspace-creation-fails-with-error-the-location-constraint-is-not-valid/</guid>
      <description><![CDATA[As of today the Azure machine learning service is offered in three locations around the world:...]]></description>
      <content:encoded><![CDATA[<p> <p>As of today the Azure machine learning service is offered in three locations around the world: <p>South Central US, <p>West Europe,  <p>Southeast Asia</p> <p><a href="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/03/28/aml_location.png" original-url="https://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-03-28/aml_5F00_location.png"><img border="0" alt=" " src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/03/28/aml_location.png" original-url="https://blogs.technet.com/resized-image.ashx/__size/550x0/__key/communityserver-blogs-components-weblogfiles/00-00-01-03-28/aml_5F00_location.png" /></a> <p>When you create a ML workspace, it will need access to an Azure storage account in the same location. If you do not supply an existing storage account, then it will try to create one on the fly. <p>In case your Azure subscription does not have access to the chosen ML workspace location, then the storage account (and subsequently the ML workspace) creation will fail with the error: &quot;<strong>The location constraint is not valid</strong>&quot;. <p>You can test which locations your Azure subscription has access to by looking at the create new storage account template. It will list all locations that your subscription has currently access to: <p><a href="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/03/28/storage_location.png" original-url="https://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-01-03-28/storage_5F00_location.png"><img border="0" alt=" " src="https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/01/03/28/storage_location.png" original-url="https://blogs.technet.com/resized-image.ashx/__size/550x0/__key/communityserver-blogs-components-weblogfiles/00-00-01-03-28/storage_5F00_location.png" /></a> <p>Note that in above screenshot I have access to 7 locations that include all three AML locations: South Central US, West Europe, Southeast Asia. Thus I can create ML workspaces in all three locations and won’t see the issue. <p>The same may not be true for your subscription. Many Azure subscriptions may by default just have access to 4 locations. And these may not include your desired ML workspace location. <p>If you find that you cannot create an ML workspace in your chosen location because your Azure subscription has no access to it, then you will need to open a support ticket and ask for the desired locations being added to the Azure subscription. When opening the ticket please make sure that you guide it towards Azure subscription management. <p>Do you just want to do quick testing of the Azure machine learning service? Then we have another solution for you. Under the URL: <a title="https://studio.azureml.net/" href="https://studio.azureml.net/">https://studio.azureml.net/</a>&nbsp; you can create a free workspace that does not require any Azure subscription.&nbsp; </p></p></p></p></p></p></p></p></p></p></p></p></p>]]></content:encoded>
    </item>
    <item>
      <title>“User is not authorized to access this workspace” error and Workaround</title>
      <link>https://docs.microsoft.com/archive/blogs/azuremlsupport/user-is-not-authorized-to-access-this-workspace-error-and-workaround</link>
      <pubDate>Tue, 08 Sep 2015 15:24:47 GMT</pubDate>
      <dc:creator><![CDATA[lisa liu]]></dc:creator>
      <guid
        isPermaLink="false">https://blogs.technet.microsoft.com/azuremlsupport/2015/09/08/user-is-not-authorized-to-access-this-workspace-error-and-workaround/</guid>
      <description><![CDATA[Azure Machine Learning (ML) Service has recently enabled the support of Azure Active Directory...]]></description>
      <content:encoded><![CDATA[<p>Azure Machine Learning (ML) Service has recently enabled the support of Azure Active Directory accounts. This change may impact the Azure ML Workspace created prior to the change, and the Workspace has one or more owner or user account using a corporate email address. Those users may lose access to the Workspace. The following error message will be returned when the user tries to connect to the Workspace from Azure Management Portal, even though the Workspace is listed there under Machine Learning with status of online.
</p><blockquote><p>User:xxxxx@corporatedomain.com
</p></blockquote><blockquote><p>Workspace ID:xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
</p></blockquote><blockquote><p>The Signed-on user is not authorized to access this workspace. Please try to sign out and re-sign on with an authorized user account. 
</p></blockquote><p>If the user goes to <a href="https://studio.azureml.net">https://studio.azureml.net</a> directly, and sign in using his or her corporate email address, the Workspace is no longer in the Workspace list on the Studio site.
</p><p>To regain access to the Workspace for these impacted users, please take the following steps 
</p><ol><li>Go to Azure Management Portal, change the workspace owner from the corporate email address to a valid live.com or Hotmail.com account
</li><li>Launch InPrivate browser, go to <a href="https://studio.azureml.net">https://studio.azureml.net</a>
		</li><li>Log in with the live.com or Hotmail.com account
</li><li><div>Invite the corporate email address from the Azure ML Workspace as User or Owner as appropriate
</div><p><img alt=" " />
			</p></li></ol>]]></content:encoded>
    </item>
  </channel>
</rss>