Preparing the Azure Machine Learning Workspace (Part 2 of 2)

By Ashwin Venugopal -

 




To read part 1, please click here




Deploying the Workspace

We can easily set up our first Azure Machine Learning workspace with the help of CLI, as follows:
  • Log in to your Azure environment via the CLI- $ az login, that will open a website with an AAD login screen, and when you return to the console, you will have some information about your AAD tenant, your subscription, as well as your user.

  • However, if you want to check which subscription is active (for more that one subscription), you can use $ az account show --output table command. 

  • Now, after being done with all that, you have to check the situation with the installed extension via $ az extension list command.

  • You should also remove the old version carefully, so that you won't break a script still in use. To do this, you can use $ az extension remove -n azure-cli-ml; or $ az extension remove -n ml commands.

  • Now, you can install the ML extension via  $ az extension add -n ml command,

  • You can look at the help page for the extension  ($ az ml -h).

  • You can also check if anything is missing for the creation of the workspace via  $ az ml workspace create -h command.

  • Now, as a resource group is required which in turn also require a location, we have to look for an available data center location for the Azure cloud with the help of  $ az account list-locations -o table command, which can be used to create the resource group.

  • Finally, if you want to check the deployment at any point, then, you can run $ az ml workspace show -g mldemo -w ml demows command.   








To read part 1, please click here




















































































Comments

Post a Comment

Popular posts from this blog

Connect Data to Azure Sentinel Using Data Connectors

By Ashwin Venugopal -
Image
  Ingest Log Data with Data Connectors You should connect your data sources with Azure Sentinel Connectors to collect the log data whose page displays a growing list of the connectors provided by Azure Sentinel, after selecting the Open connector page (the detailed connector page has a left and right blade).  The information about the connector, the connector's status, and the last time a log was received if connected is provided by the left blade. Whereas the right tab has two tabs- Instructions and Next Steps. The instructions tab can be different based on the connector having Prerequisites and Configuration which can be followed to connect to the data source. The Next Steps tab offers a quick reference to workbooks, query samples, and analytical templates. Data connectors can only be disconnected/deactivated, not deleted. Note-  The connector does not install Workbooks and Analytical Templates as they are already available in the Sentinel environment for out of the box...
Read more

Azure AI Search plugin in Microsoft Security Copilot (Preview)

By Ashwin Venugopal -
Image
  Introduction Azure AI Search is a service that allows to reliably extract content search, extract, and understand at scale. It is typically used to search for documents, data surveys, and chat-style Copilot apps over proprietary data. Indexing and querying are Azure AI Search's two main workloads. While querying allows to search the content from index, indexing loads the content into the search engine and makes it searchable. By connecting to one of the Azure AI Search indexes from within Copilot, the Microsoft Security Copilot integration for Azure enables to use the content in Copilot to produce contextualized, pertinent, and targeted responses.  Requirement Before using the Azure AI Search plugin in Copilot, the desired Azure AI Search index to connect to Copilot is configured as follows: The text field must be searchable.  The title field must be filterable. The vector-field must use text-embedding-ada-002. Integrated vectorization can be used to setup an index in t...
Read more

Information Protection Scanner: Resolve Issues with Information Protection Scanner Deployment

By Ashwin Venugopal -
Image
  About If you are experiencing problems with the Microsoft Purview Information Protection scanner, check the health of your deployment by utilizing the Start-ScannerDiagnosticsPowerShell cmdlet to start the scanner diagnostic tool. The diagnostics tool checks the following details and then creates a log files with the results: Whether the database is up to date. Whether network URLs are accessible. Whether there's a valid authentication token and policy can be acquired. Whether the profile is defined in the Azure portal. Whether offline/online configuration exists and can be acquired. Whether the rules configured are valid.  The Start-ScannerDiagnostics command does not perform a comprehensive check of prerequisites. If you encounter problems with the scanner, you need to verify that your system meets the scanner's requirements, and that your scanner's configuration and installation are finished.  Verify Scanning Details Per Scanner Node and Repository Run the Get-ScanSt...
Read more