Category Archives : Updates

05

Jul

Lessons from big box retail
Lessons from big box retail

How can retail banks generate curated experiences? Learn from retailers. They use a cloud platform that orchestrates experiences from omni-channels to devices using data collected from various touchpoints. The data is combined and analyzed with Microsoft Azure Machine Learning technology. With these technologies, retailers can now understand the shopping behavior of a customer and offer them products that that are most relevant. Retailers deliver engaging in-store experiences by digitizing the store to deliver a curated experience to the shopper at every point in their shopping journey.


Figure above: Retail Bank branch shown as the hub for digital curated experiences

Imagine this: banks that provide financial “fitting rooms” where customers can “try on” products and services before they commit. That gives the customer the ability to experiment with the recommendations that fit their holistic life, not just their financial life. That feels a lot more personal and custom fitted to me.

Convergence! Wasn’t there a movie with that title? No, sorry, that was actually Divergent. Exciting sci-fi thriller where people are divided based on virtues, but that’s going in the wrong direction for this topic. So, what’s converging? Retail experiences are giving customers new expectations about banking.

Consumer expectations are being

Share

05

Jul

Microsoft Azure launches tamper-proof Azure Immutable Blob Storage for financial services

I’m pleased to announce that Azure Immutable Blob Storage is now in public preview – enabling financial institutions to store and retain data in a non-erasable and non-rewritable format – and at no additional cost. Azure Immutable Blob Storage meets the relevant storage requirements of three key financial industry regulations: the CFTC Rule 1.31(c)-(d), FINRA Rule 4511, and SEC Rule 17a-4. Financial services customers, representing one of the most heavily regulated industries in the world, are subject to complex requirements like the retention of financial transactions and related communication in a non-erasable and non-modifiable state. These strict requirements help to provide effective legal and forensic surveillance of market conduct.

Software providers and partners can now rely on Azure as a one-stop shop cloud solution for records retention and immutable storage with sensitive workloads. Financial institutions can now easily build their own applications taking advantage of these features while remaining compliant. These Write Once Read Many (WORM) policies apply to all tiers of storage (hot, cool, and archive). This industry leading compliance storage offering is now available at no additional cost on top of the base pricing of Azure storage!

To document compliance, Microsoft retained a leading independent assessment firm that

Share

05

Jul

Microsoft Azure launches tamper-proof Azure Immutable Blob Storage for financial services

I’m pleased to announce that Azure Immutable Blob Storage is now in public preview – enabling financial institutions to store and retain data in a non-erasable and non-rewritable format – and at no additional cost. Azure Immutable Blob Storage meets the relevant storage requirements of three key financial industry regulations: the CFTC Rule 1.31(c)-(d), FINRA Rule 4511, and SEC Rule 17a-4. Financial services customers, representing one of the most heavily regulated industries in the world, are subject to complex requirements like the retention of financial transactions and related communication in a non-erasable and non-modifiable state. These strict requirements help to provide effective legal and forensic surveillance of market conduct.

Software providers and partners can now rely on Azure as a one-stop shop cloud solution for records retention and immutable storage with sensitive workloads. Financial institutions can now easily build their own applications taking advantage of these features while remaining compliant. These Write Once Read Many (WORM) policies apply to all tiers of storage (hot, cool, and archive). This industry leading compliance storage offering is now available at no additional cost on top of the base pricing of Azure storage!

To document compliance, Microsoft retained a leading independent assessment firm that

Share

03

Jul

IP filtering for Event Hubs and Service Bus

For scenarios in which Azure Event Hubs or Azure Service Bus is only accessible from certain well-known sites, the IP Filter feature enables you to configure rules for accepting or rejecting traffic originated from specify IP addresses, for instance the addresses that come under corporate NAT gateway. The Azure team is happy to announce the public preview of IP Filtering for Service Bus Premium and Event Hubs Standard and Dedicated price plans.

This feature allows users to control which IPs are accessing their resources. Some characteristics of this feature:

Rules allow you to specify accept and reject actions on IP masks. The rules work with IPv4 addresses. Rules are applied to the namespace level. You can have multiple rules and they are applied in order. The first rule that matches the IP address determines the accept or reject action. Requests from IPs that are rejected receive an unauthorized response.

Today these features are available in the Azure portal as shown in the screenshot. You can find them at the Event Hubs or Service Bus namespace level or via an ARM template.

The below ARM template shows how you can use this feature. This template takes the following parameters:

ipFilterRuleName

Share

03

Jul

IP filtering for Event Hubs and Service Bus

For scenarios in which Azure Event Hubs or Azure Service Bus is only accessible from certain well-known sites, the IP Filter feature enables you to configure rules for accepting or rejecting traffic originated from specify IP addresses, for instance the addresses that come under corporate NAT gateway. The Azure team is happy to announce the public preview of IP Filtering for Service Bus Premium and Event Hubs Standard and Dedicated price plans.

This feature allows users to control which IPs are accessing their resources. Some characteristics of this feature:

Rules allow you to specify accept and reject actions on IP masks. The rules work with IPv4 addresses. Rules are applied to the namespace level. You can have multiple rules and they are applied in order. The first rule that matches the IP address determines the accept or reject action. Requests from IPs that are rejected receive an unauthorized response.

Today these features are available in the Azure portal as shown in the screenshot. You can find them at the Event Hubs or Service Bus namespace level or via an ARM template.

The below ARM template shows how you can use this feature. This template takes the following parameters:

ipFilterRuleName

Share

02

Jul

Agile SAP development with SAP Cloud Platform on Azure

This blog post was co-authored by Mario Szpuszta, Principal Software Engineer, Azure CAT

Recently we announced that SAP Cloud Platform is transitioning from Beta to general availability on Azure. SAP Cloud Platform (SAP CP) is SAP’s multi-cloud platform-as-a-service offering and is now available for production use in Azure West Europe.

With SAP CP on Azure, we extend the choices available on Azure to meet your SAP development needs.  SAP CP offers a fully managed platform-as-a-service, operated by SAP, and is the first multi-tenant and fully managed Cloud Foundry PaaS on Azure. With SAP CP running on Azure, customers can

Leverage a broad range of certified SAP HANA offerings on Azure. Integrate with Azure-Native Services such as EventHubs, AzureSQL Database, Azure CosmosDB, Azure ServiceBus etc., using Meta Azure Service Broker. Integrate with Azure Active Directory to enable Single-Sign-On for SAP Cloud Platform SAP Cloud Platform on Azure – Getting started

To get started with SAP CP on Azure, login to your SAP CP account. Pick Cloud Foundry and select Europe (Netherlands) Azure region. This will create an Organization and Space within the SAP CP Cloud Foundry environment.

Deploying applications and services

Developers can use either the SAP CP cockpit

Share

02

Jul

Monitor Azure Data Factory pipelines using Operations Management Suite

Data Integration solutions can be complex with many moving parts involving complex data factories with multiple pipelines. Monitoring provides data to ensure that your data factory pipelines stay up and running in a healthy state. It also helps you to stave off potential problems or troubleshoot past ones. In addition, you can use monitoring data to gain deep insights about your application. This knowledge can help you to improve application performance or maintainability, or automate actions that would otherwise require manual intervention.

Azure Data Factory (ADF) integration with Azure Monitor allows you to route your data factory metrics to Operations and Management (OMS) Suite. Now, you can monitor the health of your data factory pipelines using ‘Azure Data Factory Analytics’ OMS service pack available in Azure marketplace.

Azure Data Factory OMS pack provides you a summary of overall health of your Data Factory, with options to drill into details and to troubleshoot unexpected behavior patterns. With rich, out of the box views you can get insights into key processing including:

At a glance summary of data factory pipeline, activity and trigger runs Ability to drill into data factory activity runs by type Summary of data factory top pipeline,

Share

25

Jun

Healthcare on 5G
Healthcare on 5G

Today many healthcare computational workloads still exist at or near the point of care because of high latency, low bandwidth, or challenges with wireless power requirements and limited battery capabilities. Limitations on the numbers of connections per cell are also poised to stunt the future growth of IoT (Internet of Things).

4G LTE has typical latencies of 50-100ms, bandwidth less than 50Mbps, and in the range of thousands of connections per cell (maximum). This has forced users to spend capital buying expensive, powerful hardware to be co-located at or close to the point of need, and to secure and maintain that hardware over its lifetime. In the case of IoT and wearables these limitations have either prevented certain use cases or significantly limited capabilities.

5G has a latency of less than 1ms, bandwidth of up to 10 Gbps, and up to a million connections per square KM! This is going to pave the way for many new innovations in healthcare. I discuss a few of these below.

Healthcare AR / VR from the Cloud

Microsoft HoloLens today enables MR (Mixed Reality) in healthcare. The AR (Augmented Reality), VR (Virtual Reality) in healthcare market was recently valued at USD $769 million

Share

21

Jun

Cost Reporting ARM APIs across subscriptions for EA customers

Azure enterprise customers today manage their subscriptions on the EA portal and use the EA hierarchy to group and report on usage and costs by subscription. Until today, the only APIs available for the enterprise hierarchy was the key based APIs, this month we are releasing ARM supported APIs for the enrollment hierarchy. This will enable users with the required privileges to make API calls to the individual nodes in the management hierarchy and get the most current cost and usage information.

The benefits of this API is an improved security posture, seamless onboarding to the cost APIs and benefiting from the continued investment in planned work on the APM APIs, like budgets. Departments today support rudimentary spending limits, but in the coming weeks we will be supporting budgets, that were recently announced for subscriptions and resource groups on EA hierarchy nodes as well. The ARM APIs also standardize the pattern and enable AD based authentication.

Hierarchy Updates

As part of this release the ARM API introduces a few new terms:

Enrollments in the ARM APIs are Billing Accounts Departments continue on as Departments Accounts in the ARM APIs are referred to as Enrollment Accounts

This release of ARM APIs

Share

21

Jun

Cost Reporting ARM APIs across subscriptions for EA customers

Azure enterprise customers today manage their subscriptions on the EA portal and use the EA hierarchy to group and report on usage and costs by subscription. Until today, the only APIs available for the enterprise hierarchy was the key based APIs, this month we are releasing ARM supported APIs for the enrollment hierarchy. This will enable users with the required privileges to make API calls to the individual nodes in the management hierarchy and get the most current cost and usage information.

The benefits of this API is an improved security posture, seamless onboarding to the cost APIs and benefiting from the continued investment in planned work on the APM APIs, like budgets. Departments today support rudimentary spending limits, but in the coming weeks we will be supporting budgets, that were recently announced for subscriptions and resource groups on EA hierarchy nodes as well. The ARM APIs also standardize the pattern and enable AD based authentication.

Hierarchy Updates

As part of this release the ARM API introduces a few new terms:

Enrollments in the ARM APIs are Billing Accounts Departments continue on as Departments Accounts in the ARM APIs are referred to as Enrollment Accounts

This release of ARM APIs

Share