This article is contributed. See the original author and article here.
Healthcare and Life Sciences (HLS) is a demanding and complex field that requires constant innovation, collaboration, and communication. HLS professionals often have to deal with large amounts of data, information, and documentation, which can be overwhelming and time-consuming. Moreover, the COVID-19 pandemic has added more pressure and stress to the already challenging work environment, leading to increased risks of burnout and mental fatigue.
How can HLS professionals cope with these challenges and improve their productivity and well-being? One possible solution is to leverage the power of AI and use Copilot, a tool that helps you write better code faster. Copilot is a smart assistant that can assist with email overload, summarize information from various sources, generate documentation, and more. Copilot also integrates with other applications like Teams, Word, Outlook, and more, creating a seamless workflow that can enhance your efficiency and creativity.
Check out the ever-growing repository of Use case workflow leveraging the power of Copilot.
* Note: all examples are demonstrations for educational purposes only and not intended to be used as production. No warranty or support is stated or implied.
This article is contributed. See the original author and article here.
Last updated 4/3/2024 to include v2 Tiers features.
Authors: Faisal Mustafa, Ben Gimblett, Jose Moreno, Srini Padala, and Fernando Mejia.
There are different options when it comes to integrating your API Management with your Azure Virtual Network (VNet) which are important to understand. These options will depend on your network perimeter access requirements and the available tiers and features in Azure API Management.
This blog post aims to guide you through the different options available on both the classic tiers and v2 tiers of Azure API Management, to help you decide which choice works best for your requirements.
TL; DR
Decision tree describing how to choose the right Azure API Management tier based on networking scenarios.
Here is the relevant documentation to implement these tiers and features:
Before we jump into the options and differences it’s worth taking a step back to understand more about how Azure Platform as a Service products (PaaS) work regarding networking. If you need a refresher and so we don’t repeat ourselves here, we’d ask the reader to spend a few minutes over at Jose’s excellent “Cloudtrooper blog” and his deep dive post on all things “PaaS networking”. We’ll use some of the same labels and terms in this post for consistency Taxonomy of Azure PaaS service access – Cloudtrooper.
What is API Management, what tiers are available and why does it matter in relation to networking?
The first thing to remember is that the API Management API Gateway is a Layer 7 (in OSI model terms) HTTP Proxy. Keeping this in mind helps a lot when you think about the networking options available through the different tiers. In simple terms:
An HTTP proxy terminates HTTP connections from any client going to a set of [backend] servers and establishes new HTTP connections to those servers. For most API Management Gateway use cases the resource would reside close to the [backend] servers its facades (usually in the same Azure region).
Diagram describing all the components included in Azure API Management, and the difference between inbound and outbound sections.
Why does this matter? When we talk about the available networking-options we talk about features which relate to the initial client connection to API Management(inbound) OR features relating to the connection from API Management to the API backends(outbound). From now on, we will call them inbound and outbound connections, and there are different options/features for each type.
Regarding Azure API Management tiers we will rely in the following categories:
Consumption tier, the tier that exposes serverless properties.
Classic tiers, this category refers to the Developer, Basic, Standard and Premium tiers.
V2 tiers, this category refers to the Basic v2 and Standard v2.
Networking scenarios
Let’s jump right in. To make it easier to navigate and for you to get the information you need to make the right decisions for your use case, lets summarize by the applicable use-cases, we’ll list the tiers where the functionality is available and add any applicable notes.
I have no specific networking requirements and just want to keep things simple.
Supported tiers: Consumption, Classic tiers, and V2 tiers.
Of course, there’s more to implementing a workload with API Management than just networking features and still a lot of choice when it comes to an API Management tier that fits your workload and scale requirements. But if you are ok with having inbound and outbound connections going through the Azure Backbone or Public Internet, any tier of Azure API Management can help you with this scenario. Of course, we recommend securing your endpoints using Authentication/Authorization mechanisms like subscription keys, certificates, and Oauth2/OIDC.
Diagram describing what tiers of Azure API Management allow public access for inbound and outbound.
I have a requirement to connect privately to API Management for one or more of my Client Applications
Option 1: Consider deploying a Private Endpoint into API Management.
Supported tiers: Classic tiers.
“Private endpoints allow you to access services privately within your virtual network, avoiding exposure over the public internet.” (Thanks Microsoft co-pilot).
Deploying a Private Endpoint for inbound connectivity is a good option to support secure client connections into API Management. Remember, in this context the Private Endpoint you deploy for API Management creates an alternative network path into your API MANAGEMENT service instance; it’s about facilitating inbound communication (the client connecting to API Management), and it is “one way only” meaning it doesn’t help for scenarios where you also want to connect privately to your backends.
Diagram describing what tiers of Azure API Management allow public access and private endpoint for inbound.
Note: Whilst it’s supported to use Private Endpoints in the Premium or Developer tiers – the service must not have been added to a Virtual Network (VNET). This makes private endpoints and the “VNET Injection” capability supported by Premium and Developer mutually exclusive. The Basic and Standard tiers can’t be added to a Virtual Network.
Option 2: Consider adding your API Management to your VNet.
Supported tiers: Developer tier and Premium tier.
Developer and Premium are the only tiers where you can deploy the service into your virtual network – what we sometimes refer to as “VNet injection” – and allows you to set the inbound as public or private.
Diagram describing what tiers of Azure API Management allow private access for both inbound and outbound.
As far as the Developer Tier is concerned, this is NOT meant for production use and no workloads showed be deployed on this Developer Tier.
The API backends I want to reach from API Management are private.
Supported tiers: Developer tier, Premium tier, and Standard v2 tier.
For the classic tiers Developer and Premium, as we mentioned before you can deploy the service into your virtual network. This could be in “internal” (private) or external mode.
Diagram describing what tiers of Azure API Management allow private access for both inbound and outbound.
For the v2 tiers, Standard v2, allows you to rely on a feature called “VNet Integration” (please not the difference between VNet Integration and VNet injection) which allows API Management to “see” into your network and access services through a private IP in the connected Virtual Network, or in peered / connected network(s).
Diagram describing what tiers of Azure API Management allow private access for outbound using VNet integration.
I need to connect to API Management privately as well as reach private backends with no public access.
Supported tiers: Developer tier and Premium tier.
Add API Management Premium or Developer to your Virtual Network. The best practice would be to set the mode to “internal” – meaning inbound connectivity is via a private IP, via an internal load balancer.
Diagram describing what tiers of Azure API Management allow private access for both inbound and outbound.
It’s something that relates to networking and is oft asked, so it would be remiss of us not to add a few lines summarizing the behavior and NAT (network address translation) for the different deployment modes:
Inbound
By default, inbound is via a public IP address assigned to the service.
This changes if you opt into using a Private Endpoint (for any of the tiers supporting this feature). Always remember to explicitly turn off the public ingress if you deploy a private endpoint instead and no longer require it.
This also changes if you deploy the Premium (or Developer) tier, added to your Virtual Network (“VNet-injected”), and set the mode to “internal”. In this mode, although a public IP is still deployed for control plane traffic, all data plane traffic will go through the private IP (Internal load balancer endpoint) which is provided in this mode.
Outbound
By default, outbound traffic is via the public IP(s) assigned to the service.
This changes for Premium (or Developer) tiers when the service is added to your Virtual Network (irrespective of the inbound mode being public or private). In this case
For internal traffic leaving API Management – for example API Management reaching to a backend service hosted on a downstream VM within the network – there is no SNAT (source network address translation). If the next hop is an NVA (network virtual appliance/firewall) any rules for the source should use the subnet prefix, not individually mapped IPs.
External bound traffic breaking out (non RFC1918) is SNAT to the single-tenant (dedicated) public IP assigned. This includes traffic to other PaaS services via a public endpoint (although you should note the traffic in this instance stays on the Azure backbone).
For Standard V2 using “VNet integration”
NAT for internal traffic is the same.
External bound traffic breaking out is SNAT to one of the hosting stamps shared public IPs. If you want control over the outbound IP, use an Azure NAT Gateway on the subnet or route via an NVA (network virtual appliance, or firewall). Same note as above applies for PaaS-to-PaaS traffic via Public IPs.
Note for v2 tiers: API MANAGEMENT control plane and its own dependency traffic is not seen on the customers network, which is an enhancement from the GA tiers, and simplifies scenarios requiring force-tunnelling / firewall integration.
This article is contributed. See the original author and article here.
Microsoft is excited to participate in Embedded World, April 9-11, 2024 in Nuremberg, Germany, the leading international fair for embedded systems. This event showcases the latest innovations and trends in the field. From hardware and software to tools and services, this event brings together experts and industry leaders from around the globe to share their knowledge and insights. In this blog, we will give you a sneak peek at Microsoft’s presence at the event, including highlights on key topics, and what to expect from Embedded World.
Makers of embedded devices will be interested in Azure Private MEC (Multi-access Edge Compute) for several reasons:
Low Latency and Edge Compute: Azure private MEC provides low-latency and high-bandwidth connectivity combined with highly available edge computing services, for IoT and other edge devices, enabling real-time data processing and decision-making.
Scalability: Azure private MEC allows makers of embedded devices to easily scale their solutions, adding new devices and capabilities as needed.
Security: Azure private MEC provides a secure and isolated environment for processing sensitive data, reducing the risk of data breaches and cyber-attacks.
Device Density: Azure private MEC can support a high density of devices on a manufacturing floor, allowing for seamless connectivity and communication between numerous devices.
Connect with us in Hall 5 Stand 353
Visit us at our booth in Hall 5 to explore our innovative demos and experiences, connect with product and partner experts on featured products, and meet one-on-one with Microsoft leaders.
Microsoft invites attendees to join the following sessions where they will discover more about Azure private MEC and how private 5G is unlocking industry transformation. This is a great opportunity to get practical guidance on how to prepare your organization for innovation and growth, including learning on tools and frameworks to determine when, where, and how to focus on specific use cases emerging across industries today.
Understanding the ROI of a 5G-enabled factory April 9 | 12:00 pm
Intelligent factories leverage advanced technologies and automation to optimize manufacturing processes and enhance overall efficiency. These factories integrate various technologies such as artificial intelligence (AI), machine learning, Internet of Things (IoT), robotics, and data analytics to create a connected and intelligent production environment.
Hand on Lab with Azure Private 5G Core April 10 | 4:00 pm
April 11 | 1:30 pm
Register for a deep dive session in our Microsoft Learning Center, located across from the Microsoft booth (#5-469) where we will explore:
Azure private MEC solutions and their use in different industry verticals.
Why build applications and devices supporting the private MEC platforms.
Opportunity for growth with 5G and private MEC
Learn more about Azure private MEC
Whether you’re an enterprise , looking to leverage our solutions, a developer eager to create network-aware applications, or an application ISV seeking to collaborate with Microsoft on MEC solutions, we invite you complete this form to get contacted by a member of the private MEC team.
To learn how Microsoft is helping organizations embrace 5G with modern connected applications, sign up for news and updates delivered to your inbox.
This article is contributed. See the original author and article here.
We are announcing two important updates for users of Copilot for Microsoft 365. First, we are bringing priority access to the GPT-4 Turbo model to work with both web and work data. Second, later this month we are bringing expanded image generation capabilities in Microsoft Designer.
This article is contributed. See the original author and article here.
In the ever-evolving landscape of generative AI, a copilot isn’t just a companion that makes tasks that you’re already doing at work easier, but it’s quickly becoming a transformative force reshaping the very core of how things are done.
After shipping 13 publicly available Microsoft Copilot features in Microsoft Dynamics 365 Customer Insights that enable marketing teams to ask Copilot questions about their data, receive ideas for content from key points they want to make, define audiences and journeys in everyday words, understand their data quality, or get a summarized answer from multiple sources on how to use a feature within Dynamics 365 Customer Insights (to name a few), we realized that Copilot can help our marketing teams not just with tasks, but can completely change their workflow.
This workflow in Dynamics 365 Customer Insights will enable marketers to deliver unparalleled customer experiences (CXs). This could encompass a myriad of scenarios, from a marketing campaign for a new product or promotion, to managing how companies interact with their customers in key moments at scale.
The new Copilot in Dynamics 365 Customer Insights
The new Copilot in Customer Insights in now available in preview.
Take for example a theme park—as customers scan their tickets to ride attractions, they can receive personalized messages and notifications across their preferred channels be it: in-app, web, text message, or email. This not only enhances customer experience by making the most out of their visit but also enables the company to maximize customer spending.
Companies often spend a tremendous amount of time building these campaigns and experiences. With the growing demand for digital and mobile experiences, coupled with the need to use customer data from an expanding array of disconnected systems to personalize and trigger the experiences, the time and cost to deliver continues to rise.
Our conversations with numerous companies illuminated a common pain point—the process to deliver a CX project or campaign can extend from 12 to 15 weeks (about three and a half months). There are no signs this will decrease in length.
It’s not surprising why. The current marketing workflow resembles a complex team sport, requiring multiple contributors focused on different aspects—audience, journey, content, and the delivery channel.
Most teams create campaigns starting with a blank canvas; assembling, testing, and going live; then tracking the analytics to ensure everything is going well and any drop-off points are addressed. The complexity and coordination across people affect more than the time to market, it affects the quality and level of personalization delivered to the end customer.
Copilot in Dynamics 365 Customer Insights will completely change the game.
“At Campari Group, we’re excited by the opportunities these new Copilot capabilities will bring us to streamline our digital marketing processes—driving collaboration and enhancing our ability to deliver a truly engaging consumer experience, whilst staying one step ahead of the competition!”
David Hand– Global IT Manager, CRM, Campari
Companies have data that ground Copilot in brand styles, tone, language, and imagery. Briefs contain a lot of key information about the intent, success, branding, and key points. Over time, data from prior projects or campaigns will drive the continuous improvement of business results.
Armed with this data, what if you could describe the outcomes you want, and Copilot in Dynamics 365 Customer Insights could take the lead?
Our vision has four key areas of innovation:
We’re removing complex UIs that are difficult to navigate and use, instead Copilot will provide dynamic user experiences (UX) that come to you based on what you are trying to achieve. Examples of this are the dynamic project board and analytics.
Instead of marketers having to start from a word or pixel for every element of the project or campaign, Copilot provides data-driven suggestions that allows you to curate your project instead of having to create every piece. Everything starts connected and Copilot keeps it connected and in sync making any downstream changes saving the marketer time and eliminating a class of errors due to partial changes. Choose from suggested images, emails, audiences, journeys, and more instead of having to create each element from scratch. We don’t believe any of the suggestions will be 100% of what the marketing team needs, what we do know is that even if it’s only 60% the way there, it will save 60% of the time needed to launch the project.
We’re removing the constraint of resources limiting the quality of experience and depth of personalization. Instead of personalizing to four cohorts, Copilot will personalize to 64 cohorts or more. But then, you need confidence in what you’re delivering to customers. We are innovating in new UX and Copilot capabilities that will allow marketing teams to review and approve at Copilot scale where instead of having to review 100 variations across the journey, Copilot will tell you the key variations to review and tweak and make corrections on your behalf.
Today, after a project or campaign goes live, you need to assign a person to track the analytics and find where customers are dropping off. That person then needs to work with the right people to improve the results. Now, Copilot can track the analytics on behalf of the marketing team and proactively notify of optimizations with suggested options that allow the team to curate rather than create and deliver business success.
We’re partnering with Typeface to deliver this vision, and it plays a key role in enabling scaling on-brand multimodal content personalization in ways that simply were not possible in the past. Typeface understands your brand in depth and utilizes that understanding to deliver text and images that align to companies’ brand guidelines enabling one-on-one personalization with on-brand images at a scale that wasn’t viable in terms of time and cost before.
“Copilot holds the potential to be a real game-changer. Its ability to seamlessly align our business goals with community values has the potential to save us valuable time on internal processes. This efficiency translates to quicker iterations and more frequent connections with our audience. It’s not just shaping up to be a tool but a strategic advantage.”
Martin Nicholson–Digital Engagement Manager, Rare Ltd., Xbox – Sea of Thieves
This innovation is not years away, not months, not even weeks. Today, we’re happy to announce that our first public preview focusing on curation rather than creation is now available in Dynamics 365 Customer Insights in English, in all regions. Sign up to be one of the first to preview and experience the new capabilities.
We invite you to explore this transformative journey as Copilot takes the reins, opening a new era in marketing workflows. Join us in redefining how work gets done.
Recent Comments