It was only 9 days ago that I released the latest minor version of this package, on that time the goal was to update the Security and Governance stencils to please my dear friend Nino Crudele. It was then that I notice that Microsoft did again a completely redesigned on several of the symbols and of course add new services so I decided that this was the time to not only refresh the package with the new icons but also but so extra work.

What’s new in this version?

With the growing number of stencils in this package, it was becoming hard to easily find or look for the right shape/representation. So once again based on some feedback I received from the community I decide to do so rearranging. I still have many things to do in this project in terms of organization but for now, these are the changes on this major release:

• New shapes: The main additions are all the new shapes on the Azure Portal. New shapes added on:
  • MIS Azure Stencils: containing all the main Azure Portal Services
  • MIS AI and Machine Learning Stencils: all shapes related to AI or Machine Learning scenarios;
  • MIS IoT Devices Stencils: all shapes related to IoT scenarios:
  • Microsoft Integration Stencils;
  • MIS Azure Others Stencils: containing Azure Postal Services, features of the services and other interesting shapes;
  • MIS Azure Additional or Support Stencils: other shapes that may be interesting in supporting Azure diagrams and designs or presentations;
• MIS Azure Stencils: Complete update to this category with many new shapes added and many shapes moved to MIS Azure Others Stencils file;

• MIS AI and Machine Learning Stencils: Complete update to this category with many new shapes added and updating many others to there current stencils;

• Add categories:
  • Microsoft Integration Stencils Old Version Stencils: containing all the oldest versions of stencils (obsolete, deprecated or replaced by a new shape)
• Ordered by name: I recently started to sort shapes in alphabetical order. These are the categories already sorted:
  • MIS Azure Stencils;
  • MIS Azure Others Stencils;
  • MIS AI and Machine Learning Stencils;
  • Microsoft Integration Stencils Old Version Stencils;
  • MIS Security and Governance;
• Text Annotations: This is a requested feature and I already started to work on it but it will get some time to finish it. For now, you will see text annotations on:
  • MIS AI and Machine Learning Stencils

• SVG Files: Add new SVG files, and uniform the name of the files;

Microsoft Integration, Azure, Power Platform, Office 365 and much more Stencils Pack

Microsoft Integration, Azure, Power Platform, Office 365 and much more Stencils Pack it’s a Visio package that contains fully resizable Visio shapes (symbols/icons) that will help you to visually represent On-premise, Cloud or Hybrid Integration and Enterprise architectures scenarios (BizTalk Server, API Management, Logic Apps, Service Bus, Event Hub…), solutions diagrams and features or systems that use Microsoft Azure and related cloud and on-premises technologies in Visio 2016/2013:

• BizTalk Server
• Microsoft Azure
  • Integration
    • Integration Service Environments (ISE)
    • Logic Apps and Azure App Service in general (API Apps, Web Apps, and Mobile Apps)
    • Azure API Management
    • Messaging: Event Hubs, Event Grid, Service Bus, …
  • Azure IoT and Docker
  • AI, Machine Learning, Stream Analytics, Data Factory, Data Pipelines
  • SQL Server, DocumentDB, CosmosDB, MySQL, …
  • and so on
• Microsoft Power Platform
  • Microsoft Flow
  • PowerApps
  • Power BI
• Office365, SharePoint,…
• DevOps and PowerShell
• Security and Governance
• And much more…
• … and now non-related Microsoft technologies like:
  • SAP Stencils

The Microsoft Integration Stencils Pack is composed of 28 files:

• Microsoft Integration Stencils
• MIS Azure Stencils
• MIS Additional or Support Stencils
• MIS AI and Machine Learning Stencils
• MIS Apps and Systems Logo Stencils  
• MIS Azure Additional or Support Stencils
• MIS Azure Mono Color
• MIS Azure Old Versions
• MIS Azure Others Stencils
• MIS Buildings Stencils
• MIS Databases and Analytics Stencils
• MIS Deprecated Stencils
• MIS Developer Stencils
• MIS Devices Stencils
• MIS Files Stencils
• MIS Generic Stencils
• MIS Infrastructure Stencils
• MIS Integration Fun
• MIS Integration Patterns Stencils
• MIS IoT Devices Stencils
• MIS Office365
• MIS Power BI Stencils
• MIS PowerApps and Flows Stencils
• MIS SAP Stencils
• MIS Security and Governance
• MIS Servers (HEX) Stencils
• MIS Users and Roles Stencils
• Microsoft Integration Stencils Old Version Stencils

That you can use and resize without losing quality, in particular, the new shapes.

Download

You can download Microsoft Integration, Azure, BAPI, Office 365 and much more Stencils Pack for Visio from:
Microsoft Integration, Azure, Power Platform, Office 365 and much more Stencils Pack for Visio
GitHub

or from :

You can download Microsoft Integration Stencils Pack for Visio 2016/2013 from:

Microsoft Integration Stencils Pack for Visio 2016/2013 (10,1 MB)
Microsoft | TechNet Gallery

The post Microsoft Integration and Azure Stencils Pack for Visio: New major version available (v6.0.0) appeared first on SANDRO PEREIRA BIZTALK BLOG.

The post Microsoft Integration and Azure Stencils Pack for Visio: New major version available (v6.0.0) appeared first on BizTalkGurus.

Do you feel difficult to keep up to date on all the frequent updates and announcements in the Microsoft Integration platform and Azure iPaaS?

Integration weekly update can be your solution. It’s a weekly update on the topics related to Integration – enterprise integration, robust & scalable messaging capabilities and Citizen Integration capabilities empowered by Microsoft platform to deliver value to the business.

Microsoft Announcements and Updates

• Azure Storage Blobs User Delegation SAS Tokens now Generally Available
• The Azure Blockchain Workbench Solidity compiler has been upgraded to version 0.5.10
• Turning to a new chapter of Windows Server innovation
• Update to the Power Platform Center of Excellence Starter Kit

Community Blog Posts

• BizTalk Server 2020 is Released!  by stephen-w-thomas
• If a service doesn’t do these 3 things, it’s probably not Serverless  by Burke Holland
• For loop in Logic Apps  by Toon Vanhoutte
• Understanding Managed Identity and using it to Call Secured function App  by Maheshkumar Tiwari
• The Reunification of .NET 5  by Matthew MacDonald
• Power Platform Governance with Power Clarity  by John Liu
• Developer’s Guide to Common Vulnerabilities and How to Prevent Them  by Holly Lloyd
• Where programming languages are headed in 2020

Video

• Improving Azure Logic Apps Performance using the SplitOn feature  by Kent Weare
• How to do Bulk and Transactional Batch operations with the Azure Cosmos DB .NET SDK  via channel9
• Best Practices – Advanced Async / Await   via channel9

Podcasts

• Visual Studio Online with Nik Molnar  via .Net Rocks Podcast
• Myself: It’s not weird at all  via Hanselminutes Podcast
• DevOps from a Product Manager’s Perspective  via Azure DevOps Podcast

How to get started with iPaaS design & development in Azure?

• Robust Cloud Integration with Azure
• Microsoft Azure for Developers: What to Use When
• Serverless Computing: The Big Picture
• Azure Logic Apps: Getting Started
• Azure Logic Apps: Fundamentals
• Microsoft Azure Developer: Creating Enterprise Logic Apps
• Microsoft Azure API Management Essentials
• Azure Functions Fundamentals
• Cloud Design Patterns for Azure: Availability and Resilience
• Architecting for High Availability in Microsoft Azure

Feedback

Hope this would be helpful. Please feel free to reach out to me with your feedback and questions.

• Twitter
• LinkedIn

The post January 20, 2020 Weekly Update on Microsoft Integration Platform & Azure iPaaS appeared first on BizTalkGurus.

On 15^th of January 2020, Microsoft announced the release of BizTalk Server 2020. There was a lot of buzz on social media about the release. Pretty much all of the posts were highlighting and excited about the new set of features that got shipped in the product.

Even though the release came with a bunch of exciting new features like any other regular software product updates, there are some important points to note, especially for people who invested heavily in Microsoft BizTalk Server for the past 2 decades.

BizTalk Server 2020 is not just a simple software update it’s a game-changer and beginning of a new era. 

Two decades of past

That’s how long Microsoft BizTalk Server is in the market. 

The first version came in 2000, and now we are in 2020 and excited about the new release “BizTalk Server 2020”. Microsoft consistently released a new version every 2-4 years once for the past 20 years (2000, 2002, 2004, 2006, 2006 R2, 2009, 2010, 2013, 2013 R2, 2016 and now 2020) – i.e 11 major releases. 

There are very few products in the history of software sustained a two decades life span and still going strong. On Microsoft land I can only think of a few products like Windows, Office, SQL Server are the ones which reached this milestone.

 I’m feeling lucky enough to be one of them who worked on this amazing piece of technology for 20 years now. For most of the software developers out there, our career is pretty much determined by our initial few months/years after graduation and where we end up. For some people, you become programmers, again depending on what technology stack you got initial opportunities, some become data guys like DBA’s, IT administrators,  and in the modern era new things like AI/ML, Big Data, etc. For me, it was/is BizTalk Server and Integration in general. 

In the past 20 years, I have seen various technologies come and go. We ourselves were bitten by choosing a wrong one for BizTalk360 in the initial days. Microsoft Silverlight as our front-end, the thing that looked flashy and promised to change the way Rich Internet Applications (RIA) are build quietly died and we ended up wasting full 1 year rebuilding everything in HTML5. We finally released version 7.0 back in Oct 2013 fully revamped in HTML5  

Unless otherwise, the product solves a core problem well, the chances of sustainability for this long is pretty slim.

One decade of future commitment

When Microsoft releases a server product like BizTalk Server, they commit for 10 years of product support commitment. 5 years of regular support and another 5 years of extended support for you to comfortably run your production systems without worrying about the end of life.

BizTalk Server 2020 is Microsoft’s commitment to existing customers who invested in BizTalk Server and future customers the product is supported until 2030.

It’s very important for large enterprises to get this commitment. As I mentioned earlier, you cannot afford to make wrong bets (like what we did on the front-end technology for BizTalk360 using Microsoft Silverlight), you simply end up with wasted time, money and more importantly opportunity. For us, that one year was a very painful period, with limited resources instead of building exciting new features for our customers, we ended up redoing the same thing.

It’s not easy

Even for a large organization like Microsoft, it’s not easy to maintain and improve a legacy matured product like BizTalk Server.

During my long-standing relationship with BizTalk Server in this 20 years period, I have personally dealt with at least 4-5 different completely different sets of teams at Microsoft. This is what I have witnessed 

“People will come, people will go but the product stays.”

I can imagine it will be such a hard job to bring people on board to get up to speed understanding such a vast platform and innovate on top of that mixing the old and new era.   In spite of the challenges, Microsoft still continued and innovated constantly for the past 20 years. 

What goes behind the scene?

On every release, one of the important updates will be platform alignment. BizTalk Server relies on four important underlying platforms, the core Windows Operating System, SQL Server for data, Visual Studio for development tools and finally Microsoft Office for certain dependencies like BAM.

BizTalk Server 2020 supports the following platforms

• Visual Studio 2019
• Windows Server 2019, Windows Server 2016, Windows 10
• SQL Server 2019, SQL Server 2017, SQL Server 2016 SP2
• Office 2019, Office 2016

Supporting these new platforms is not always just a recompile of your code. For instance, the team had spent nearly 3 years rebuilding the tools for Visual Studio 2019. Some of the BizTalk Server toolings like Mapper and Orchestration designer is complex. Visual Studio 2019 changed the complete plugin-architecture and significant work has gone behind the scene to make it work.

There are few areas Microsoft does not highlight on the release notes, but that takes a significant amount of time for the product group like accelerators and adapters. Microsoft BizTalk Server is a central middleware hub supporting various industry standards like HL7, SWIFT, etc, these specifications change regularly as well, in every release they need to make sure they support the latest standards.

In a similar way, all those connecting BizTalk adapters like SAP, Oracle, JD Edwards, Peoplesoft, etc all need to be retested and realigned.

Being a global product there are a ton lot of legal procedures they need to pass through before a 20 year old product like BizTalk Server is released to the public.

You probably are not aware, some of the high-end military/defense teams across the world use BizTalk Server, it’s not that easy to commit a new release when you have such sensitive customers.

I remember having a conversation with one of the product owners of BizTalk Server in the past, how tough the whole legal process before they can get a go-ahead for the release.

Hub for modern and legacy world

If you look carefully at how Microsoft is positioning BizTalk Server 2020, it’s positioning it as a hub/window between the legacy and modern world.

The fact is, however the new cloud technology stack spans out and promises to change the world, there will always be an on-premise dependency. It will take at least another few decades (or never), for 100% cloud-native organizations to evolve.

Oh! Do you know still some of the big bank’s core systems are still running on IBM Mainframes built-in 1960 and ’70s?

For the past 10 years, in the enterprise world, it’s always a hybrid scenario, where certain things are best suited for on-premise and certain things are best suited for the cloud, you mix and match the tech stack that’s suitable for your business.

The below picture depicts how Microsoft BizTalk Server can act as a glue between the on-prem and the cloud world and get most of the benefit out of both.

There are a lot of features that shipped with BizTalk Server 2020 supporting this vision.

• API Management
• Azure Adapters for Event Hub, Blob Storage, Service Bus v2, Logic Apps
• Using blog storage for data backups
• Office365 adapters for Email, Calendar, and Contacts

New customers – is BizTalk Server the right technology?

If you are on a hunt for choosing your middleware platform, it’s not an easy decision to make. With a ton of new products available in the market and each product requiring months of learning to understand the capabilities, it’s never going to be easy to compare and test everything.

But sometimes you need to go with the proven technology and the future vision of the product. BizTalk Server sustained 20 years of constant improvement (a release pretty much every 2-3 years once 2000, 2002, 2004, 2006, 2006 R2, 2009,2010, 2013, 2013 R2, 2016), a lot of features and underlying architecture are robust and scalable to sustain such a long time period.

This long history of the product is such an important decision-making factor.

And the future commitment from Microsoft gearing towards the cloud makes it a perfect candidate for any organization to bet on this middleware platform.

Why BizTalk Server developers and administrators must be excited?

Learning a complex product like BizTalk Server is time consuming long term commitment. It takes years of work and the right projects to fully understand the product and its capabilities. If you have invested your time in the past few years being a BizTalk Developer or Administrator it’s a great time to be excited with the commitment from Microsoft on the future of BizTalk Server. 

BizTalk360 is ready for BizTalk Server 2020

For those of you who are not aware of BizTalk360. I would like to give a short intro and excited to announce after working with Microsoft for the past few months, we are now fully supporting Microsoft BizTalk Server 2020 with our latest release.

We are a 3^rd party product providing advanced monitoring and management capabilities for Microsoft BizTalk Server. Out of the box, BizTalk Server comes with a management console called “BizTalk Admin Console”, which does a great job for people to manage and operate your BizTalk Server environments. However, the tool lacks a lot of advanced capabilities like web-based management console, advanced user access security features, advanced toolings like throttling analyzer, topology viewer, messaging patterns viewer, health dashboards, etc.

Monitoring for a platform like BizTalk Server is so crucial, but BizTalk Server doesn’t come out of the box with any monitoring capabilities. The customers need to rely on Microsoft SCOM or 3^rd party products like BizTalk360. SCOM management packs for BizTalk Server is not updated for many years and it comes with only minimal monitoring capabilities.

BizTalk360 is a widely used product in the market with over 650 large enterprises helping them to manage/operate and monitor their BizTalk Server environments. BizTalk360 supports BizTalk Server 2013, 2013 R2, 2016 and now 2020.

You can get a 30 days trial version of BizTalk360 and explore the product yourself or arrange for a personal demo of the product.  

The post BizTalk Server 2020 – Why it’s a game-changer? appeared first on BizTalk360.

The post BizTalk Server 2020 – Why it’s a game-changer? appeared first on BizTalkGurus.

BizTalk Filter Finder tool got an update and it is now more powerful and with new features and mainly all of that thanks to Michał Plutyński contributions. And for those who are not familiar with this tool, the BizTalk Filter Finder Tool is a simple tool that aims to simplify the process for better understand and maintain solutions based on content-based routing and context-based routing with or without orchestrations involved.

This tool will extend default BizTalk Server capabilities transforming this tedious and sometimes complicate analysis a little simple, easy and fast. You can read more details about this tool in the original post here: BizTalk Filter Finder Tool.

What’s new in the release

• A new dropdown list that allows you to select your BizTalk Server environment (you can set up them in the config file), this way is better and easier to use in bigger teams with several environments.

• Add filters/search capabilities allowing you to filter the existing subscriptions and only show filters with subscriptions that contain some text;

• Hotfix/improvements: Changes in reading orchestration list when it’s used a MessageBoxDb on a different server then ManagementDb.

Credits to Michał Plutyński for becoming a collaborator of this tool.

Download

You can download BizTalk Filter Finder Tool from:
BizTalk Filter Finder Tool
GitHub

The post BizTalk Filter Finder Tool v2.0.0 available for BizTalk Server 2016 appeared first on SANDRO PEREIRA BIZTALK BLOG.

The post BizTalk Filter Finder Tool v2.0.0 available for BizTalk Server 2016 appeared first on BizTalkGurus.

Microsoft has been discontinuing some actions for some time or at least
running side by side different versions, don’t get me wrong. But they were never
extremely good at providing proper documentation, even in the old days that we
had software releases every two or three years, now imagine in this crazy fast
delivery world that we are leaving! What you see is:

• A big gap between the documentation and the features that we have available or not properly documented in terms of how they work;
• There is nothing that tells you what was change or how certain task that was possible to do in previous versions of action can now be done.

When I say that for the first time that Microsoft deprecated connection
actions, I mean actual remove from the list of actions on the Logic App design,
taking from the example the two connectors mention above you can’t see
the deprecated action on the Logic App designer anymore:

But don’t be alarmed, your existing logic apps that still use these
deprecated actions continue to work properly.

In this article, we will address the Office 365 Outlook connector and especially the Send an Email V2 action because Send an Email action is now deprecated. So the question here is:

How to send a well-formatted custom HTML Email using Send an Email V2 action available on the Office 365 Outlook connector?

I personally liked the Send
an Email action because we were able to directly put HTML code on the body
property and define that the email body format would be HTML bt setting the
property Is HTML to true.

Quite simple to use and
efficient.

However, Send an email (V2) action has totally different
behavior. First of all, it owns fewer properties:

• Is HTM property was removed from this action;

And a completely new look
and feel of the Body property as you see in the picture below:

• With a powerful editor similar to what we have in our office tools (Word, Outlook, …)

That also means that we no longer have the possibility to directly insert HTML code into the body property of the message as we did earlier with the previous version. Well, we can write HTML code on the body of this action:

But the end result will not be what you expect:

Unluckily Power Automate designer, we don’t have a Code View button (</>) on the Body property editor, I will be blogging about this feature soon on Serveless360 blog. So, who we are able to send a proper well-formatted HTML Email using Send an email V2 action?

The answer is: unfortunately, at least in my opinion, we need to build the HTML in an action beforehand in a composite action or in a variable. And then put the compose output or variable as the send mail body property, and the action will render correctly the output as an HTML.

To do that we need:

• On
  the Logic App designer, add the next step by clicking the +New step
  button
• On
  the Choose an action window, enter Variables and select the
  action Initialize variable
• On
  the Variable action configuration:
  • On
    the Name property, type “EmailBody”
  • On
    the Type property, specify the type as “String”
  • On
    the Value property leave it blank

• On
  the Logic App designer, add the next step by clicking the +New step
  button
• On
  the Choose an action window, enter Variables and select the
  action Set variable
• On
  the Variable action configuration:
  • On
    the Name property, select “EmailBody” variable
  • On
    the Value property, type your custom HTML

Note: you can take as example this fancy HTML Template that I created specifically for this article here: HTML Notification Template to use Logic App or Power Automate Outlook connector and not this basic HTML that you are seeing on the picture.

• And then define directly on the Body editor (without switching to Code View) that the body will be the content of the variable we created earlier:

And you will see that you
will be receiving also a well-formatted HTML email on your mailbox:

Thanks Thiago Almeida for the help and credits to Pedro Rosa that helped me creating this HTML Template and most important to be compatible with Outlook because not all the stylesheets that we can apply aren’t compatible.

Hope this helps!

The post Logic Apps: How to send a well-formatted HTML Email notification with Office 365 Outlook connector appeared first on SANDRO PEREIRA BIZTALK BLOG.

The post Logic Apps: How to send a well-formatted HTML Email notification with Office 365 Outlook connector appeared first on BizTalkGurus.

At our annual event Integrate, Microsoft announced last year that BizTalk Server 2020 should have released in the first quarter of 2019. Only two weeks in the new year, Microsoft has released BizTalk Server 2020 (v3.13.717.0)! In this blog, we want to update you on what’s new in this version of the product.

No Changes in Available Editions

Similar to earlier versions of the product, BizTalk Server 2020 comes in 4 flavors:

• Microsoft BizTalk Server 2020 Developer
• Microsoft BizTalk Server 2020 Branch
• Microsoft BizTalk Server 2020 Standard [to do: changed limitations]
• Microsoft BizTalk Server 2020 Enterprise

You can download these products when you have an Enterprise MSDN account.

New Features in BizTalk Server 2020

During Integrate 2019, Paul Larsen, the Program Manager who is responsible for BizTalk Server, already highlighted which new features are coming in BizTalk Server 2020. You can read a recap about Paul’s session here.

As you can understand from Paul’s session, we were already expecting platform alignment. More importantly, BizTalk Server 2020 contains all features from BizTalk Server 2016, including the 3 Feature Packs, which have been released.

You can find the complete set of new features here

But, let’s have a look at some of the new features and capabilities.

Deprecated and Removed Features

Some features of the product are deprecated or removed from the product. Here’s the list:

Changes that Catch the Eye

Based on the above lists, and besides the already expected features and improvements, a few features catch the eye.

Audit Log

Until now, no auditing was available for any operations performed against the BizTalk environment. Luckily, from BizTalk Server 2020 on, the Administration console provides auditing of operations. To be able to use this feature, you will have to turn it on in the Group Settings screen.

The auditing data is stored in the Management database, and you can access it via the Operational Services. At the moment, the supported operations are:

• Creating, updating and deleting ports
• Suspending, resuming and terminating service instances
• Adding, updating and removing BizTalk applications
• Importing binding files

Although this is a good start, multiple important operations are still missing; think of starting/stopping of ports, orchestrations, and host instances. We hope that Microsoft adds such operations in the future.

Read more about this feature here.

Support of .NET Framework v4.7

Earlier, Microsoft has announced that .NET 4.8 will be supported.

New Read-Only Operator role

The BizTalk Operator role has changed. Where before, it was possible to perform actions like stopping/starting ports and changing the port configuration, this role is now completely read-only. This can certainly be useful for facilitating DevOps scenarios.

When accessing the BizTalk Server 2020 Admin console as a BizTalk Operator, all the operations are still accessible. However, when an operator tries, for example, to stop a port, an error message shows up, and the operation becomes blocked. Unfortunately, the error message is not always clear that the operation is blocked due to insufficient permissions.

BAM Portal is Deprecated

Microsoft has decided to deprecate the BAM portal. Probably due to the new capabilities to push data to Azure, they decided to deprecate the old-fashioned BAM portal. In case you are using BAM, and you are considering upgrading to BizTalk Server 2020, you can still install and configure the BAM portal from the BizTalk installer and configuration wizard; you won’t be left in the dark.

Deprecated and Removed Adapters

Multiple updates in this area as well. For example, Microsoft deprecates the POP3 and the SMTP adapters in favor of the Office 365 adapters, which appeared in the BizTalk Server 2016 Feature Packs. Next, the old SQL adapter has been removed and replaced by the WCF-SQL adapter, and the JDE OneWorld and the WCF-NetTcpRelay adapter have both been deprecated.

BizTalk360 Support of BizTalk Server 2020

The BizTalk360 product team has eagerly followed the developments around BizTalk Server 2020, and we are glad that BizTalk Server 2020 has been released. For BizTalk360, it is evident that the product must support all recent versions of BizTalk Server.

That’s why we made the latest released versions of BizTalk360 and Atomic Scope compatible with BizTalk Server 2020!

Conclusion

BizTalk Server 2020 has been released. This is the 11^th version of the product since its inception in 2000. Although we have already seen most of the features of this release (in the BizTalk Server 2016 Feature Packs), this is still a useful release. Especially when you are still on versions older than BizTalk Server 2016, it will certainly be worth upgrading or migrating to this release.

The post What’s new in BizTalk Server 2020! appeared first on BizTalk360.

The post What’s new in BizTalk Server 2020! appeared first on BizTalkGurus.

Do you feel difficult to keep up to date on all the frequent updates and announcements in the Microsoft Integration platform and Azure iPaaS?

Integration weekly update can be your solution. It’s a weekly update on the topics related to Integration – enterprise integration, robust & scalable messaging capabilities and Citizen Integration capabilities empowered by Microsoft platform to deliver value to the business.

Microsoft Announcements and Updates

• Azure Logic Apps updates for November and December 2019
• Azure API Management update—January 2020
• Azure Functions runtime 3.0 is now generally available
• Introducing the SAP ERP connector
• Best Practices and Step-By-Step Guide for creating an enterprise scale automated invoicing process with Power Automate

Community Blog Posts

• BizTalk Server 2020 – Why it’s a game-changer?  by Saravana Kumar
• BizTalk Filter Finder Tool v2.0.0 available for BizTalk Server 2016  by Sandro Pereira
• Azure Functions Live – January 2020
• How to create a serverless application to receive and process events via an Azure Event Grid  by Paolo Salvatori
• How Azure Event Grid is different from logs, alerts, change feeds and webhooks  by Tom Kerkhove
• Exposing Cosmos DB change feed from ASP.NET Core  by Tomasz Pęczek
• Getting Started with Visual Studio Online – Cloud IDE  by Chris Pietschmann
• Refactoring Code to Use C# Local Functions  Jason Roberts
• Five Questions for 2020  by  Stephen O’Grady

Video

• Microsoft Cloud Adoption Framework for Azure, Part 1  via Azure Friday
• Microsoft Cloud Adoption Framework for Azure, Part 2  via Azure Friday
• It’s just SQL: CLR in Azure SQL Database Managed Instance  via channel9
• Connecting Power Virtual Agents to ServiceNow using Power Automate Video  by Kent Weare

Podcasts

• Azure FarmBeats  via The Azure Podcast
• Emily Freeman on Modern DevOps  via Azure DevOps Podcast
• The Perfect Education for a Software Developer with Thomas Betts  via .Net Rocks Podcast

How to get started with iPaaS design & development in Azure?

• Robust Cloud Integration with Azure
• Microsoft Azure for Developers: What to Use When
• Serverless Computing: The Big Picture
• Azure Logic Apps: Getting Started
• Azure Logic Apps: Fundamentals
• Microsoft Azure Developer: Creating Enterprise Logic Apps
• Microsoft Azure API Management Essentials
• Azure Functions Fundamentals
• Cloud Design Patterns for Azure: Availability and Resilience
• Architecting for High Availability in Microsoft Azure

Feedback

Hope this would be helpful. Please feel free to reach out to me with your feedback and questions.

• Twitter
• LinkedIn

The post January 27, 2020 Weekly Update on Microsoft Integration Platform & Azure iPaaS appeared first on BizTalkGurus.

Nino Crudele just published a free whitepaper about Azure Fundamental for Ethical Hackers and Special Ops Team. This is a 39 pages whitepaper about Azure Fundamentals and Penetration Testing and if you’re passionate about security or want to know a little more, then you shouldn’t miss this opportunity.

Nino Crudele is a freelance living in the United Kingdom. He is Global Azure Lead and Cybersecurity expert in Hexagon Manufacturing Intelligence, a global manufacturing company. He is responsible for leading the Microsoft Azure Cloud area, supporting and advising the Company to select the most appropriate cloud strategies and solutions from high-level design to implementation and Security is one of my top priorities.

What to expect about Azure Fundamental for Ethical Hackers and Special Ops Team whitepaper

This whitepaper will provide:

• A good understanding of Microsoft Azure, how it is organized and how it works, and this is a good prerequisite in order to create penetration tests, understanding the weaknesses and the critical areas and for any type of security operator.
• A good introduction and understanding about penetration testingS, the phases, the standards, the technique, and the methodologies related to Microsoft Azure

Where you can download it

The whitepaper is completely free and you can download it here:

• https://ninocrudele.com/azure-fundamental-for-ethical-hackers-and-special-ops-team

I would like to take this opportunity also to say thanks to Nino Crudele for inviting me to be is a technical reviewer for this whitepaper, as always with him it was a nightmare but a very enjoyable one.

The post Azure Fundamental for Ethical Hackers and Special Ops Team [free whitepaper] By Nino Crudele appeared first on SANDRO PEREIRA BIZTALK BLOG.

The post Azure Fundamental for Ethical Hackers and Special Ops Team [free whitepaper] By Nino Crudele appeared first on BizTalkGurus.

Do you feel difficult to keep up to date on all the frequent updates and announcements in the Microsoft Integration platform and Azure iPaaS?

Integration weekly update can be your solution. It’s a weekly update on the topics related to Integration – enterprise integration, robust & scalable messaging capabilities and Citizen Integration capabilities empowered by Microsoft platform to deliver value to the business.

Microsoft Announcements and Updates

• A new experiment: Call .NET gRPC services from the browser with gRPC-Web
• New Azure Lighthouse features are now generally available
• Azure DevOps—Release and pipelines events now available in the audit logs
• Assess your servers with a CSV import into Azure Migrate
• Introducing simplified AI Builder experience in Power Automate
• Driving Employee Training Using Microsoft Power Platform

Community Blog Posts

• What’s new in BizTalk Server 2020!  by Lex Hegt
• Cumulative Update 7 for Microsoft BizTalk Server 2016  by Coen (Colin) Dijkgraaf
• Azure Functions Triggers and Bindings  by  Priya Latha
• Why is my Azure Function host permanently stopped?!  by Tom Kerkhove
• Creating Azure Functions with Function Monkey–First Look by Jason Roberts
• Deploying ASP .NET Core 3.1 to Azure App Service  by Shahed C
• Azure Fundamental for Ethical Hackers and Special Ops Team [free whitepaper] By Nino Crudele  by Nino Crudele
• Power Apps Portals 2020 Release Plan Wave 1: CRUD is coming!  by Nick Doelman
• Create backups of your Power Apps environment  by Pieter Veenstra
• Microsoft Blazor to become mainstream in 2020  by ed Charbeneau
• Trying out Container Tools in Visual Studio 2019  by Scott Hanselman
• Top 10 .NET Core Libraries Every Web Developer Should Know  by Nagaraj Marisamy

Video

• How to publish your APIs with the new developer portal in Azure API Management  via Azure Friday.
• How to get started with Azure using Azure Quickstart Center  via Azure Friday
• Defining your cloud infrastructure as code with Pulumi and .NET  via channel9
• Bot Framework Composer  via channel9

Podcasts

• Building a CPU from Scratch with Ben Eater  via Hanselminutes Podcast
• SQL 2019 Big Data Clusters  via The Azure Podcast

How to get started with iPaaS design & development in Azure?

• Robust Cloud Integration with Azure
• Microsoft Azure for Developers: What to Use When
• Serverless Computing: The Big Picture
• Azure Logic Apps: Getting Started
• Azure Logic Apps: Fundamentals
• Microsoft Azure Developer: Creating Enterprise Logic Apps
• Microsoft Azure API Management Essentials
• Azure Functions Fundamentals
• Cloud Design Patterns for Azure: Availability and Resilience
• Architecting for High Availability in Microsoft Azure

Feedback

Hope this would be helpful. Please feel free to reach out to me with your feedback and questions.

• Twitter
• LinkedIn

The post February 03, 2020 Weekly Update on Microsoft Integration Platform & Azure iPaaS appeared first on BizTalkGurus.

BizTalk Server 2020 was officially released in the middle of January, January 15, 2020, to be more accurate. And you may be asking, why haven’t I written a post about this new version yet.

The answer is simple. I think this version should be properly analyzed, tested by us, and then we can talk about it. And for me, it all starts with installing and configuring the product, and this is where you will find the big differences between the previous version, BizTalk Server 2016 for this new version. You may have a quick overview of that on my twitter handle: https://twitter.com/sandro_asp:

It is not yet available, but for now, I can tell you that I have finished my BizTalk Server 2020 installation and configuration guide – 122 pages guide describing detail instructions to install all the features of the product – I think I may be the first one installing and configuring BAM Portal and is running properly. The installation guide will be published soon but for now, is under review.

Meanwhile, I’m really happy to see a lot of community members using my unofficial BizTalk Server 2020 logo on their articles:

It is a sign that you like it, but, once again, this is not the official logo. The official logo was released by Microsoft when BizTalk Server 2016 was launched and at that time Microsoft decided to drop the fancy Server icon from the logo and the version identification, now it is a simple generic logo with just Text that will be consistent in this and further versions of BizTalk Server. You may find the official logo here: Because BizTalk Server 2016 is almost here… take a look to the new BizTalk Server logotype.

But people sometimes prefer to use the “old” format just because it specifies the version, so it is easier to associate with the last version or a specific version of the product. And that was the main reason for me to create that logo.

Nevertheless, during BizTalk Server 2016 release, Microsoft also updated or released a BizTalk Server icon/stencil that you may find in the official BizTalk Server twitter handle:

So I decided that my first blog post after BizTalk Server 2020 was launched, it would be about updating my unofficial BizTalk Server logo and this time it would combine:

• The official BizTalk Server icon with the official BizTalk Server logo.
• Plus the version number.

And the end
result is this:

This package is a collection of 4 different image formats of the new Unofficial BizTalk Server 2020 logotype, two of them are available in vector format that will allow you to use and resize without losing quality:

• BizTalkLogo.ai
• BizTalkLogo.pdf
• BBizTalkLogo-01.jpg
• BizTalkLogoWhite-01.png

Thanks to Cristóvão Silva (Graphic & Web Designer @ DevScope) for helping me creating these resources.

Download

New Unofficial BizTalk Server 2020 logo in vector format
Microsoft | TechNet Gallery

The post BizTalk Server 2020: a new unofficial logo appeared first on SANDRO PEREIRA BIZTALK BLOG.

The post BizTalk Server 2020: a new unofficial logo appeared first on BizTalkGurus.

Recently I was challenged by my dear friend Wagner Silveira, to create another BizTalk Server sticker for INTEGRATE 2020 London, this time for BizTalk Server 2020. You may be aware of my previous BizTalk Stickers that you may find it here: Get your BizTalk Server 2016 Stickers!.

Note: personally, this is, without a doubt my favorite.

And of course the infamous badass T-Rex
version:

And the last one here: BizMan, The BizTalk Server Superhero Sticker

And of course, this was my answer: @WSilveiraNZ a new BizTalk Server 2020 sticker is being made… just to let you know #msbts but then Coen Dijkgraaf joined and asked if the sticker would be available on time for Global Integration Bootcamp?

I was undecided
about whether to publish or wait to INTEGRATE to be a surprise. But I at the
end I decided to create not one but two stickers:

• On to published during the INTEGRATE event… spam alert: it is awesome!
• And this one above to publish now in order for you all to grab it and go to a graphics shop to make your BizTalk Sticker. A simple and clean BizTalk Server 2020 sticker identical to the logo that I publish this week: BizTalk Server 2020: a new unofficial logo

This package is a collection of 3 different image formats of the new BizTalk
Server 2020 sticker, two of them are available in vector
format that will allow you to use and resize without losing quality:

• BizTalkSticker.ai
• BizTalkSticker.pdf
• BizTalkSticker-01.png

All of the
resources are in the original size ready to print in a graphics shop.

Thanks to Cristóvão Silva (Graphic & Web Designer @ DevScope) for helping me creating these resources.

I hope you enjoy!

Download

BizTalk Server 2020 sticker
Microsoft | TechNet Gallery

The post BizTalk Server 2020 sticker appeared first on SANDRO PEREIRA BIZTALK BLOG.

The post BizTalk Server 2020 sticker appeared first on BizTalkGurus.

As most of us are aware, starting with BizTalk Server 2013 and newer versions, Microsoft BizTalk ESB Toolkit is integrated with the BizTalk Server setup.

The wait is over, BizTalk Server 2020 is out now! On 15th of January 2020, Microsoft announced the release of BizTalk Server 2020. We got an opportunity to install and configure the ESB toolkit using BizTalk Server 2020.

While installing and configuring ESB we faced a huge challenge and surprise, that the ESB Portal was missing!!! In this blog, we would like to share our experience with you all that we gained and how we configured the ESB portal.

We would like to start from scratch, right from the installation of ESB in BizTalk Server 2020.

Prerequisites

• Choose Windows Server 2019 (Preferred) / 2016
• Install Visual Studio 2019 – Required for BizTalk Server Developer Tools and SDK.
• .NET Framework 4.7 – BizTalk projects created in Visual Studio require the Visual Studio build target to be set to your .NET Framework version
• Microsoft SQL Server 2019 (Preferred) – 2017 / 2016 SP2
• Install Enterprise Library 5.0 from the link- http://www.microsoft.com/en-us/download/details.aspx?id=15104
• Install Microsoft Report Viewer Redistributable 2008 from the link – http://www.microsoft.com/en-us/download/details.aspx?id=577

Add Roles & Features

• IIS with IIS 6 compatibility Tools(complete)
• Windows Authentication & Basic Authentication (Under: Web Server(IIS) -> Security
• WCF & HTTP Activation for both .Net 3.5 and 4.5/4.7

Installing ESB

Close any programs you have opened.

1. Run the BizTalk Server 2020 setup.exe file as Administrator
2. On the BizTalk Server installation Start page, click Install Microsoft BizTalk ESB Toolkit
3. On the License Agreement page, select “Yes, I accept the terms of the license agreement” and then select Next
4. In the Component Installation page, select the components you want to install, and then select Next

Note: If you observe the installation wizard, you may find the ESB Toolkit version is missing while comparing it with the BizTalk Server 2016.

5. In the Summary, review the installation details that you chose, and then select Install
6. On the Installation completed page, Select Finish to close the installation wizard. An install log file is created, similar to C:UsersyourUserNameAppDataLocalTempSetup(xxxxxx).htm
7. Starting with BizTalk Server 2020, to install the Itinerary Designer, also install the BizTalk ESB Toolkit Itinerary Designer extension in Visual Studio

Using Visual Studio 2019 -> Continue without code -> Extensions -> Manage Extensions -> Install BizTalk ESB Toolkit Itinerary Designer

Note:

1. You must configure BizTalk Server before configuring BizTalk ESB Toolkit
2. You must run the ESB Configuration Tool as an administrator

Configuring Microsoft BizTalk ESB Toolkit

1. From the Start menu, type ESB Configuration Tool or Scroll and select Microsoft BizTalk ESB Toolkit, and then select ESB Configuration Tool
2. In the ESB Configuration Tool, from the left pane, select ESB Configuration.
3. On the right pane, for Database Server: specify the database server where the databases, which are required for BizTalk ESB Toolkit, are created
4. In the IIS Web Services box, specify the User Account credentials under which the applications required for BizTalk ESB Toolkit are created. Also, specify the name of the website in IIS under which the applications are created
5. The BizTalk User Groups box lists the default user groups which are available for ESB configuration

Note: At this stage, you can click “Apply Configuration” towards the top of the ESB Configuration Tool to configure the Microsoft BizTalk ESB Toolkit with the default settings. However, if you want to do a custom configuration, you can perform the remaining steps as well. In such a case, the values you specify in the subsequent steps take precedence over the default values.

6. In the left pane, expand ESB Configuration, expand Exception Management, and then:

• If you don’t want to configure an exception management database, then select Database, and uncheck the Enable Exception Management Database
• If you want to use an existing database instead of creating a new database, then select Database, and select Use Existing Database. Enter the database server name and the database name
• If you don’t want to configure exception web service, then select Exception Web Services, and uncheck Enable Exception Services. If you want to run these services under a different website, you can enter that here

• If you don’t want to configure an itinerary database, then select Itinerary Database, and uncheck Itinerary Database
• If you want to use an existing itinerary database, then select Itinerary Database and select Use Existing Database. Enter the database server name and the database name
• If you don’t want to configure these web services, then select Core Web Services, and uncheck Enable Core Services. If you want to run these services under a different website, you can enter that here

If you are installing and configuring the BizTalk ESB Toolkit in a single server environment, select File Configuration Source.

If you are setting up a multiple-machine deployment, select the SSO Configuration Source, and then enter the following:

• SSO Server: Enter the name of the SSO server
• Configuration file: Click the ellipsis, and then browse to the esb.config file (Program Files (x86)Microsoft BizTalk ESB Toolkit)
• Application Name: Enter a name for the SSO application. For example, enter ESB Toolkit
• Contact Information: Enter a valid email address the appropriate contact information in the following format: support@biztalk360.com
• Administrator Group Name: Select the ellipsis, and then browse to the appropriate admin group
• User Group Name: Select the ellipsis, and then browse to the appropriate group

• Select Enable ESB Core Components in BizTalk Server to create the application in the BizTalk Server Administration console. Select Use Default Binding to bind this application to the default host. Select Do not use Default Binding, if you do not want to bind the application to the default host. In this scenario, you must explicitly bind the application to a host once the application is created.
• Select Enable ESB JMS/WMQ Components in BizTalk Server to create the application in the BizTalk Server Administration console. Select Use Default Binding to bind this application to the default host. Select Do not use Default Binding if you do not want to bind the application to the default host. In this scenario, you must explicitly bind the application to a host once the application is created.
• Click Apply Configuration to create the applications you selected. Verify that the applications are created in the BizTalk Server Administration console.

Verify Your Installation

To ensure if the site has been configured correctly, navigate to the folder C:Program Files (x86)Microsoft BizTalk ESB ToolkitWeb. Compare the folders and subfolders, and the sites under IIS -> Sites -> Default Web Site.

Open the BizTalk Server Administration console and notice that the ESB applications is now installed and present in our console.

Finally, ensure the availability of the “EsbExceptionDb” and “EsbItineraryDb” in the database.

ESB Portal Findings

Once after the installation and configuration of ESB Toolkit, if you have a look at the installation folder to configure ESB Portal, you will find that the file “ESBSource.zip” is missing…!!!

Once after the configuration in BizTalk Server 2016, you will be able to find the ESBSource.zip file. But it is not available in BizTalk 2020.

*Screenshot from BizTalk Server 2016 ESB Toolkit installed folder location

*Screenshot from BizTalk Server 2020 ESB Toolkit installed folder location

But, if you want to use the default ESB portal, you need the “ESBSource.zip” file to create it, or if you have another option, you can build your custom portal. We have compared the esb.config file to check if any changes have been done. When we checked the file, we found out that no changes have been done in the latest file. So, we thought of using the same portal in BizTalk server 2020 that was already used in the BizTalk server 2016.

To be able to use the existing ESB portal, we have copied the “ESBSource.zip” file from BizTalk Server 2016 and pasted inside the BizTalk Server 2020 folder C:Program Files (x86)Microsoft BizTalk ESB Toolkit.

ESB Portal Installation and Configuration

To install the default ESB portal

1. Create a folder in your C: drive and name it as Projects. Now, unzip ESBSource.zip file from the download location into the C:ProjectsMicrosoft.Practices.ESB folder
2. Once after extraction, Remove the Read-only attribute from all files in C:ProjectsMicrosoft.Practices.ESB folder
3. Install Enterprise Library 5.0 from http://www.microsoft.com/en-us/download/details.aspx?id=15104
4. Install Microsoft Report Viewer Redistributable 2008 from http://www.microsoft.com/en-us/download/details.aspx?id=577

Note: Leave step 4 and 5 if you have already done it earlier

5. In Visual Studio 2019, open ESB.Portal.sln found in C:ProjectsMicrosoft.Practices.ESBSourceSamplesManagement PortalESB.Portal
6. When Visual Studio 2019 starts converting the solution to the current format, a dialog pops up that warns you about ESB.Portal.Setup.vdproj file not being supported in Visual Studio 2019. Click OK. Wait until the solution opens
7. In the Solution Explorer, add Microsoft.Practices.ServiceLocation.dll as a reference to the ESB.BAM.Service.Implementation project. This assembly is found in C:Program Files (x86)Microsoft Enterprise Library 5.0Bin
8. Save all files in the solution
9. Rebuild ESB.Portal solution
10. Close Visual Studio
11. Run Management_Install.cmd file found in C:ProjectsMicrosoft.Practices.ESBSourceSamplesManagement PortalInstallScripts

If you can successfully run the Management_Install.cmd without any error/exception, the portal will be configured. Now when you open Internet Explorer and navigate to http://localhost/ESB.Portal you should see the ESB Management Console home page.

If you face any issues/exceptions when you run the Management_Install.cmd and the portal is not created, follow the below steps.

1. Open PowerShell as an Administrator and run the following command:

set-executionpolicy unrestricted

2. Open a command prompt as an administrator and run the following command to ensure WCF script maps are registered:

C:WindowsMicrosoft.NETFrameworkv4.0.30319> ServiceModelReg.exe -r –y

3. Got to turn on Windows Feature make sure the

• WCF features have been selected
• Web Core option also configured

• Powershell –executionpolicy bypass –file .Management_Install.ps1
• Management_Install.cmd

Now, without any errors/exceptions, the portal should be configured. Check if the ESB.Portal is available in IIS. When you open Internet Explorer and navigate to http://localhost/ESB.Portal you should see the ESB Management Console home page.

Phew!!! That’s how we configured ESB Portal.

Hub for Modern and Legacy World

Now we will come to the second option, custom portal…!

Even though the Exception Management framework is very robust and strong, the Exception Management Portal that comes out of BizTalk Server is not that easy to configure as we have experienced.

Firstly, the portal from the ESB Toolkit can be replaced with a portal within BizTalk360. BizTalk360 addresses these challenges in several ways. As with all features within BizTalk360, this portal is protected with security and auditing.

You don’t need to configure the default ESB portal. We want to mention here that a few of our customers haven’t installed the ESB portal.

Instead, they are using BizTalk360’s ESB Portal alone and from the portal, they are performing actions successfully.

To be able to repair ESB Faults, there is an Edit and Resubmit feature in BizTalk360. To make the repair even easier, you can write and associate Knowledge Base articles to the ESB Faults. So, in case of recurring problems, you can simply document the solution in such a KB article and associate it with the ESB Fault, thereby making repairs in the future easier.

How much time will it take to configure ESB portal within BizTalk360?

All you need to do to configure the ESB Exception management framework within BizTalk360, is to simply provide the connection string to your ESB exception database, relevant to your BizTalk Environment.

That’s it! You are set (takes about 3 minutes, definitely not more than that).

Check the below blogs to know more about BizTalk360 ESB Portal.

• Why did we build ESB Exception Management Portal in BizTalk360?

• Why did we build ESB Management Portal?

• Introducing ESB Reporting in BizTalk360

BizTalk360 is ready for BizTalk Server 2020!

For those of you who are not aware of BizTalk360, I would like to give a short intro and we are excited to announce that after working with Microsoft for the past few months, we are now fully supporting Microsoft BizTalk Server 2020 with our latest release.

Why not give BizTalk360 a try? It takes about 10 minutes to install on your BizTalk environments. Get started with the free 30 days trial.

The post Configuring ESB in BizTalk Server 2020 appeared first on BizTalk360.

The post Configuring ESB in BizTalk Server 2020 appeared first on BizTalkGurus.

I
have an insane roadmap of things to be published but if I didn’t have this week
was fertile in providing me with new content. Full week troubleshooting and
fixing issues in several clients… what an amazing week! But the best one
arrived almost on the last day.

Do
you know the feeling when you develop a solution that has been working properly
for a while and stops working for no logical reason? I bet you do. And this happened
to me this week at a client where we are using the BizTalk Server Logic App
Adapter to extend part of our logical business to the cloud. And without we
make any changes to the Logic Apps or any changes in our BizTalk Server environment
(aka no new development installed, no patch’s or hotfixes installed, no
restarts, …) everything stops to work, we were not receiving any new messages
on our Logic Apps.

When
I access to BizTalk Server environment, I realize that all the requests were
suspended with the following error:

System.ServiceModel.CommunicationException: An error occurred while making the HTTP request to https://prod-….logic.azure.com/workflows/…/triggers/manual/paths/invoke?queryparameters . This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between the client and the server. —> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. —> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. —> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
  at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)
  at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult a

The adapter failed to transmit message going to send port “LOGICAPP_SEND_PORT” with URL “https://prod-….logic.azure.com/workflows/…/triggers/manual/paths/invoke?queryparameters“. It will be retransmitted after the retry interval specified for this Send Port. Details:”System.ServiceModel.CommunicationException: An error occurred while making the HTTP request to https://prod-….logic.azure.com/workflows/…/triggers/manual/paths/invoke?queryparameters. This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case. This could also be caused by a mismatch of the security binding between the client and the server. —> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. —> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. —> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

   at System.Net.Sockets.Socket.EndReceive(IAsyncResult asyncResult)

   at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult)

   — End of inner exception stack trace —

   at System.Net.TlsStream.EndWrite(IAsyncResult asyncResult)

   at System.Net.ConnectStream.WriteHeadersCallback(IAsyncResult ar)

   — End of inner exception stack trace —

   at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)

   at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result)

   — End of inner exception stack trace —

Server stack trace:

   at System.Runtime.AsyncResult.End[TAsyncResult](IAsyncResult result)

   at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)

   at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)

   at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)

Exception rethrown at [0]:

   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

   at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)

   at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.RequestCallback(IAsyncResult result)”.

The other curious thing was that all my environments DEV, QA, and PROD were with the same symptom and all of them start at the same time which made this problem even more intriguing.

However,
I was able to connect with the adapter, see and select all the Logic Apps in my
subscription.

To
demystify if that was a problem with the adapter, I switch to the HTTP adapter
in order to try. Nevertheless, I got identical problems that made me dismiss
the idea that there could be something wrong with the adapter.

The
next step was to see if there was a network issue, maybe a firewall or proxy, which
should be because there was no intervention in the environment, but it is
always worth testing. To do that, I used one of my favorite tools, postman, and
to my surprise, everything was working fine. I was able to communicate and send
requests to all my Logic Apps in all my environments!

Cause

If you don’t are really
familiar with this type of problem, you may be pointed for a certificate issue,
but in our case, we were not using any kind of certificates to call our Logic
Apps and no additional type of authentication.

But I was sure that I had
already seen that error in the past, and I was related to security protocol (TLS
1.0 or TLS 1.2) used on the HTTPS communication and yes HTTPS because
all Logic Apps endpoints are in HTTPS.

BizTalk
Server came out-of-the-box and works very well with SSL (Secure Socket Layer)
3.0 or TLS (Transport Layer Security) 1.0, and these are the security
protocol used. New versions of BizTalk Server allow us to use TLS 1.2, but that
required extra manual configurations that we need to do in the environment and I
know that everyone is deprecating TLS 1.0 and 1.1 because of the well know vulnerabilities,
nevertheless, everything was working fine I have been doing this kind of hybrid
solution connecting with Logic Apps.

What
I discovered on the official documentation was that they say that: The
Request trigger supports only Transport Layer Security (TLS) 1.2 for incoming
calls. Outgoing calls continue to support TLS 1.0, 1.1, and 1.2.

Nevertheless,
that wasn’t true until a few days ago, and my guess is that they actually discontinue
support for TLS 1.0 and 1.1 on the incoming calls without any notice, something
that, in my opinion, you shouldn’t do.

Solution

The solution was very simple,
we just need to specify that the default security protocol on BizTalk Server is
TLS 1.2. And to do that you need:

• To
  make some changes on the registry to set TLS 1.2 as default security protocol TLS1.2;
• Or
  creating a Custom BizTalk Server behavior;

I
choose the first option, making some changes to the registry. And to accomplish
that we need to add the below DWORD values in our registry:

• On the [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSecurityProvidersSCHANNELProtocolsTLS 1.2Client]
  • Create the following DWORD (32-bit) values
    • Name: DisabledByDefault
      • Value Data: 0
    • Name: Enabled
      • Value Data: 1
• On the [HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSecurityProvidersSCHANNELProtocolsTLS 1.2Server]
  • Create the following DWORD (32-bit) values
    • Name: DisabledByDefault
      • Value Data: 0
    • Name: Enabled
      • Value Data: 1
• On the [HKEY_LOCAL_MACHINESOFTWAREMicrosoft.NETFrameworkv4.0.30319]
  • Create the following DWORD (32-bit) values
    • Name: SchUseStrongCrypto
      • Value Data: 1
• On the [HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoft.NETFrameworkv4.0.30319]
  • Create the following DWORD (32-bit) value
    • Name: SchUseStrongCrypto
      • Value Data: 1

If
you try resending a message to your Logic App, everything should work properly
again.

The post BizTalk Server Logic App Adapter: An error occurred while making the HTTP request. This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case appeared first on SANDRO PEREIRA BIZTALK BLOG.

The post BizTalk Server Logic App Adapter: An error occurred while making the HTTP request. This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case appeared first on BizTalkGurus.

Recently a
client call me reporting a strange behavior on the BizTalk Server Administration
Console. Based on what was reported to me, some updates were applied to the
server at the level of the operating system and that after installation, they
would have performed a controlled restart to the environment. However, after
the environment is back once again online when trying to access the
administrative console, they got the following error:

The snap-in performed a non-valid
operation and has been unloaded. To continue working with this snap-in, restart
MMC or try loading the snap-in again.

Just for curiosity, BizTalk Health Monitor, worked perfectly fine. And the BizTalk Server engine was working properly also. It was just a matter of UI.

Cause

I don’t really know the specific reasons that cause this problem, and to be honest, being a production environment, the important was to put everything working again. But in a simple way, this error message normally means that the MMC or one of the snap-ins, in this case, BizTalk Server Administration snap-in did not load correctly.

Restarting the machine again, or even restart
the BizTalk Server Administration console doesn’t solve the issue.

Solution

You can troubleshoot fudder this problem and use
a tool like System File Checker to scan and see if you find the root of the
issue and probably the fix.

However, the simple way to solve this is to:

• Repair
  BizTalk Server installation;

Once you repair the installation, everything
should be working fine again.

Notice: don’t forget to reinstall the last Cumulative
updates.

The post BizTalk Administration Console Error: The snap-in performed a non-valid operation and has been unloaded. To continue working with this snap-in, restart MMC or try loading the snap-in again appeared first on SANDRO PEREIRA BIZTALK BLOG.

The post BizTalk Administration Console Error: The snap-in performed a non-valid operation and has been unloaded. To continue working with this snap-in, restart MMC or try loading the snap-in again appeared first on BizTalkGurus.

Do you feel difficult to keep up to date on all the frequent updates and announcements in the Microsoft Integration platform and Azure iPaaS?

Integration weekly update can be your solution. It’s a weekly update on the topics related to Integration – enterprise integration, robust & scalable messaging capabilities and Citizen Integration capabilities empowered by Microsoft platform to deliver value to the business.

Microsoft Announcements and Updates

• OpenAPI v3 support in Azure API Management is now generally available
• Azure API Management now supports integration with Azure App Service
• Azure Blockchain development kit for Ethereum is now generally available
• New Azure DevOps features include improved Azure Pipelines security with read-only variables
• Data Factory adds schema import, connection tests, and custom sink ordering to data flows
• Azure Key Vault—Private endpoints now available in preview
• Log telemetry for your Apps using Azure Application Insights

Community Blog Posts

• BizTalk Server 2020: a new unofficial logo  by Sandro Pereira
• Configuring ESB in BizTalk Server 2020  by Sivaramakrishnan Arumugam
• BizTalk Server Logic App Adapter: An error occurred while making the HTTP request. This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case  by Sandro Pereira
• How Azure Event Grid is different from logs, alerts, change feeds and webhooks  by Tom Kerkhove
• Manage the Power Platform with the new Power Platform Administrator Role  by Kent Weare
• Guide to Currencies in the Common Data Service  by Nick Doelman
• EF Core Relationships in ASP .NET Core 3.1  by Shahed Chowdhuri
• Guidance Framework for Modernizing .NET Applications  by Gartner
• 13 API Metrics That Every Platform Team Should be Tracking by Derric Gilling

Videos

• Learn all about Open Application Model (OAM)  via Azure Friday
• Increase your productivity with blockchain data manager  via channel9

Podcasts

• AI That Helps You Code with Danny Simmons and Gustavo Soares  via .Net Rocks Podcast

How to get started with iPaaS design & development in Azure?

• Robust Cloud Integration with Azure
• Microsoft Azure for Developers: What to Use When
• Serverless Computing: The Big Picture
• Azure Logic Apps: Getting Started
• Azure Logic Apps: Fundamentals
• Microsoft Azure Developer: Creating Enterprise Logic Apps
• Microsoft Azure API Management Essentials
• Azure Functions Fundamentals
• Cloud Design Patterns for Azure: Availability and Resilience
• Architecting for High Availability in Microsoft Azure

Feedback

Hope this would be helpful. Please feel free to reach out to me with your feedback and questions.

• Twitter
• LinkedIn

The post February 10, 2020 Weekly Update on Microsoft Integration Platform & Azure iPaaS appeared first on BizTalkGurus.

Another error
and warnings, cause and solutions blog post. This time on a small issue that I got
during an application configuration in a developing environment.

Well, I
think I will not tell you anything new, but when you are generating Schemas
from a SQL database, regardless of whether they are actions directly on tables
or invoking stored procedures, a binding file is automatically created on your
BizTalk Server Visual Studio solution. And you can use it to easily create the
necessary ports to communicate with your SQL database. You don’t need to create
them manually.

On one of these occasions, as I did thousands of times before, I successfully import my binding file containing the receive ports for my SQL database. But to my surprise every time I was trying to open the port configuration to change the attributes, I was getting the following error:

Error loading properties. (System.Configuration.ConfigurationErrorsException) Unrecognized attribute ‘Attribute-Name’. Note that attribute names are case-sensitive.

For a better context, why this error was happening, I was working with the BizTalk Server 2013 R2 version.

Cause

Although I didn’t initially understand why it
happened, the error is quite clear. The attribute name, in my case ApplicationIntent
was invalid.

Only thing I was sure:

• It
  wasn’t a case-sensitive issue I was sure about that because this was an auto-generated
  binding file and the only thing I did was to change the receive port and
  receive location names

To demystify the problem, I ended up:

• Manually
  creating the receive port;
• Export
  the bindings;
• And
  compare the bindings;

And what I noticed was that the bindings were different, this last one, that was working, didn’t contain the ApplicationIntent attribute and two other additional attributes like MultiSubnetFailover attribute.

I end up realizing that, because I didn’t have access to the client and I was with limit access to my dev machines, I end up creating the Schemas and the transformations using a different version: BizTalk Server 2016.

The schemas and almost artifacts, even if you
developer in a higher version, it will work well on BizTalk Server 2013 R2, you
just need to compile with a different network. Nevertheless, I will not advise doing
that. However, the binding files are different and not compatible between these
two versions for this adapter.

Solution

The solution is easy and you have three options:

• Manually remove, fixing the binding file, for example, open in notepad and remove the ApplicationIntent=”ReadWrite”;
  • I will not recommend that approach;
  • You will find other issues that you need to solve;
• Regenerate the schemas and bindings in your correct Visual Studio solution;
  • It may give you additional work on redeploying the solution;
  • But it is the most consistent option, everything will be updated and you sure that you have all the correct resources.
• Manually create the ports on the BizTalk Server Administration Console;
  • Make sure to generate the binding files and update them in our Visual Studio solution;

The post BizTalk Administration Console Error: Unrecognized attribute ‘Attribute-Name’. Note that attribute names are case-sensitive appeared first on SANDRO PEREIRA BIZTALK BLOG.

The post BizTalk Administration Console Error: Unrecognized attribute ‘Attribute-Name’. Note that attribute names are case-sensitive appeared first on BizTalkGurus.

Are you an Integration expert? Want to get up to speed on the Microsoft Integration technologies and stay updated on their vision and road map?  Then, INTEGRATE 2020 is the answer to all these questions. The 3-day event, with speakers from the Microsoft Product Group and from the Global Integration Community, to listen to the leading Integration Specialists and learn what is coming next in integration and to network with your peers.

Any Microsoft events like the Ignite, Inspire, Build, etc will have sessions covering a wide range of technologies, which is overwhelming to some extent, whereas INTEGRATE 2020 focuses on a niche category of people interested in Microsoft Integration space.

Last year INTEGRATE edition was by far the most successful one which means the conference is only getting better year after year. This is undoubtedly the premier event focusing on the Microsoft integration space. Therefore, it is key for everyone in the integration space to attend this event to know the interesting things that are happening and learn what’s coming next from the Microsoft Product Group.

Here I wish to express why attending Integrate 2020 in-person is so important:

What’s Microsoft Integration Roadmap?

Here is a list of important announcements made at INTEGRATE by the Microsoft Product team. It would be more valuable for you to connect with the product team over networking to discuss more on the benefits, challenges, and considerations to be followed for these important announcements.

INTEGRATE 2019 – Paul Larsen, Principal Program Manager at Microsoft made the big announcement “BizTalk Server 2020” and he also announced it will be released at the end of 2019. BizTalk Server 2020 is not just a simple software update it’s a game-changer and beginning of a new era. BizTalk Server 2020 is Microsoft’s commitment to existing customers who invested in BizTalk Server. The new BizTalk Server version will be supported until 2030

Also, the Logic Apps team announced the public preview for Rosetta Net and a few real use cases of Rosetta Net.

INTEGRATE 2018 – Jon Fancey, Principal Program Manager at Microsoft in his Keynote mentioned the need to embrace change towards cloud adoption. The whole of the conference in 2018 was about what’s the future with hybrid and cloud integrations. There were a lot of announcements from Microsoft on introduction towards Azure Integration Services, Logic Apps, Function, etc.

Paul Larsen announced BizTalk Server 2016 Cumulative Update (CU) 5. He also showed the traditional BizTalk Server life cycle diagram that showed that just a month is left ahead for support to end for BizTalk Server 2013 and BizTalk Server 2013 R2.

Clemens Vasters – Principal Architect announced Event Hubs for the Kafka Ecosystem.

INTEGRATE 2017 – Jim Harrer, Principal Group Program Manager at Microsoft Pro Integration team emphasized how Microsoft brings intelligence to its Hybrid Integration Platform. Jim showed the Pro Integration team’s year in review showing how they have progressed as a team in the 4 main departments – Logic Apps, BizTalk, Host Integration Server, and API Management.

INTEGRATE 2016 – Jim Harrer, Program Manager of the Pro-Integration group at Microsoft announced Microsoft’s integration vision and road map to provide a unified integration experience across on-premises and cloud.

Now, are you excited about the important Microsoft updates at INTEGRATE 2020? We are excited as much as you are!

Network and Explore an Opportunity for Partnerships

INTEGRATE is the biggest and best opportunity to build a strong network and explore the opportunities to build a strong business. You certainly not want to miss out on the best possible opportunity to grow your company and network with the community.

Pricing

We already opened registrations for INTEGRATE 2020. The early bird registrations for tickets closes on March 31st. Also, given the Public Holiday on June 1st in parts of Europe and our wish to accommodate attendees enjoying a long weekend, all the Microsoft Speaker sessions will take place on Day 2 and Day 3. We have now made available a 2 Day Pass Option for June 2nd and June 3rd only.

If you are planning to attend INTEGRATE 2020, then go ahead and register as this will be the best ticket sale of the year. Be quick as when they’re gone, they’re gone.

Sponsorship

We are also opening sponsorship opportunities for this event. There are sponsorship packages available at different levels. If you are interested to sponsor this event, please contact us at contact@biztalk360.com.

Join with other leading consulting and ISV companies as sponsors:

Are you still not convinced? Don’t miss out, register today and take the early bird offer.

Don’t miss out on the conference which is highly focused on Microsoft Integration space. We look forward to planning your trip to London and joining the community in June.

The post Why you should attend INTEGRATE 2020? appeared first on BizTalk360.

The post Why you should attend INTEGRATE 2020? appeared first on BizTalkGurus.

Introduction

During our last premier event, INTEGRATE 2019, the Microsoft product group announced the new version release of BizTalk Server 2020. This version has been released in mid-January 2020. A most awaited moment comes into real; BizTalk 2020 is public now! To know more about the exciting new features, take a look at our Founder Saravana Kumar blog “BizTalk Server 2020 – Why it’s a Game-Changer?”.

In this blog post, I will be covering the new features shipped in BizTalk Server 2020, in terms of Operation and Administration. Yes, this version brought in quite a number of new capabilities to make the life of admin/support people easier. Let’s take a look at the features one by one in detail in the coming sections.

Scheduling

In BizTalk Server, there is an option available to schedule receiving or transmitting the messages on certain days and hours. However, there is no scheduling available to specify the preferred time zones and at a specific time on a daily, weekly or monthly basis. Therefore, the administrator relayed on other tricks to achieve this business scenario as below:

1. Windows Task Scheduler – To drop a file to the specified Receive Location
2. SQL Adapter – Implementing a simple stored procedure that creates a “dummy” message that initiates the process
3. BizTalk Scheduled Task Adapter – An in-process receive adapter that executes a prescribed task on a daily, weekly or monthly schedule.

Advanced Scheduling

Now with BizTalk Server 2020, the new advanced scheduling comprises all the options which administrators wanted for scheduling.

New Options:

1. The preferred time zone can be set based on the business scenario
2. Automatically adjust for daylight saving time
3. Recurrence options like daily, weekly, and monthly

Local time can be confusing, as all the places on earth use their own local time for the smooth functioning of the large-scale business spread across the world. (Ex: companies with abroad partners, railways, ). Until the previous versions, there won’t be any option available to set the preferred time zone for message processing. With this new option, the time zone can be set according to the business needs along with the automatic setting daylight-saving.

Another exciting capability is recurrence. To achieve this formerly, Admins used various tricks to process the messages. With this new capability, they can set daily, weekly and monthly schedules as per the needs.

1. Daily – Configure the number of recurring days and from which date the recurrence will be active
2. Weekly – Configure the number of recurring days, from when the recurrence will be active and on which weekdays the recurrence must be active
3. Monthly – Configure which months and which days the recurrence should take place

Backup to Azure Blob Storage

To align with the latest trend, BizTalk Server 2020 has this exciting capability to extend its support in hybrid solutions. With this feature, you can configure the BizTalk Server job to back up your BizTalk databases and log files into the Azure Blob storage account.

To configure this job, you will need to:

1. Create a general-purpose Azure Storage account
2. Create a container within your Blob Storage account
3. Create stored access policy and shared access storage
4. Create SQL Credential using the SAS

Create a general-purpose Azure Storage account

An Azure Storage account contains all your Azure Storage data where all the saved data is highly available, secure, and scalable at any point in time. Then the storage account is ready to create the container.

Creating a Container

All the database backup files are stored in the Blobs. For that, you must first create a container.

Once the container is created, click on the ellipsis button at the end of the row and look for the property “Container properties”.

In the opened window, copy the URL value as highlighted in the below screenshot. This URL will be used to create the credentials in the SQL Server and as well as configure the backup jobs.

Shared Access Signature

A shared access signature is a URI that grants restricted access rights to the container in the Azure Storage account. A stored access policy provides an additional level of control over shared access signatures. When using this, you need to create a policy on a container with at least read, write and list rights.

In the Azure Storage account you have created, look for the menu “Shared access signature” and click on the “Generate SAS and connection string”, as shown in the below screenshot.

All the connection strings and URLs will be generated and listed in the below section. There you require the SAS token to create the credentials.

Create SQL Credential

This is the final step, where you need to create a credential in SQL Server in order to connect with the blob storage. As mentioned in the screenshot, Open the new query and click on the menu “Azure Storage”.

In the next wizard, you are prompted to sign in the respective Azure account where the container is created. Once after the sign-in, select the respective storage account and the container and click ok.

After the successful sign-in, execute the below query with the correct parameters.

Once the query is successfully executed just navigate to Security -> Credentials. You can see the new shared access signature in the credential folder. Now everything is set for the database backup to Azure Blob.

Once the credentials are created, you need to configure the BizTalk Server backup job as mentioned in this article.

After the successful configuration, you need to run the backup job. Once the execution is completed, all the BizTalk Server database backups are available in the Blobs as you see in the below screenshot.

Audit Log

Until the previous versions of BizTalk Server, it is a completely black box for the administrators where they are not sure about who does what in the environment since all support persons have elevated access to the BizTalk and SQL Servers and no auditing is taking place.

BizTalk Server 2020 can audit the application and its artifact activities performed by the users. All the auditing activities are stored in the BizTalk Management DB -> bts_auditlog table.

Admins can get an insight about,

1. Who has done the action?
2. In which Server with the Artifact id, artifact name, and the corresponding operation
3. Payload information
4. At which specific date and time the particular action took place

The new audit API lists all the auditing activities performed by the users. The result will be returned in the JSON format.

After installing and configuring the BizTalk Environment, the next is to enable the Global level Audit Management operations, as shown in the picture.

The following are the detailed list of the activities audited by the BizTalk Server,

Applications

Receive Ports

Receive Locations

Orchestrations

Send Port Groups

Service Instances

Binding file importing activity is audited as well.

Artifacts which don’t have auditing capabilities:

Note: Only the admin users can view the auditing activities performed by other users.

New Read-Only Operator Role

The new role “BizTalk Server Read-Only Users”, is completely providing read-only access to the users. This role will be useful to facilitate the dev-ops scenario.

With this new role, users are restricted to perform actions against,

1. Application and Artifacts
2. Service Instances
3. Changing port configuration

If a user, who is in the Read-only Operator role, tries to do any actions, these actions will be restricted by BizTalk Server and the user will get an error message like below.

When the user tries to change the host instance status, the error message will be different, as shown below.

Group Managed Service Accounts

Group managed service provides automatic password management. The main reason behind this is to delegate the management of passwords to other administrators.  When this option is enabled, users don’t need to provide the passwords to handle the services. This specific option will be shown when you run the BizTalk Server custom configuration. The features support gMSA have a “Is gMSA account” setting. Once this setting is enabled, the password property disables.

gMSA is supported for the features,

1. BizTalk Runtime
2. Business Rules Engine
3. BAM Tool
4. Rest API
5. BizTalk TMS

Note: gMSA is not available when BizTalk is configured with a Basic Configuration.

You can find more information about gMSA in this article.

Conclusion

Microsoft released many useful features to ease the Operation and Administration capability for support/admin people. BizTalk Server 2020 promises the on-going commitment of Microsoft in this platform. We are in the process of creating some great guides and materials related to BizTalk Server 2020. (Ex: Detailed upgrade guide from previous versions). If you are interested, comment below with your answers for the following two questions along with your mail id, we will keep you in the loop.

1. What version of BizTalk Server are you using?
2. Is BizTalk Server 2020 migration in your scope?

Here are a few detailed blogs on BizTalk Server 2020, hope you will find them useful.

• Why is BizTalk Server 2020 a game-changer
• What’s new in BizTalk Server 2020
• Configuring ESB in BizTalk Server 2020

The post BizTalk Server 2020 – Operations and Administration Capability appeared first on BizTalk360.

The post BizTalk Server 2020 – Operations and Administration Capability appeared first on BizTalkGurus.

Nino Crudele just published another free whitepaper about Azure Reconnaissance and Scanning for Ethical Hackers and Special Ops Team. It is a 25 pages whitepaper that will provide you with a quick and practical guide full of tools and techniques for scanning and reconnaissance in Azure to Ethical Hackers and Special Ops Team that want to learn or know a little more. You shouldn’t miss this opportunity!

Once again, I would like to take this opportunity to say thanks to Nino Crudele for inviting me to be his technical reviewer for this whitepaper. I never learn to say no to him, it is always a crazy nightmare but a delightful one. And I’m already waiting to our next challenge.

Nino Crudele is a freelance living in the United Kingdom. He is Global Azure Lead and Cybersecurity expert in Hexagon Manufacturing Intelligence, a global manufacturing company. He is responsible for leading the Microsoft Azure Cloud area, supporting and advising the Company to select the most appropriate cloud strategies and solutions from high-level design to implementation and Security is one of my top priorities.

What to expect about  Azure Reconnaissance and Scanning for Ethical Hackers and Special Ops Team whitepaper

This whitepaper will provide:

• The final objective of a Penetration Testing project is to provide useful information to resolve the errors identified before they can be used for malicious purposes.
• How to identify our attack surface by researching, collecting, and organizing as much information as possible about a potential attack target. Then it will seek ways that could be exploited to get into the systems.
• And of course, like any good Penetration Testing project should be, how to provide useful information to resolve the errors identified before they can be used for malicious purposes. 

Where you can download it

The whitepaper is completely free and you can download it here:

• https://ninocrudele.com/azure-reconnaissance-and-scanning-for-ethical-hackers-and-special-ops-team-free-whitepaper

The post Azure Reconnaissance and Scanning for Ethical Hackers and Special Ops Team [free whitepaper] By Nino Crudele appeared first on SANDRO PEREIRA BIZTALK BLOG.

The post Azure Reconnaissance and Scanning for Ethical Hackers and Special Ops Team [free whitepaper] By Nino Crudele appeared first on BizTalkGurus.

Back to one of my favorite topics: Errors and Warnings, Causes, and Solutions since I have several issues to report in my internal OneNote. But in fact, this one happened today while I was implementing a new RosettaNet PIP on a client… nevertheless, this is not specific to RosettaNet.

I
was making a small improvement to an existing process/project to allow specific
orchestrations to be activated based on some properties promoted from the
message by applying a filter on the activate Receive Message shape. Everything
was going peacefully well until I tried to redeploy the Visual Studio solution.
Once I try to redeploy the BizTalk Server Visual Studio solution from Visual
Studio, I got the following error:

Error The “MapperCompiler” task failed unexpectedly.

System.UnauthorizedAccessException: Access to the path ‘C:……MapsmapNotifyOfShipmentReceipt_To_PIP4B2.btm.cs’ is denied.

   at Microsoft.VisualStudio.BizTalkProject.Compiler.MapCompiler.Compile(BizTalkBuildSnapshot buildSnapshot, IEnumerable`1 mapFilesToCompile, IEnumerable`1 schemaFiles, List`1& generatedCodeFiles, List`1& xsltFiles)

   at Microsoft.VisualStudio.BizTalkProject.BuildTasks.MapperCompiler.Execute()

   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()

   at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext() EAI.RosettaNet.4B2.

The funny part was that this was a small change that I did in an existing solution that already was running fine in the environment… and the change was a small improvement in the orchestration, not on the map!

Cause

Well,
I don’t know why the compiler decided to pick the mapper to complain. But This
issue is not related to any kind of maps you may have in your solution.

And
yes, the user that I was using to open, and build the solution had full rights
to access the file in question, all full rights to deploy stuff to the BizTalk
Server environment.

There are several possible causes for you to get such Access Denied errors when deploying BizTalk solutions directly from Visual Studio. Most common is that you don’t have the right BizTalk privileges to deploy artifacts, or in other words, you are not a local Administrator.

But most of the time is simpler than that and indeed is related to additional securities setting present in recent Windows Server versions. For you to be able to successfully deploy a BizTalk Server solution directly from Visual Studio, you must run Visual Studio as an Administrator, or with elevated permissions, because BizTalk assemblies need to be deployed into the GAC. What normally happens, is that if you have User Account Control (UAC) activated, or sometimes even deactivated, there are some additional securities setting present in recent Windows Server versions that, by default, doesn’t run Visual Studio with elevated permissions.

This
was indeed one of these cases, Visual Studio was not open with elevated
permissions.

Solution

The quick solution is for you to run
Visual Studio as an Administrator by simply run below step:

• Right-click
  under Visual Studio and choose Run as administrator option.

The problem with this approach is that
you need to remember yourself to do it every time you want to run Visual Studio.
Otherwise, the next time you try to deploy the solution, it will fail again
with the same error.

You may find more how to configure Visual Studio to run with elevated permissions as administrator by default here: https://blogs.biztalk360.com/biztalk-server-tips-and-tricks-configure-visual-studio-to-run-with-elevated-permissions-as-administrator/

If you try now to deploy your solution, you will see that this problem goes aways and you will be able to deploy it successfully (assuming that the solution does not actually have errors).

The post BizTalk Visual Studio Deploy Issue: The “MapperCompiler” task failed unexpectedly. Access to the path ‘…’ is denied appeared first on SANDRO PEREIRA BIZTALK BLOG.

The post BizTalk Visual Studio Deploy Issue: The “MapperCompiler” task failed unexpectedly. Access to the path ‘…’ is denied appeared first on BizTalkGurus.