A journey to green labelling

by Contributed | Apr 6, 2021 | Technology

This article is contributed. See the original author and article here.

Before joining Microsoft and falling in love with the technology and platform and possibilities that the Azure public cloud provides, I was (and for a 2-digit number of years, gosh) an expert in the contact center and telco market: the technology that companies use to provide customer service on their products. Lately, my focus has been mostly on the customer experience, as the power clearly shifted over the years from the technology and technologists to the end-users and how their perception of experience was contributing to the success (or failure) of a company.

As a part of my customer experience work, I researched how to apply the idea of a Net Promoter Score. I was really drawn to the technique of using a single question to define if something was going to succeed or fail. But the more I saw companies using NPS, the more I realized this approach omitted an entire important set of choices a company can make: green choices.

While a customer is navigating your virtual space, such as a website, mobile app or even your physical store, there is nothing that communicates a green option for the product or the technology that is used to bring that product to the end user.

When I think about my e-commerce experiences, which started back in the year 2000, the closest example to a green option was the energy consumption label on some appliances. I searched the web and found the EU energy consumption labels only apply to the following categories: appliances (dishwashers, refrigerators, etc.), air conditioners, light bulbs, cars, televisions, houses, and tires. When buying a large appliance, this label helped me, as a consumer, to pick the one that was more energy efficient. While choosing an appliance that consumes less energy could be framed as a “greener” choice, in most cases, it’s framed more like a “cost savings” choice.

The point is we need to start doing something at all levels, and little changes can lead to a great impact if we concentrate our efforts in the same direction. Consumers make many small choices every day on the products they buy. In many cases, they have little or no knowledge about the carbon impact those choices have.

But what if the end-user could be more knowledgeable about the carbon impact of their purchases? Thinking of my own experiences as a user, I’d like to see in the foreseeable future something like:

• An energy consumption label (with street-light color code and A to F rating) on computers and devices.


• How recyclable a device is.


• Sustainable software, knowing that the software used in the device was created with sustainability paths and best practices and will allow the user choices on energy consumption.


• Active and real-time information from the energy suppliers about the carbon impact of the consumed energy in my house. A device might be labeled as low carbon impact, but knowing from the energy supplier when is the greenest moment (i.e. the time of day when energy is produced with alternative sources) to charge my device is something that needs to be done at user level and is highly dependent on the location.

Omitting carbon impact information from a product undervalues a customer’s desire to reduce their carbon footprint through their purchasing choices. Adding this labeling opens up a lot of potential for both consumers and companies to make more sustainable choices. For companies, this could even mean leveraging “green loyalty”, which is a marketing technique that can help people feel more active in their consumers’ choices on sustainability.

By Sandra Pallier

Today, a customer has the ability to make some green choices, such as conserving water, recycling, using reusable items and shopping bags, etc. Adding labeling around carbon impact would give customers significantly more choice. Despite the upfront challenges in providing this information, carbon impact labeling would allow products with a lower carbon impact to differentiate themselves. This could produce better products as well as a reduction in carbon emissions, and an overall education of technology users to search for the greener option.

Issues with LogicApp RosettaNet connector

by Contributed | Apr 6, 2021 | Technology

This article is contributed. See the original author and article here.

The problem:

If you use LogicApp Rosettanet connector(i.e: from RN Encode/Decode templates) to send/receive documents to/from external Rosettanet systems like BizTalk server, you may meet different MIME decoding/disassembler errors like the following:

Receive pipeline rejected incoming message

due to the following RNIF exception:

UNP.PRMB.VALERR : A failure occurred while validating the preamble.                            

Details:

Invalid character in the given encoding. Line 10, position 13.

Analysis:

The following is an original message from LogicApp Rosettanet connector:

MIME-Version: 1.0

Content-Type: application/xml

Content-Transfer-Encoding: base64

Content-Description: Preamble_MP

Content-Disposition: attachment;           filename=”86822f5b5dc84dca974635740be5e359″

Content-Location: RN-Preamble

77u/PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhRE9DVFlQRSBQcmVhbWJsZSBTWVNURU0gIlByZWFtYmxlX01TX1YwMl8wMC5kdGQiW10+DQo8UHJlYW1ibGU+DQogIDxzdGFuZGFyZE5hbWU+DQogICAgPEdsb2JhbEFkbWluaXN0ZXJpbmdBdXRob3JpdHlDb2RlPlJvc2V0dGFOZXQ8L0dsb2JhbEFkbWluaXN0ZXJpbmdBdXRob3JpdHlDb2RlPg0KICA8L3N0YW5kYXJkTmFtZT4NCiAgPHN0YW5kYXJkVmVyc2lvbj4NCiAgICA8VmVyc2lvbklkZW50aWZpZXI+VjAyLjAwPC9WZXJzaW9uSWRlbnRpZmllcj4NCiAgPC9zdGFuZGFyZFZlcnNpb24+DQo8L1ByZWFtYmxlPg==

–_0ea1da80-4cfa-4c0a-9047-c16e3d663d45_

Content-Type: application/xml

Content-Transfer-Encoding: base64

Content-Description: DeliveryHeader_MP

Content-Disposition: attachment;           filename=”a09bdee8c9f246faa8b15b5931fc4c4e”

Content-Location: RN-Delivery-Header

77u/PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhRE9DVFlQRSBEZWxpdmVyeUhlYWRlciBTWVNURU0gIkRlbGl2ZXJ5SGVhZGVyX01TX1YwMl8wMC5kdGQiW10+DQo8RGVsaXZlcnlIZWFkZXI+DQogIDxpc1NlY3VyZVRyYW5zcG9ydFJlcXVpcmVkPg0KICAgIDxBZmZpcm1hdGlvbkluZGljYXRvcj5ZZXM8L0FmZmlybWF0aW9uSW5kaWNhdG9yPg0KICA8L2lzU2VjdXJlVHJhbnNwb3J0UmVxdWlyZWQ+DQogIDxtZXNzYWdlRGF0ZVRpbWU+DQogICAgPERhdGVUaW1lU3RhbXA+MjAyMTAzMThUMTAyMDEyLjU5OVo8L0RhdGVUaW1lU3RhbXA+DQogIDwvbWVzc2FnZURhdGVUaW1lPg0KICA8bWVzc2FnZVJlY2VpdmVySWRlbnRpZmljYXRpb24+DQogICAgPFBhcnRuZXJJZGVudGlmaWNhdGlvbj4NCiAgICAgIDxkb21haW4+DQogICAgICAgIDxGcmVlRm9ybVRleHQ+RFVOUzwvRnJlZUZvcm1UZXh0Pg0KICAgICAgPC9kb21haW4+DQogICAgICA8R2xvYmFsQnVzaW5lc3NJZGVudGlmaWVyPjIwMTYyMDE2MjwvR2xvYmFsQnVzaW5lc3NJZGVudGlmaWVyPg0KICAgICAgPGxvY2F0aW9uSUQ+DQogICAgICAgIDxWYWx1ZT5DWUVBSTIwMTY8L1ZhbHVlPg0KICAgICAgPC9sb2NhdGlvbklEPg0KICAgIDwvUGFydG5lcklkZW50aWZpY2F0aW9uPg0KICA8L21lc3NhZ2VSZWNlaXZlcklkZW50aWZpY2F0aW9uPg0KICA8bWVzc2FnZVNlbmRlcklkZW50aWZpY2F0aW9uPg0KICAgIDxQYXJ0bmVySWRlbnRpZmljYXRpb24+DQogICAgICA8ZG9tYWluPg0KICAgICAgICA8RnJlZUZvcm1UZXh0PkRVTlM8L0ZyZWVGb3JtVGV4dD4NCiAgICAgIDwvZG9tYWluPg0KICAgICAgPEdsb2JhbEJ1c2luZXNzSWRlbnRpZmllcj4wNTIzNTQwNjk8L0dsb2JhbEJ1c2luZXNzSWRlbnRpZmllcj4NCiAgICAgIDxsb2NhdGlvbklEPg0KICAgICAgICA8VmFsdWU+QVpVUkU8L1ZhbHVlPg0KICAgICAgPC9sb2NhdGlvbklEPg0KICAgIDwvUGFydG5lcklkZW50aWZpY2F0aW9uPg0KICA8L21lc3NhZ2VTZW5kZXJJZGVudGlmaWNhdGlvbj4NCiAgPG1lc3NhZ2VUcmFja2luZ0lEPg0KICAgIDxJbnN0YW5jZUlkZW50aWZpZXI+YzkzOTQwOGQwY2ZjNGI5YmIyY2JiZTNiMWU1MjgyNTc8L0luc3RhbmNlSWRlbnRpZmllcj4NCiAgPC9tZXNzYWdlVHJhY2tpbmdJRD4NCjwvRGVsaXZlcnlIZWFkZXI+

–_0ea1da80-4cfa-4c0a-9047-c16e3d663d45_

Content-Type: application/xml

Content-Transfer-Encoding: base64

Content-Description: RN-Service-Header

Content-Disposition: attachment;           filename=”de7c1086c0774fb9b32b8cea930cb53e”

Content-Location: RN-Service-Header

77u/PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhRE9DVFlQRSBTZXJ2aWNlSGVhZGVyIFNZU1RFTSAiU2VydmljZUhlYWRlcl9NU19WMDJfMDAuZHRkIltdPg0KPFNlcnZpY2VIZWFkZXI+DQogIDxQcm9jZXNzQ29udHJvbD4NCiAgICA8QWN0aXZpdHlDb250cm9sPg0KICAgICAgPEJ1c2luZXNzQWN0aXZpdHlJZGVudGlmaWVyPkRpc3RyaWJ1dGUgQXN5bmNocm9ub3VzIFRlc3QgTm90aWZpY2F0aW9uPC9CdXNpbmVzc0FjdGl2aXR5SWRlbnRpZmllcj4NCiAgICAgIDxNZXNzYWdlQ29udHJvbD4NCiAgICAgICAgPGZyb21Sb2xlPg0KICAgICAgICAgIDxHbG9iYWxQYXJ0bmVyUm9sZUNsYXNzaWZpY2F0aW9uQ29kZT5Jbml0aWF0b3I8L0dsb2JhbFBhcnRuZXJSb2xlQ2xhc3NpZmljYXRpb25Db2RlPg0KICAgICAgICA8L2Zyb21Sb2xlPg0KICAgICAgICA8ZnJvbVNlcnZpY2U+DQogICAgICAgICAgPEdsb2JhbEJ1c2luZXNzU2VydmljZUNvZGU+SW5pdGlhdG9yIFNlcnZpY2U8L0dsb2JhbEJ1c2luZXNzU2VydmljZUNvZGU+DQogICAgICAgIDwvZnJvbVNlcnZpY2U+DQogICAgICAgIDxNYW5pZmVzdD4NCiAgICAgICAgICA8bnVtYmVyT2ZBdHRhY2htZW50cz4NCiAgICAgICAgICAgIDxDb3VudGFibGVBbW91bnQ+MDwvQ291bnRhYmxlQW1vdW50Pg0KICAgICAgICAgIDwvbnVtYmVyT2ZBdHRhY2htZW50cz4NCiAgICAgICAgICA8U2VydmljZUNvbnRlbnRDb250cm9sPg0KICAgICAgICAgICAgPEFjdGlvbklkZW50aXR5Pg0KICAgICAgICAgICAgICA8R2xvYmFsQnVzaW5lc3NBY3Rpb25Db2RlPkFzeW5jaHJvbm91cyBUZXN0IE5vdGlmaWNhdGlvbiBBY3Rpb248L0dsb2JhbEJ1c2luZXNzQWN0aW9uQ29kZT4NCiAgICAgICAgICAgIDwvQWN0aW9uSWRlbnRpdHk+DQogICAgICAgICAgPC9TZXJ2aWNlQ29udGVudENvbnRyb2w+DQogICAgICAgIDwvTWFuaWZlc3Q+DQogICAgICAgIDx0b1JvbGU+DQogICAgICAgICAgPEdsb2JhbFBhcnRuZXJSb2xlQ2xhc3NpZmljYXRpb25Db2RlPlJlc3BvbmRlcjwvR2xvYmFsUGFydG5lclJvbGVDbGFzc2lmaWNhdGlvbkNvZGU+DQogICAgICAgIDwvdG9Sb2xlPg0KICAgICAgICA8dG9TZXJ2aWNlPg0KICAgICAgICAgIDxHbG9iYWxCdXNpbmVzc1NlcnZpY2VDb2RlPlJlc3BvbmRlciBTZXJ2aWNlPC9HbG9iYWxCdXNpbmVzc1NlcnZpY2VDb2RlPg0KICAgICAgICA8L3RvU2VydmljZT4NCiAgICAgIDwvTWVzc2FnZUNvbnRyb2w+DQogICAgPC9BY3Rpdml0eUNvbnRyb2w+DQogICAgPEdsb2JhbFVzYWdlQ29kZT5Qcm9kdWN0aW9uPC9HbG9iYWxVc2FnZUNvZGU+DQogICAgPHBpcENvZGU+DQogICAgICA8R2xvYmFsUHJvY2Vzc0luZGljYXRvckNvZGU+MEMxPC9HbG9iYWxQcm9jZXNzSW5kaWNhdG9yQ29kZT4NCiAgICA8L3BpcENvZGU+DQogICAgPHBpcEluc3RhbmNlSWQ+DQogICAgICA8SW5zdGFuY2VJZGVudGlmaWVyPmQ0MmI3YzhhLTY4NGYtNGY4MS1iZjg3LTU1NDQwZWE5ZTJhMjwvSW5zdGFuY2VJZGVudGlmaWVyPg0KICAgIDwvcGlwSW5zdGFuY2VJZD4NCiAgICA8cGlwVmVyc2lvbj4NCiAgICAgIDxWZXJzaW9uSWRlbnRpZmllcj5SMDEuMDI8L1ZlcnNpb25JZGVudGlmaWVyPg0KICAgIDwvcGlwVmVyc2lvbj4NCiAgICA8UXVhbGl0eU9mU2VydmljZVNwZWNpZmljYXRpb24+DQogICAgICA8UXVhbGl0eU9mU2VydmljZUVsZW1lbnQ+DQogICAgICAgIDxRdWFsaXR5T2ZTZXJ2aWNlQ2xhc3NpZmljYXRpb25Db2RlPkNhbm5vdEJlRW1wdHk8L1F1YWxpdHlPZlNlcnZpY2VDbGFzc2lmaWNhdGlvbkNvZGU+DQogICAgICAgIDxWYWx1ZT5DYW5ub3RCZUVtcHR5PC9WYWx1ZT4NCiAgICAgIDwvUXVhbGl0eU9mU2VydmljZUVsZW1lbnQ+DQogICAgPC9RdWFsaXR5T2ZTZXJ2aWNlU3BlY2lmaWNhdGlvbj4NCiAgICA8S25vd25Jbml0aWF0aW5nUGFydG5lcj4NCiAgICAgIDxQYXJ0bmVySWRlbnRpZmljYXRpb24+DQogICAgICAgIDxkb21haW4+DQogICAgICAgICAgPEZyZWVGb3JtVGV4dD5EVU5TPC9GcmVlRm9ybVRleHQ+DQogICAgICAgIDwvZG9tYWluPg0KICAgICAgICA8R2xvYmFsQnVzaW5lc3NJZGVudGlmaWVyPjA1MjM1NDA2OTwvR2xvYmFsQnVzaW5lc3NJZGVudGlmaWVyPg0KICAgICAgICA8bG9jYXRpb25JRD4NCiAgICAgICAgICA8VmFsdWU+QVpVUkU8L1ZhbHVlPg0KICAgICAgICA8L2xvY2F0aW9uSUQ+DQogICAgICA8L1BhcnRuZXJJZGVudGlmaWNhdGlvbj4NCiAgICA8L0tub3duSW5pdGlhdGluZ1BhcnRuZXI+DQogIDwvUHJvY2Vzc0NvbnRyb2w+DQo8L1NlcnZpY2VIZWFkZXI+

–_0ea1da80-4cfa-4c0a-9047-c16e3d663d45_

Content-Type: application/xml;

                  charset=”utf-8″

Content-Transfer-Encoding: base64

Content-Description: ServiceContent_MP

Content-Disposition: attachment;           filename=”377ffd9bfb4c45dba5fb7779afada257″

Content-Location: RN-Service-Content

<?xml version=”1.0″ encoding=”UTF-8″ ?>

<!DOCTYPE Pip0C1AsynchronousTestNotification SYSTEM “0C1_MS_R01_02_AsynchronousTestNotification.dtd”>

<Pip0C1AsynchronousTestNotification>

                  <AsynchronousTest></AsynchronousTest>

                  <fromRole>

                                    <PartnerRoleDescription>

                                                      <ContactInformation>

                                                                        <contactName>

                                                                                          <FreeFormText xml:lang=”EN”>John Doe Sender</FreeFormText>

                                                                        </contactName>

                                                                        <EmailAddress>jdoesender@johndoe.com</EmailAddress>

                                                                        <facsimileNumber>

                                                                                          <CommunicationsNumber>000.000.0001</CommunicationsNumber>

                                                                        </facsimileNumber>

                                                                        <telephoneNumber>

                                                                                          <CommunicationsNumber>000.000.0001</CommunicationsNumber>

                                                                        </telephoneNumber>

                                                      </ContactInformation>

                                              <GlobalPartnerRoleClassificationCode>Initiator</GlobalPartnerRoleClassificationCode>

                                                      <PartnerDescription>

                                                                        <BusinessDescription>

                                                                                          <GlobalBusinessIdentifier>123456783</GlobalBusinessIdentifier>

                                                                                          <GlobalSupplyChainCode>Information Technology</GlobalSupplyChainCode>

                                                                        </BusinessDescription>

                                                                        <GlobalPartnerClassificationCode>Warehouser</GlobalPartnerClassificationCode>

                                                      </PartnerDescription>

                                    </PartnerRoleDescription>

                  </fromRole>

                  <GlobalDocumentFunctionCode>Request</GlobalDocumentFunctionCode>

                  <thisDocumentGenerationDateTime>

                                    <DateTimeStamp>20040122T073935.737Z</DateTimeStamp>

                  </thisDocumentGenerationDateTime>

                  <thisDocumentIdentifier>

                    <ProprietaryDocumentIdentifier>20040122T073935.737Z</ProprietaryDocumentIdentifier>

                  </thisDocumentIdentifier>

                  <toRole>

                                    <PartnerRoleDescription>

                                                      <ContactInformation>

                                                                        <contactName>

                                                                                          <FreeFormText xml:lang=”EN”>John Doe Receiver</FreeFormText>

                                                                        </contactName>

                                                                        <EmailAddress>jdoereceiver@johndoe.com</EmailAddress>

                                                                        <facsimileNumber>

                                                                                          <CommunicationsNumber>000.000.0002</CommunicationsNumber>

                                                                        </facsimileNumber>

                                                                        <telephoneNumber>

                                                                                          <CommunicationsNumber>000.000.0002</CommunicationsNumber>

                                                                        </telephoneNumber>

                                                      </ContactInformation>

                                         <GlobalPartnerRoleClassificationCode>Responder</GlobalPartnerRoleClassificationCode>

                                                      <PartnerDescription>

                                                                        <BusinessDescription>

                                                                                          <GlobalBusinessIdentifier>123456784</GlobalBusinessIdentifier>

                                                                                          <GlobalSupplyChainCode>Information Technology</GlobalSupplyChainCode>

                                                                        </BusinessDescription>

                                                                        <GlobalPartnerClassificationCode>End User</GlobalPartnerClassificationCode>

                                                      </PartnerDescription>

                                    </PartnerRoleDescription>

                  </toRole>

</Pip0C1AsynchronousTestNotification>

–_0ea1da80-4cfa-4c0a-9047-c16e3d663d45_–

Below is a modified message which can be accepted by BizTalk:

POST http://xx.xx.xx.xx/BTARNHttpReceive/BTSHTTPReceive.dll?xRNResponseType=async HTTP/1.1

Host: xx.xx.xx.xx

Content-Length: 8573

Expect: 100-continue

Connection: Keep-Alive

MIME-Version: 1.0

MIME-Version: 1.0

Content-Type: multipart/related; start=a1b66a8d58d34adb81d17737ec2b2819;

                  type=”application/xml”; boundary=”_410bf7bd-d294-4c7e-9c17-0bf85b7890d2_”

–_410bf7bd-d294-4c7e-9c17-0bf85b7890d2_

MIME-Version: 1.0

Content-Type: application/xml

Content-Transfer-Encoding: base64

Content-ID: afafcd4ecb04489cbed76f7e7a0e0492

Content-Description: Preamble_MP

Content-Disposition: attachment;           filename=”df9591d3f63e465bbefc37bcff854d47″

Content-Location: RN-Preamble

77u/PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhRE9DVFlQRSBQcmVhbWJsZSBTWVNURU0gIlByZWFtYmxlX01TX1YwMl8wMC5kdGQiW10+DQo8UHJlYW1ibGU+DQogIDxzdGFuZGFyZE5hbWU+DQogICAgPEdsb2JhbEFkbWluaXN0ZXJpbmdBdXRob3JpdHlDb2RlPlJvc2V0dGFOZXQ8L0dsb2JhbEFkbWluaXN0ZXJpbmdBdXRob3JpdHlDb2RlPg0KICA8L3N0YW5kYXJkTmFtZT4NCiAgPHN0YW5kYXJkVmVyc2lvbj4NCiAgICA8VmVyc2lvbklkZW50aWZpZXI+VjAyLjAwPC9WZXJzaW9uSWRlbnRpZmllcj4NCiAgPC9zdGFuZGFyZFZlcnNpb24+DQo8L1ByZWFtYmxlPg==

–_410bf7bd-d294-4c7e-9c17-0bf85b7890d2_

Content-Type: application/xml

Content-Transfer-Encoding: base64

Content-ID: 9eeecf9805834e07a01e5fa893e54472

Content-Description: DeliveryHeader_MP

Content-Disposition: attachment;           filename=”254cb5e4c75b4690a7bdcd28fccf4f97″

Content-Location: RN-Delivery-Header

77u/PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhRE9DVFlQRSBEZWxpdmVyeUhlYWRlciBTWVNURU0gIkRlbGl2ZXJ5SGVhZGVyX01TX1YwMl8wMC5kdGQiW10+DQo8RGVsaXZlcnlIZWFkZXI+DQogIDxpc1NlY3VyZVRyYW5zcG9ydFJlcXVpcmVkPg0KICAgIDxBZmZpcm1hdGlvbkluZGljYXRvcj5ZZXM8L0FmZmlybWF0aW9uSW5kaWNhdG9yPg0KICA8L2lzU2VjdXJlVHJhbnNwb3J0UmVxdWlyZWQ+DQogIDxtZXNzYWdlRGF0ZVRpbWU+DQogICAgPERhdGVUaW1lU3RhbXA+MjAyMTAzMThUMTAxODEyLjU5M1o8L0RhdGVUaW1lU3RhbXA+DQogIDwvbWVzc2FnZURhdGVUaW1lPg0KICA8bWVzc2FnZVJlY2VpdmVySWRlbnRpZmljYXRpb24+DQogICAgPFBhcnRuZXJJZGVudGlmaWNhdGlvbj4NCiAgICAgIDxkb21haW4+DQogICAgICAgIDxGcmVlRm9ybVRleHQ+RFVOUzwvRnJlZUZvcm1UZXh0Pg0KICAgICAgPC9kb21haW4+DQogICAgICA8R2xvYmFsQnVzaW5lc3NJZGVudGlmaWVyPjIwMTYyMDE2MjwvR2xvYmFsQnVzaW5lc3NJZGVudGlmaWVyPg0KICAgICAgPGxvY2F0aW9uSUQ+DQogICAgICAgIDxWYWx1ZT5DWUVBSTIwMTY8L1ZhbHVlPg0KICAgICAgPC9sb2NhdGlvbklEPg0KICAgIDwvUGFydG5lcklkZW50aWZpY2F0aW9uPg0KICA8L21lc3NhZ2VSZWNlaXZlcklkZW50aWZpY2F0aW9uPg0KICA8bWVzc2FnZVNlbmRlcklkZW50aWZpY2F0aW9uPg0KICAgIDxQYXJ0bmVySWRlbnRpZmljYXRpb24+DQogICAgICA8ZG9tYWluPg0KICAgICAgICA8RnJlZUZvcm1UZXh0PkRVTlM8L0ZyZWVGb3JtVGV4dD4NCiAgICAgIDwvZG9tYWluPg0KICAgICAgPEdsb2JhbEJ1c2luZXNzSWRlbnRpZmllcj4wNTIzNTQwNjk8L0dsb2JhbEJ1c2luZXNzSWRlbnRpZmllcj4NCiAgICAgIDxsb2NhdGlvbklEPg0KICAgICAgICA8VmFsdWU+QVpVUkU8L1ZhbHVlPg0KICAgICAgPC9sb2NhdGlvbklEPg0KICAgIDwvUGFydG5lcklkZW50aWZpY2F0aW9uPg0KICA8L21lc3NhZ2VTZW5kZXJJZGVudGlmaWNhdGlvbj4NCiAgPG1lc3NhZ2VUcmFja2luZ0lEPg0KICAgIDxJbnN0YW5jZUlkZW50aWZpZXI+YjhhYTY4ZjI0N2NlNDA1ZjkwMDU0OGYwY2Y2MjBhYWE8L0luc3RhbmNlSWRlbnRpZmllcj4NCiAgPC9tZXNzYWdlVHJhY2tpbmdJRD4NCjwvRGVsaXZlcnlIZWFkZXI+

–_410bf7bd-d294-4c7e-9c17-0bf85b7890d2_

Content-Type: application/xml

Content-Transfer-Encoding: base64

Content-ID: a1b66a8d58d34adb81d17737ec2b2819

Content-Description: RN-Service-Header

Content-Disposition: attachment;           filename=”465a75c692254f86a813b6d38dee4890″

Content-Location: RN-Service-Header

77u/PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz4NCjwhRE9DVFlQRSBTZXJ2aWNlSGVhZGVyIFNZU1RFTSAiU2VydmljZUhlYWRlcl9NU19WMDJfMDAuZHRkIltdPg0KPFNlcnZpY2VIZWFkZXI+DQogIDxQcm9jZXNzQ29udHJvbD4NCiAgICA8QWN0aXZpdHlDb250cm9sPg0KICAgICAgPEJ1c2luZXNzQWN0aXZpdHlJZGVudGlmaWVyPkRpc3RyaWJ1dGUgQXN5bmNocm9ub3VzIFRlc3QgTm90aWZpY2F0aW9uPC9CdXNpbmVzc0FjdGl2aXR5SWRlbnRpZmllcj4NCiAgICAgIDxNZXNzYWdlQ29udHJvbD4NCiAgICAgICAgPGZyb21Sb2xlPg0KICAgICAgICAgIDxHbG9iYWxQYXJ0bmVyUm9sZUNsYXNzaWZpY2F0aW9uQ29kZT5Jbml0aWF0b3I8L0dsb2JhbFBhcnRuZXJSb2xlQ2xhc3NpZmljYXRpb25Db2RlPg0KICAgICAgICA8L2Zyb21Sb2xlPg0KICAgICAgICA8ZnJvbVNlcnZpY2U+DQogICAgICAgICAgPEdsb2JhbEJ1c2luZXNzU2VydmljZUNvZGU+SW5pdGlhdG9yIFNlcnZpY2U8L0dsb2JhbEJ1c2luZXNzU2VydmljZUNvZGU+DQogICAgICAgIDwvZnJvbVNlcnZpY2U+DQogICAgICAgIDxNYW5pZmVzdD4NCiAgICAgICAgICA8bnVtYmVyT2ZBdHRhY2htZW50cz4NCiAgICAgICAgICAgIDxDb3VudGFibGVBbW91bnQ+MDwvQ291bnRhYmxlQW1vdW50Pg0KICAgICAgICAgIDwvbnVtYmVyT2ZBdHRhY2htZW50cz4NCiAgICAgICAgICA8U2VydmljZUNvbnRlbnRDb250cm9sPg0KICAgICAgICAgICAgPEFjdGlvbklkZW50aXR5Pg0KICAgICAgICAgICAgICA8R2xvYmFsQnVzaW5lc3NBY3Rpb25Db2RlPkFzeW5jaHJvbm91cyBUZXN0IE5vdGlmaWNhdGlvbiBBY3Rpb248L0dsb2JhbEJ1c2luZXNzQWN0aW9uQ29kZT4NCiAgICAgICAgICAgIDwvQWN0aW9uSWRlbnRpdHk+DQogICAgICAgICAgPC9TZXJ2aWNlQ29udGVudENvbnRyb2w+DQogICAgICAgIDwvTWFuaWZlc3Q+DQogICAgICAgIDx0b1JvbGU+DQogICAgICAgICAgPEdsb2JhbFBhcnRuZXJSb2xlQ2xhc3NpZmljYXRpb25Db2RlPlJlc3BvbmRlcjwvR2xvYmFsUGFydG5lclJvbGVDbGFzc2lmaWNhdGlvbkNvZGU+DQogICAgICAgIDwvdG9Sb2xlPg0KICAgICAgICA8dG9TZXJ2aWNlPg0KICAgICAgICAgIDxHbG9iYWxCdXNpbmVzc1NlcnZpY2VDb2RlPlJlc3BvbmRlciBTZXJ2aWNlPC9HbG9iYWxCdXNpbmVzc1NlcnZpY2VDb2RlPg0KICAgICAgICA8L3RvU2VydmljZT4NCiAgICAgIDwvTWVzc2FnZUNvbnRyb2w+DQogICAgPC9BY3Rpdml0eUNvbnRyb2w+DQogICAgPEdsb2JhbFVzYWdlQ29kZT5Qcm9kdWN0aW9uPC9HbG9iYWxVc2FnZUNvZGU+DQogICAgPHBpcENvZGU+DQogICAgICA8R2xvYmFsUHJvY2Vzc0luZGljYXRvckNvZGU+MEMxPC9HbG9iYWxQcm9jZXNzSW5kaWNhdG9yQ29kZT4NCiAgICA8L3BpcENvZGU+DQogICAgPHBpcEluc3RhbmNlSWQ+DQogICAgICA8SW5zdGFuY2VJZGVudGlmaWVyPmEyODY1ZjA4LThjYjctNDViZi05MDA2LWIwNmI0ZTM2MTgwMzwvSW5zdGFuY2VJZGVudGlmaWVyPg0KICAgIDwvcGlwSW5zdGFuY2VJZD4NCiAgICA8cGlwVmVyc2lvbj4NCiAgICAgIDxWZXJzaW9uSWRlbnRpZmllcj5SMDEuMDI8L1ZlcnNpb25JZGVudGlmaWVyPg0KICAgIDwvcGlwVmVyc2lvbj4NCiAgICA8UXVhbGl0eU9mU2VydmljZVNwZWNpZmljYXRpb24+DQogICAgICA8UXVhbGl0eU9mU2VydmljZUVsZW1lbnQ+DQogICAgICAgIDxRdWFsaXR5T2ZTZXJ2aWNlQ2xhc3NpZmljYXRpb25Db2RlPkNhbm5vdEJlRW1wdHk8L1F1YWxpdHlPZlNlcnZpY2VDbGFzc2lmaWNhdGlvbkNvZGU+DQogICAgICAgIDxWYWx1ZT5DYW5ub3RCZUVtcHR5PC9WYWx1ZT4NCiAgICAgIDwvUXVhbGl0eU9mU2VydmljZUVsZW1lbnQ+DQogICAgPC9RdWFsaXR5T2ZTZXJ2aWNlU3BlY2lmaWNhdGlvbj4NCiAgICA8S25vd25Jbml0aWF0aW5nUGFydG5lcj4NCiAgICAgIDxQYXJ0bmVySWRlbnRpZmljYXRpb24+DQogICAgICAgIDxkb21haW4+DQogICAgICAgICAgPEZyZWVGb3JtVGV4dD5EVU5TPC9GcmVlRm9ybVRleHQ+DQogICAgICAgIDwvZG9tYWluPg0KICAgICAgICA8R2xvYmFsQnVzaW5lc3NJZGVudGlmaWVyPjA1MjM1NDA2OTwvR2xvYmFsQnVzaW5lc3NJZGVudGlmaWVyPg0KICAgICAgICA8bG9jYXRpb25JRD4NCiAgICAgICAgICA8VmFsdWU+QVpVUkU8L1ZhbHVlPg0KICAgICAgICA8L2xvY2F0aW9uSUQ+DQogICAgICA8L1BhcnRuZXJJZGVudGlmaWNhdGlvbj4NCiAgICA8L0tub3duSW5pdGlhdGluZ1BhcnRuZXI+DQogIDwvUHJvY2Vzc0NvbnRyb2w+DQo8L1NlcnZpY2VIZWFkZXI+

–_410bf7bd-d294-4c7e-9c17-0bf85b7890d2_

Content-Type: application/xml;

                  charset=”utf-8″

Content-Transfer-Encoding: base64

Content-ID: 4c9a493f37144d8988741b641eb30086

Content-Description: ServiceContent_MP

Content-Disposition: attachment;           filename=”216c6b984eb94a2995b707ca57c13bc4″

Content-Location: RN-Service-Content

PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0iVVRGLTgiID8+DQo8IURPQ1RZUEUgUGlwMEMxQXN5bmNocm9ub3VzVGVzdE5vdGlmaWNhdGlvbiBTWVNURU0gIjBDMV9NU19SMDFfMDJfQXN5bmNocm9ub3VzVGVzdE5vdGlmaWNhdGlvbi5kdGQiPg0KPFBpcDBDMUFzeW5jaHJvbm91c1Rlc3ROb3RpZmljYXRpb24+DQoJPEFzeW5jaHJvbm91c1Rlc3Q+PC9Bc3luY2hyb25vdXNUZXN0Pg0KCTxmcm9tUm9sZT4NCgkJPFBhcnRuZXJSb2xlRGVzY3JpcHRpb24+DQoJCQk8Q29udGFjdEluZm9ybWF0aW9uPg0KCQkJCTxjb250YWN0TmFtZT4NCgkJCQkJPEZyZWVGb3JtVGV4dCB4bWw6bGFuZz0iRU4iPkpvaG4gRG9lIFNlbmRlcjwvRnJlZUZvcm1UZXh0Pg0KCQkJCTwvY29udGFjdE5hbWU+DQoJCQkJPEVtYWlsQWRkcmVzcz5qZG9lc2VuZGVyQGpvaG5kb2UuY29tPC9FbWFpbEFkZHJlc3M+DQoJCQkJPGZhY3NpbWlsZU51bWJlcj4NCgkJCQkJPENvbW11bmljYXRpb25zTnVtYmVyPjAwMC4wMDAuMDAwMTwvQ29tbXVuaWNhdGlvbnNOdW1iZXI+DQoJCQkJPC9mYWNzaW1pbGVOdW1iZXI+DQoJCQkJPHRlbGVwaG9uZU51bWJlcj4NCgkJCQkJPENvbW11bmljYXRpb25zTnVtYmVyPjAwMC4wMDAuMDAwMTwvQ29tbXVuaWNhdGlvbnNOdW1iZXI+DQoJCQkJPC90ZWxlcGhvbmVOdW1iZXI+DQoJCQk8L0NvbnRhY3RJbmZvcm1hdGlvbj4NCgkJCTxHbG9iYWxQYXJ0bmVyUm9sZUNsYXNzaWZpY2F0aW9uQ29kZT5Jbml0aWF0b3I8L0dsb2JhbFBhcnRuZXJSb2xlQ2xhc3NpZmljYXRpb25Db2RlPg0KCQkJPFBhcnRuZXJEZXNjcmlwdGlvbj4NCgkJCQk8QnVzaW5lc3NEZXNjcmlwdGlvbj4NCgkJCQkJPEdsb2JhbEJ1c2luZXNzSWRlbnRpZmllcj4xMjM0NTY3ODM8L0dsb2JhbEJ1c2luZXNzSWRlbnRpZmllcj4NCgkJCQkJPEdsb2JhbFN1cHBseUNoYWluQ29kZT5JbmZvcm1hdGlvbiBUZWNobm9sb2d5PC9HbG9iYWxTdXBwbHlDaGFpbkNvZGU+DQoJCQkJPC9CdXNpbmVzc0Rlc2NyaXB0aW9uPg0KCQkJCTxHbG9iYWxQYXJ0bmVyQ2xhc3NpZmljYXRpb25Db2RlPldhcmVob3VzZXI8L0dsb2JhbFBhcnRuZXJDbGFzc2lmaWNhdGlvbkNvZGU+DQoJCQk8L1BhcnRuZXJEZXNjcmlwdGlvbj4NCgkJPC9QYXJ0bmVyUm9sZURlc2NyaXB0aW9uPg0KCTwvZnJvbVJvbGU+DQoJPEdsb2JhbERvY3VtZW50RnVuY3Rpb25Db2RlPlJlcXVlc3Q8L0dsb2JhbERvY3VtZW50RnVuY3Rpb25Db2RlPg0KCTx0aGlzRG9jdW1lbnRHZW5lcmF0aW9uRGF0ZVRpbWU+DQoJCTxEYXRlVGltZVN0YW1wPjIwMDQwMTIyVDA3MzkzNS43MzdaPC9EYXRlVGltZVN0YW1wPg0KCTwvdGhpc0RvY3VtZW50R2VuZXJhdGlvbkRhdGVUaW1lPg0KCTx0aGlzRG9jdW1lbnRJZGVudGlmaWVyPg0KCQk8UHJvcHJpZXRhcnlEb2N1bWVudElkZW50aWZpZXI+MjAwNDAxMjJUMDczOTM1LjczN1o8L1Byb3ByaWV0YXJ5RG9jdW1lbnRJZGVudGlmaWVyPg0KCTwvdGhpc0RvY3VtZW50SWRlbnRpZmllcj4NCgk8dG9Sb2xlPg0KCQk8UGFydG5lclJvbGVEZXNjcmlwdGlvbj4NCgkJCTxDb250YWN0SW5mb3JtYXRpb24+DQoJCQkJPGNvbnRhY3ROYW1lPg0KCQkJCQk8RnJlZUZvcm1UZXh0IHhtbDpsYW5nPSJFTiI+Sm9obiBEb2UgUmVjZWl2ZXI8L0ZyZWVGb3JtVGV4dD4NCgkJCQk8L2NvbnRhY3ROYW1lPg0KCQkJCTxFbWFpbEFkZHJlc3M+amRvZXJlY2VpdmVyQGpvaG5kb2UuY29tPC9FbWFpbEFkZHJlc3M+DQoJCQkJPGZhY3NpbWlsZU51bWJlcj4NCgkJCQkJPENvbW11bmljYXRpb25zTnVtYmVyPjAwMC4wMDAuMDAwMjwvQ29tbXVuaWNhdGlvbnNOdW1iZXI+DQoJCQkJPC9mYWNzaW1pbGVOdW1iZXI+DQoJCQkJPHRlbGVwaG9uZU51bWJlcj4NCgkJCQkJPENvbW11bmljYXRpb25zTnVtYmVyPjAwMC4wMDAuMDAwMjwvQ29tbXVuaWNhdGlvbnNOdW1iZXI+DQoJCQkJPC90ZWxlcGhvbmVOdW1iZXI+DQoJCQk8L0NvbnRhY3RJbmZvcm1hdGlvbj4NCgkJCTxHbG9iYWxQYXJ0bmVyUm9sZUNsYXNzaWZpY2F0aW9uQ29kZT5SZXNwb25kZXI8L0dsb2JhbFBhcnRuZXJSb2xlQ2xhc3NpZmljYXRpb25Db2RlPg0KCQkJPFBhcnRuZXJEZXNjcmlwdGlvbj4NCgkJCQk8QnVzaW5lc3NEZXNjcmlwdGlvbj4NCgkJCQkJPEdsb2JhbEJ1c2luZXNzSWRlbnRpZmllcj4xMjM0NTY3ODQ8L0dsb2JhbEJ1c2luZXNzSWRlbnRpZmllcj4NCgkJCQkJPEdsb2JhbFN1cHBseUNoYWluQ29kZT5JbmZvcm1hdGlvbiBUZWNobm9sb2d5PC9HbG9iYWxTdXBwbHlDaGFpbkNvZGU+DQoJCQkJPC9CdXNpbmVzc0Rlc2NyaXB0aW9uPg0KCQkJCTxHbG9iYWxQYXJ0bmVyQ2xhc3NpZmljYXRpb25Db2RlPkVuZCBVc2VyPC9HbG9iYWxQYXJ0bmVyQ2xhc3NpZmljYXRpb25Db2RlPg0KCQkJPC9QYXJ0bmVyRGVzY3JpcHRpb24+DQoJCTwvUGFydG5lclJvbGVEZXNjcmlwdGlvbj4NCgk8L3RvUm9sZT4NCjwvUGlwMEMxQXN5bmNocm9ub3VzVGVzdE5vdGlmaWNhdGlvbj4=

–_410bf7bd-d294-4c7e-9c17-0bf85b7890d2_–

After above modification, the modified 0C1 message can be successfully processed by BizTalk.

Items modified:

1. Added Content-Type with boundary string. (Green)


2. Added first boundary string is missing. (Yellow)


3. Added Content-IDs on all segments. (Red) NOTE: Content-ID is optional according to Rosettanet specification.


4. Corrected ServiceContent part’s encoding to Base64. (Blue)


5. processName is incorrectly set as PIP name in PIP configuration.

This will lead to the following error in BizTalk:

Public Responder could not send an Async exception signal due to internal errors below:

                             RNIF Exception detail:-

              Error code:UNP.SHDR.VALERR

              Error Number:2005

              Description: PIP name specified does not match the PIP specification.

This is because the wrong processName is set as BusinessActivityIdentifier in ServiceHeader.

<?xml version=”1.0″ encoding=”utf-8″?>

<!DOCTYPE ServiceHeader SYSTEM “ServiceHeader_MS_V02_00.dtd”[]>

<ServiceHeader>

  <ProcessControl>

    <ActivityControl>

      <BusinessActivityIdentifier>Test0C1</BusinessActivityIdentifier>

      <MessageControl>

        <fromRole>

          <GlobalPartnerRoleClassificationCode>Initiator</GlobalPartnerRoleClassificationCode>

        </fromRole>

        <fromService>

          <GlobalBusinessServiceCode>Initiator Service</GlobalBusinessServiceCode>

To resolve this error, we need to manually edit the PIP in JSON and correct the processName as the same string of BizTalk PIP configuration:

Solution & workaround:

LogicApps product group is actively working on the fixes of these issues now.

For item #4 ServiceContent encoding issue, the corresponding fix has already been deployed to East US region and other regions’ deployment will be finished in couple of days as well.

For items #1 and #2, we can manually edit RN Encode/Decode LogicApps from template to add Content-Type and boundary string as a workaround(see below).

RN Encode LogicApp:

RN Decode LogicApp:

(The samples of these two modified workflows’ JSON definition can be found in attachment.)

Also, please don’t forget to correct processName in PIP config (Edit As JSON). For 3A4, processName should be Request Purchase Order.

{

After all the changes above, your LogicApp should be able to successfully send/receive Rosettanet documents without error.

Can’t list pool due to encryption key after subscription suspension

by Contributed | Apr 6, 2021 | Technology

This article is contributed. See the original author and article here.

Can’t list pool due to encryption key after subscription suspension

For some reason, Subscription Account got suspended because of which unable to list the pools in the pool blade and you will see the following error message:

Error Message: AccountEncryptionKeyUnavailable message: Account data could not be decrypted as the account encryption key is currently unavailable.

Cause
 

This is a known bug in Batch, typically associated with subscriptions being suspended due to credits running out, fraud, and other things for any period of time.

Solution

Since this is a known issue in Batch, the Product Team is already working on this.
 

We are aware of this issue and will deploy a fix in the future, but unfortunately. At this moment the customer’s only recourse is to delete and recreate the batch account.

in order to mitigate the issue. We apologize for any inconvenience this has caused.

Next Step

If your Azure issue is not addressed in this article, please submit a support request, on the Azure support page, select Get support.

Raising the minimum bar with Azure Automanage

by Contributed | Apr 6, 2021 | Technology

This article is contributed. See the original author and article here.

Hello Folks,

I’ve always believed that one of the true roles of IT in any organizations is to help the business units achieve their goals while maintaining adequate control over company resources. This is not an all-encompassing rule. It’s just my own personal view of our role.

But to perform that role, we need to ensure that resources that are deployed are at the very least adequately inventoried, protected, monitored, and operated. Basically, we need to ensure that all the facets of the operation lifecycle of our resources are covered.

That means that when deploying a new VM in Azure for example you need to ensure you’ve enrolled it in the following services:

• VM Insights Monitoring


• Backup


• Azure Security Center


• Microsoft Antimalware


• Update Management


• Change Tracking & Inventory


• Azure Guest Configuration


• Boot Diagnostics


• Azure Automation Account


• Log Analytics Workspace

These services if performed manually one by one could take you a significant amount of time.  And yes, I know…  This can be automated through Azure Resource Manager (ARM) templates, through PowerShell scripts, Azure CLI Scripts, and other means. However, when you do that, you now have to manage your environment AND your custom code.

In comes Azure Automanage…  A new service, currently in preview (at publishing time) that helps you automate this process without the need to create your own code for it.  For a demo of Azure Automanage you can see Sarah Lean’s first look video.

I meet with Dean Wells, Principal PM Manager for Azure Automanage.  He shared the genesis of the service, the current state and the roadmap for added functionality.

Even if this service is in preview, there are resources available for you to lean and try this new functionality.

Resources:

• Provide your Feedback – ITOpsTalk-Feedback@Microsoft.com or directly to Dean Wells at Dean@microsoft.com


• Learn more about Azure Automanage: Azure Automanage | Microsoft Azure


• Get Started https://aka.ms/AutomanagePreview


• General docs: https://aka.ms/automanage

Check it out and let us know what you think.

Cheers!

Pierre

The Azure Data Architecture Map

by Contributed | Apr 6, 2021 | Technology

This article is contributed. See the original author and article here.

Hi,

I’m excited to announce this new map and I’m happy to see the great success (beyond expectations) of this map series. With nearly 300K views, these maps even gave birth to a more exhaustive book.

FYI, here are all the maps of the series:

• The OpenID Connect (OIDC) Architecture Map


• The Azure Kubernetes Service (AKS) Architecture Map


• The Cloud-native Azure Application Architect Map


• The Azure Infrastructure Architect Map


• The Azure Security Architect Map – This map


• The Azure Solution Architect Map

Admittedly, the data map was by far the hardest to build, because there is a big functional overlap across data services. Nevertheless, I tried to identify the primary use case of each service, or where a given service shines the most. 

The purpose of the this map is to see, in a glimpse, which services may suit your functional needs but it is up to you to dig deeper.

Here is the map:

which focuses on the following areas:

• Traditional: many enterprises still deal with traditional BI and there is nothing wrong with it! This category regroups Azure services which you can use to build your cubes, run your ETL jobs, etc.


• Modern: this category is the counterpart of the traditional category. For example, ELT is the modern counterpart of ETL…that’s a bit the spirit :). You may of course find services that are in both sides.


• Big Data: Big Data is also recent in the data lanscape, so it could have been a subset of the modern group, but for sake of clarity, I decided to make it a separate group. 
  
  


• Artificial Intelligence: AI is on every lips so I couldn’t skip it although this category was hard to craft. There is so much overlap across AI services that it’s kind of hard to categorize them. I tried to have a very condensed group.
  
  


• Others: in this category, you’ll find concerns such as “sharing data with other companies”, “Governing data”, etc.

One note though: Microsoft is pushing hard on Azure Synapse Analytics and their aim is to have a all-in-one service, that combines decades of on-premises data practices and the most modern and top-notch data features. So, you’d better keep an eye on its development!

Here is the pointer to the map:

Firewall integration in Azure VMware Solution

by Contributed | Apr 5, 2021 | Technology

This article is contributed. See the original author and article here.

2020 has been a year like no other. In just a few months’ time, businesses have transformed and have accelerated their efforts to migrate to the cloud. Following our announcement of Azure VMware Solution (AVS) last year, we have been helping customers accelerate this move to cloud by providing an easy lift and shift migration. Albeit customers love the same operational experience for VMware workloads and use familiar VMware technologies like vCenter, NSX Manager, HCX etc. in AVS, they also want to leverage security integrations that they have invested in for years. Below are a few common questions that we get from customers around this topic. 

How can they use the same firewalls/tools that they have been using for years?

How do they maintain the same security posture?

How can they use the same firewall for both Azure and VMware workloads in AVS?

In this blog series, we plan to discuss native security options, 3^rd party firewall integration with AVS along with a deep dive into configuration details. First in the series, this blog would summarize the security options available at your disposal.

Let’s start with the built-in security capabilities that you can leverage in AVS.

Built-in security/firewall with VMware NSX-T – VMware NSX-T is the default networking stack in AVS and it provides out-of-box security features that you can use to protect your workloads. Following are the capabilities that you can leverage.

Distributed Firewall (DFW) –A stateful L3-L7 firewall that powers micro-segmentation and runs on your ESXi hosts in your AVS private cloud. DFW rules are enforced on the vNIC level of a VM workload and what that means is that the traffic is either allowed or dropped on the vNIC level based on the rule you defined. So, there is no more hair-pinning that traffic through a centralized or perimeter firewall.  From a feature standpoint, it’s rich and allows you to define security rules using network or application constructs.  You could group the workloads using static (IPSet/NSX constructs like Segment etc.) or dynamic membership (VM tags, guest OS etc.). Even when you have a perimeter firewall, you should secure your East-West traffic.

Gateway Firewall – A L4-L7 aware stateful North-South firewall that can be configured on NSX-T Tier-1 Gateway in AVS. It can also be used as an Inter-tenant or Inter-zone firewall i.e. filtering traffic between different tenants of your organization each with a dedicated Tier-1 Gateway.

Azure Firewall – A managed, stateful firewall with built-in HA and SLA of 99.99% (when deployed in two or more availability zones). Customers can configure L3-L7 policies to filter traffic and take advantage of threat intelligence-based filtering to alert and deny traffic from/to known malicious IP addresses and domains. Please refer to the Azure firewall feature set here.

If you are already using Azure firewall capabilities deployed in Azure Virtual WAN to protect resources in VNETs, you can connect the same virtual WAN hub over an express route connection to AVS and route internet traffic from AVS to Azure firewall.

Let’s switch gears and talk about the 3rd party firewall integration with Azure VMware Solution. There is a strong desire from customers to continue using the same firewall in AVS that they have been using in an on-premises datacenter. Based on the use-case, you could deploy a 3rd party firewall NVA in AVS private cloud or SDDC or leverage a firewall from Azure marketplace. Let’s double click on both options.

3rd Party firewall deployed as NVA in AVS private cloud or SDDC –Before we discuss this integration, it’s important to understand NSX-T deployment in AVS private cloud. When you create a private cloud in AVS, a default NSX-T Tier-0 Gateway configured in Active/Active mode and a default NSX-T Tier-1 Gateway configured in Active/Standby mode is deployed for you. Users can connect segments (logical switches) and provide East-West and North-South connectivity to the workloads connected on these segments.

A 3rd party firewall NVA can be connected southbound to the default NSX-T Tier-1 gateway and this firewall can act as a North-South firewall or East-West firewall depending upon your use case. This integration is supported in following topologies.

• Option 1: Workload segments are directly connected to the firewall and the gateway on workloads is 3^rd party firewall. This topology restricts the users with numerous segments as the vNICs on the NVA becomes a limiting factor.


• Option 2: Workload segments are connected to an isolated Tier-1 and this Tier-1 gateway provides northbound connectivity to a 3^rd party firewall. This topology solves the problem of limited number of vNICs on NVA as you connect 100s of workload segments to an isolated Tier-1 which connects to the firewall NVA northbound. In this topology, isolated Tier-1s simulate security zones and the firewall can provide East-West filtering between security zones and North-South filtering for all traffic.

We will discuss routing and other configuration details for these topologies in next part of this blog series.

3rd Party firewall deployed in Azure VNET – Customers can also deploy a 3^rd party firewall in Azure VNET and route traffic from AVS to this firewall via Azure Virtual WAN hub. To redirect internet traffic from AVS VMs to the firewall NVA, you need to connect AVS to an express route gateway in Azure virtual WAN and propagate a default route. Next, you configure a default route in Azure Virtual WAN hub to direct internet bound traffic to a NVA in spoke VNET.

We will go through the configuration details in greater detail in upcoming blogs. Stay tuned!

Summary

Azure VMware Solution customers have multiple security options available to protect their workloads. Some of these firewalling capabilities can be used out of the box to provide East-West and North-South firewalling. Along with the built-in security capabilities, customers can also leverage the 3^rd party firewalls or next-gen firewalls to provide additional security and maintain the same security posture as they have on-premises.

Following are a few resources to learn more about Azure VMware Solution.

Learn Azure VMware Solution Networking

Try Azure VMware Solution Hands-on-lab