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

By Ashwin Venugopal -

 





To read part 2, please click here




Deploying an Azure Machine Learning Workspace

Firstly, we will require an Azure subscription so that you can log-in to the Azure portal with your identity and with the knowledge of the Azure subscription to which you would like to deploy your ML services.

Now, if you want to use your work account, then, you will have to go to porta.azure.com in order to log-in. If it works, then, this means that your company has already set up an Azure AD instance. After this, you can talk to your Azure Global Administrator to discuss about the Azure subscription to use for your purpose.

However, if you want to use your private account, then, go to azure.com and click on Free Account to create an Azure AD for yourself with a free trial subscription containing a certain amount of money to spend within 30 days on Azure services.

Understanding the Available Tooling for Azure Deployments

In Azure, any action that deploys or change an Azure service goes through ARM (Azure Resource Manager) which accepts requests either from the Azure portal, Azure PowerShell, the Azure CLI, or the Azure REST API. Some of them are explained below:

  • Azure CLI- This fully-fledged command-line environment can be installed in any major operating system and its latest version can be downloaded from https://docs.microsoft.com/en-us/cli/azure/ install-azure-cli.

  • Azure PowerShell- It's a library of PowerShell modules that can be added to a PowerShell environment and the new PowerShell Core 7.x can also support all the major Linux releases and macOS (before this, it was only available on Windows).

  • Azure REST API- This one is available to call ARM through REST, allowing you to manage Azure resources via curl or the popular Python requests library. 

All the above above options not only allow the use of so-called ARM templates, Azures version of Infrastructure as Code (IaC); but also offers you the ability to save as well as version-control the infrastructure definitions in files which is highly recommended while dealing with the complex ones.  









To read part 2, please click here







































































































Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different groups of computers, re
Read more

Project Resourcing (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here Engineering - SIEM The SIEM engineers configures Microsoft Sentinel, including Log Analytics, Logic Apps, workbooks, and playbooks. They are also responsible for the following high-level tasks: Initial configuration of Azure tenant, including provisioning required resources, assigning access roles, and configuring workspace parameters like log retention, resource tagging, and blueprints.  Deployment and configuration of syslog/CEF log collection agents in appropriate locations to collect logs from on-premises devices. Generally, it will be joint effort of both system engineer and SIEM engineer, involving configuration and potential troubleshooting.  Working with system owners to enable log forwarding and configuring any required parsing of log data in Log Analytics.  Working with security operations to create and deploy KQL analytic rules to offer detections for SOC/Computer Security Incident Response Team (CSRIT) use. Tuning of alert rule parameter
Read more

Design Planning (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Complex Organizational Structures SIEM can be an expensive security control, hence, it is common multiple businesses to contribute to the overall expense. Various organizational units may require a level of access to specific dashboards or sets of data. Microsoft Sentinel offers the ability to assign table-level permissions and limit the level of access to the minimum required to perform requisite job functions.  Role-based Access Control (RBAC) Requirements Microsoft Sentinel offers an extensive list of Azure built-in roles that can be used to provide granular access according to the job requirements and permitted level of access. Some of them are various Microsoft Sentinel dedicated roles: Microsoft Sentinel Contributor- Can perform all engineering-related configuration, such as creating alert rules, configuring data connectors, and additional similar tasks.  Microsoft Sentinel Reader- Can query the log data stor
Read more