This week: Microsoft Azure pros share their insights about working with Sentinel, Dedicated Host and Cloud Shell, comparisons between Event Hubs and Service Bus and more.
Comparing Event Hubs and Service Bus
Surya Venkatasubramanian, writing on the Serverless360 blog, compared Event Hubs and Service Bus. Event Hubs draws in millions of events with very high throughput and low latency. “…It allows the ‘Senders’ to pass a message with high throughput and streamlines it in the partitions,” he wrote, adding that it interoperates easily with Power BI, Azure Storage and Stream Analytics. It is particularly useful for transaction processing, telemetry, logging and data archiving.
By contrast, Service Bus is a JSON, XML and text message transfer hub with basic, standard and premium pricing tiers. According to Venkatasubramanian, Service Bus has one-to-one message queues, storing messages for a receiver to collect, as well as one-to-many topics messages. He wrote:
Event Hubs focuses more on event streaming whereas Service Bus is more focused on high-value enterprise messaging, which means the latter is focused on messages rather than events.
Getting started with Azure Sentinel
Joe Carlyle, writing on WeDoAzure, explained how to get started with Azure Sentinel. Users start by enabling Sentinel and a workspace by way of the Azure portal and then activate a data connector. Within Sentinel, Azure AD sign-in log overview is almost immediately available with built-in dashboards or the option to create custom ones. Microsoft provides sample queries on GitHub to help users set Log Analytics-style detection rules.
Sentinel enables Playbooks, based on Logic Apps, to respond to alerts. Carlyle hasn’t tried out hunting queries yet. He encouraged other users to try out Sentinel in-preview and see if it’s a good fit for their tenant.
Looking into Azure Dedicated Host
Microsoft senior cloud advocate Thomas Maurer took a look at Azure Dedicated Host, which is available in preview to run a single tenant on a physical server. It supports a variety of scenarios, such as controlling a single host without sharing with other customers or compliance-related isolations. The preview is in a pay as you go pricing model with Esv3, Dsv3 and Fsv3 VMs. The first two make up Dedicated Host Type 1, with 64 vCPUs while Fsv3 is part of the 72 vCPU Dedicated Host Type 2.
Users will need to create a new host group to house Azure VMs, configure fault domains and set up cost saving measures like Hybrid Benefit. He added, “…with the dedicated host you get unlimited virtualization rights for Windows Server and SQL Server.”
Getting license keys in Azure for SQL Server Reporting Services
On 2 Azure, Cor den Boer answered a recent question about getting SQL license keys. When using a SQL VM deployed on Azure, the key is invisible to a user because it gets deployed from Azure portal. Boer recommended logging into the VM with RDP and navigating with Windows Explorer. He found the default setup file and opened it in plain-text in Notepad. A line visible in Notepad contains the key. From there, it’s possible to run the key in the SSRS installation wizard.
Adding Azure Cloud Shell to Windows Terminal
Richard Hooper, writing on Pixel Robots, explored how to install Azure Cloud Shell for Windows Terminal. Users need to open Windows Terminal and click on Settings. A JSON file opens if Visual Studio Code is installed, and he shared code to add in for that don’t have VS Code. Back on the main page of Windows Terminal, Cloud Shell indicates as installed. Users can log in through a browser to test it and add tenants if they have multiple.