We previously announced the preview of Azure Backup reporting and gave customers the ability to generate their own reports and build customizations using Power BI. Today, we are pleased to let you know that you can leverage the same workflow to build your own Microsoft Operations Management Suite (OMS) monitoring solution for Azure Backup in the upgraded OMS workspace. The OMS monitoring solution allows you to monitor key backup parameters such as backup and restore jobs, backup alerts, and cloud storage usage across Recovery Services vaults and subscriptions. You can then utilize OMS log analytics capabilities to raise further alerts for events that you deem important for the business to be notified of. You could even open tickets through webhooks or ITSM integration using the OMS log analytics capabilities.
Here’s how you do it…
Configuring Diagnostic settings
You can open the diagnostic setting window from the Azure Recovery services vault, or you can open the diagnostic setting window by logging into Azure portal. First, click “Monitor” service followed by “Diagnostic settings” in settings section. You can then specify the relevant Subscription, Resource Group, and Recovery Services Vault. In the Diagnostic settings window, as shown below, you can select “Send data
Microsoft becomes the first hyperscale cloud provider to offer SAP HANA supportable VMs in the UK.
Azure Virtual Machines (VMs) customers can now take advantage of the Azure M/V3/B-series of VM sizes available in the UK South region. We’re also excited to announce that Azure is the first hyperscale cloud provider to offer VMs optimized for large in-memory workloads such as SAP HANA in the UK.
New Azure M series – The Azure M-series is perfectly suited for your large in-memory workloads like SAP HANA and SQL Hekaton. With the M-series, these databases can load large datasets into memory and utilize fast memory access with massive virtual CPU (vCPU) parallel processing to speed up queries and enable real-time analytics.
Learn more about M-Series.
Size vCPU’s Memory (GiB) Local SSD (GiB) Max data disks M64s 64 1024 2048 32 M64ms 64 1792 2048 32 M128s 128 2048 4096 64 M128ms 128 3800 4096 64
New Azure B series – B-series VMs provide the lowest cost option for customers with flexible vCPU requirements. These are useful for workloads like web servers, small databases, and development or test environments where CPU utilization is low most of the time, but spikes for
Today we are happy to announce performance upgrades to all paid service tiers in Azure Search. For the exact same price, these upgraded Azure Search services have roughly double the compute power of the previous hardware configuration that backed Azure Search. Additionally, services in the Standard tier began using SSD storage under the hood, compared to HDD storage used previously.
What does this mean for Azure Search?
With these service upgrades, we removed the document count limits from the Basic and Standard pricing tiers. This means that only storage limits are enforced in new Azure Search services. Depending on a scenario’s workload, these upgraded services may also benefit from faster indexing and querying performance at the same exact price points.
The Basic tier now supports an increase in the number of indexes from 5 to 15. Also in the Basic tier, Azure Search can now support up to 15 data sources and indexers per service. For the Standard 3 High Density pricing tier (great for multitenant scenarios), we were able to remove the 200 million document per partition limit, only enforcing per-index limits.
Unlimited document counts
These upgrades allow Azure Search to no longer enforce document count limits on Basic
In December we announced the release of ARM APIs for usage details. We continue that transformation to ARM APIs with this release of the Marketplace charges API for Enterprise and Web Direct customers with a few exceptions documented in the limitations and a Price Sheet API for Enterprise customers.
The updated ARM API offers the benefits of:
Migrating from a key based authorization model to ARM based authentication. Resulting in an improved security posture and the ability to utilize ARM RBAC for authorization. Adding support for Web Direct subscriptions, with a few exceptions documented below. Limitations on subscriptions
The following subscription types are currently not supported with the Marketplace Charges API:
MS-AZR-0145P MS-AZR-0 146P MS-AZR-159P MS-AZR-0036P MS-AZR-0143P MS-AZR-0015P MS-AZR-0144P Support for E-Tags
Customers who are heavy users of our APIs have requested a new data indicator. This helps them avoid polling the API and getting a full response back that has not changed since the last call. To address this request, we are releasing an updated version of the legacy usage details API that will use E-Tags to let callers know when data has been refreshed. Each call to the API will return an E-Tag, in subsequent calls to the
We are excited to announce a refresh for the Microsoft Jenkins offer in Azure Marketplace.
Like the previous version, this offer allows customers to run a Jenkins master on a Linux (Ubuntu 16.04 LTS) VM in Azure. The price is the cost of running the software components and Azure infrastructure deployed by the solution template. If you are looking to run Jenkins in the cloud, you will have full control over the Jenkins master you set up.
So why are we so excited about this refresh? Because now you can go from zero to hero. Just set up the server with the configurations you need and start building in the least amount of time.
Virtual network: We added support for VNET so that you can provision Jenkins in your own virtual network/subnet.
Azure integration: You can choose to enable Managed Service Identity (MSI) or supply an Azure Service Principal. We add the credential in Jenkins credential store automatically so that you don’t have to do this manually. Choose off if you prefer to set this up later. Build: By enabling VM agent or Azure Container Instances (ACI), you can start building your projects in Azure right away. We create the default
We heard from several customers that you need a way to view your Azure Security Center alerts in your SIEM solution for a centralized view of your security posture across your organization. Today, we are excited to announce the public preview of a new feature called SIEM Export that allows you to export Azure Security Center alerts into popular SIEM solutions such as Splunk and IBM QRadar. We are continuing to invest in the number of partners we support. This feature is part of our on-going commitment to provide unified security management and protection for your cloud and on-premises workloads.
Security Center uses a variety of detection capabilities to alert you of potential threats to your environment. The alerts can tell you what triggered the alert, what in your environment was targeted, the source of the attack, and if necessary, remediation steps. You also have the flexibility to set up custom alerts to address specific needs in your environment.
Now you can take these alerts from Security Center and integrate them into your own SIEM solutions, so you can quickly view what needs your attention from one management place and take action.
To move your Azure Security Center alerts to a
Today we’re pleased to announce three new Time Series Insights (TSI) explorer capabilities that we think our users are going to love.
First, we are delighted to share that the TSI explorer, the visualization service of TSI, is now generally available and backed by our SLA. Second, we’ve made the TSI explorer more accessible and easier to use for those with visual and fine-motor disabilities. And finally, we’ve made it easy to export aggregate event data to other analytics tools like Microsoft Excel.
Now that the TSI explorer is generally available, users will notice that the explorer is backed by TSI’s service level agreement (SLA), and we’ve removed the preview moniker from the backsplash when the explorer is loading. We have many customers using TSI in production environments and we’re thrilled to offer them the same SLA that backs the rest of the product. The ActionPoint IoT-PREDICT solution is a great example of one of those customers using the TSI explorer to enable their customers to explore and analyze time series data quickly. Check out their solution below.
There are no limits to what people can achieve when technology reflects the diversity of everyone who uses it. Transparency, accountability, and
Azure Cosmos DB provides a scalable database solution that can handle both batch and real-time ingestion and querying and enables developers to implement lambda architectures with low TCO. Lambda architectures enable efficient data processing of massive data sets. Lambda architectures use batch-processing, stream-processing, and a serving layer to minimize the latency involved in querying big data.
To implement a lambda architecture, you can use a combination of the following technologies to accelerate real-time big data analytics:
Azure Cosmos DB, the industry’s first globally distributed, multi-model database service. Apache Spark for Azure HDInsight, a processing framework that runs large-scale data analytics applications Azure Cosmos DB change feed, which streams new data to the batch layer for HDInsight to process The Spark to Azure Cosmos DB Connector
We wrote a detailed article that describes the fundamentals of a lambda architecture based on the original multi-layer design and the benefits of a “rearchitected” lambda architecture that simplifies operations.
What is a lambda architecture?
The basic principles of a lambda architecture are depicted in the figure above:
All data is pushed into both the batch layer and speed layer. The batch layer has a master dataset (immutable, append-only set of raw data)
Today, we are excited to announce the general availability of several features in Azure Stream Analytics. These features are designed to help address a variety of scenarios for both enterprise and non-enterprise customers alike. These include:
Sub-streams support: A variety of streaming applications that customers build using Azure Stream Analytics such as IoT, connected car and automotive telematics, smart elevators, etc requires processing of telemetry streams from each asset or source by itself – all in the same job without merging the timeline from events belonging to different devices or sources. This is because their clocks may be drastically out of sync. The new sub-streams support in Stream Analytics will offer this powerful new capability with very simple language constructs. A new keyword OVER is being introduced to extend the TIMESTAMP BY clause for this purpose. More details can be found at the TIMESTAMP documentation page.
Process data from different senders (toll stations) without applying time policies across different senders. The input data is partitioned based on TollId.
Egress to Azure functions: Azure Functions is a serverless compute service in Azure that helps users run their custom code triggered by events occurring in Azure or third-party services. This ability
Azure Network Watcher Connection Troubleshoot, previously in preview as Connectivity Check, is making general availability sporting a new name. Connection Troubleshoot, part of our Network Watcher suite of networking tools and capabilities, enable you to troubleshoot network performance and connectivity issues in Azure.
Continuing the expansion of tools within Azure Network Watcher, this new addition provides visualization of the hop by hop path from source to destination, identifying issues that can potentially impact your network performance and connectivity.
Network Watcher Connection Troubleshoot features
With the addition of Connection Troubleshoot, Network Watcher will see an incremental increase in its capabilities and ways for you to utilize it in your day to day operations. You can now:
Check connectivity between source (VM) and destination (VM, URI, FQDN, IP Address) Identify configuration issues that are impacting reachability Provide all possible hop by hop paths from the source to destination Hop by hop latency Latency – min, max, and average between source and destination A topology (graphical) view from your source to destination Number of packets dropped during the connection troubleshoot check
Connectivity troubleshoot check graph view output Source: Azure VM and Destination: www.bing.com.
What kind of issues can Connection Troubleshoot detect?