New Zealand football predictions today

10. Weekly Match Preview

Stay ahead of the week with our comprehensive match previews that delve into upcoming fixtures with detailed analyses:

• Fixture Highlights: A rundown of key fixtures scheduled for the week, emphasizing high-stakes games.
<|file_sep|># Power Platform Protocols This sample app is here as an example of how to consume a Power Platform connector using protocols (e.g. SOAP and REST) with a platform like Azure Logic Apps. ## Features - Reusability - Connect to the same use case with different protocols - The end user designs the solution without needing any technical skills ### Reusability Logic Apps are a great example of reuse as they are serverless, do not need provisioning like an API Management instance and are an excellent fit for configurable integration solutions. ### Connect to the same use case with different protocols In this article, we'll be exploring how to use the SOAP API supported by Power Automate connectors using Azure Logic Apps with an Azure Function. ### The end user designs the solution without needing any technical skills Finally, as Azure Logic Apps supports both codeless, graphical experiences as well as code-first templates (JSON), they're a great lightweight platform for integrating with your broader organization without needing developers. ## Benefits - Integrations with less developer overhead - More choices for technology (e.g., can use different protocols than typical REST API) - Better governance - Better oversight of what integrations are running # Building an Integration Based on Power Platform Connectors ## About this article This article is retained as an example of how you can leverage Microsoft Power Platform connectors using protocols like SOAP within other products like Azure Logic Apps, which do not natively support Power Platform connectors. For those unfamiliar, Power Platform connectors are one way you can connect data across apps such as Microsoft Power Apps, Microsoft Power Automate (formerly Microsoft Flow), Microsoft Power Virtual Agents (formerly Microsoft Bot Framework), Microsoft Dynamics 365, etc. While most Power Platform connectors use RESTful APIs, some connectors do support other protocols like SOAP and OData V2. For this article, I'll briefly summarize how this integration would normally work and then discuss why it doesn't right now. ## How it works We're going to leverage a sample use case scenario developed by [Mandiant](https://www.mandiant.com/) - an MITRE ATT&CK® use case: **[ModifyAccountRights](https://attack.mitre.org/wiki/Technique/T1060)** that is available in my sample repository (the XML file is called **Mandiant.xml**). This use case shows how to modify user rights across different systems. The MITRE ATT&CK® framework is publicly available free toolset created by members of the [MITRE Corporation](https://www.mitre.org/) for designing better security within digital environments. We're using an Office 365 E5 or Office 365 GCC environment in this example with a Power Platform Application created:  The graphic below shows one way this integration would work.  By leveraging this solution, if a security alert or trigger is received from Microsoft Sentinel or another security product about an attacker modifying user rights leveraging the ModifyAccountRights MITRE ATT&CK® technique (as defined by MITRE), then this solution would stop that moving forward by blocking modification of user rights in Office 365. ## How it doesn't work As of writing this article, there is no support within Azure Logic Apps for consuming Power Platform connectors by leveraging their SOAP APIs. Logic Apps support SOAP connections out of the box However you would not be able to use the SOAP connection to connect to endpoints that require authentication. ## How to make it work This example shows one way you could do it using Azure Functions in conjunction with Logic Apps (with a very small amount of code) in your own Azure subscription. ### Use case  ## Solution Components There are several components in this solution. ### Azure Logic App This is the main orchestration component for this solution. ### Azure Function This component is used to assist with authentication through using OAuth 2.0 with Azure AD Authorization Code Flow. ### Azure Active Directory Application This component provides authentication tokens to be used by both the Azure Logic App as well as the Azure Function.  Azure AD tokens will authenticate against the Power Platform connection named **O365CIS** that we'll create later. ## Getting started To setup this sample solution you need to have the following prerequisites: - An active Office 365 tenant - Appropriate Office 365 licensing on at least one account in your Office 365 tenant (**Users & licenses | Active users** tab) - An appropriate Azure subscription - An active Microsoft Power Platform environment (linked to your Office 365 tenant) - The [MITRE ATT&CK® use case](https://attack.mitre.org/wiki/Technique/T1060) file: **[Mandiant.xml](./MITRE/Mandiant.xml)** ## Lab Setup 1 - Setup environment In this lab setup section, we'll be setting up the various components required for logic app to run properly (e.g. AAD app registrations). #### Lab Setup Notes - To follow along with this lab setup step-by-step you might want to open a new tab or window with the [Power Platform Admin Center](https://admin.powerplatform.microsoft.com/) as we will be utilizing it in this section. - We'll also be using a [Power Platform entitlement offer](https://docs.microsoft.com/en-us/power-platform/admin/onboard-administrator#onboard-an-environment-with-the-admin-center) as a sandbox environment for this demonstration ### Step 1: Create a tenant and assign licenses If you don't already have a subscription that satisfies the above prerequisites then head over an create an Azure subscription that satisfies those prerequisites (e.g., [responseresourcekits.com/fast-start](https://www.responseresourcekits.com/fast-start)). If you'd like to leverage a sandbox environment for this you could use a [Power Platform entitlement offer](https://docs.microsoft.com/en-us/power-platform/admin/onboard-administrator#onboard-an-environment-with-the-admin-center) as shown in the step by step instructions below. For more information on how to configure access permissions for your Power Platform environment see: [Power Platform Permissions](https://learn.microsoft.com/en-us/power-platform/admin/database-security-and-privacy) resources. #### Step 1.1: Create an Office 365 tenant (if required) If you already have an Office 365 tenant with the appropriate licensing then you can move on to step 1.2. If not start by creating an Office 365 tenant: - Select **Create a free Microsoft account**:  - Enter your name on the **Personal information** tab:  - You'll then enter your email address on the **Select an email address** tab:  - Decide if you want to create a business account now or just sign up for a personal account on the **Pick your type** tab:  #### Step 1.2: Assign licenses The next step is to verify that at least one user has been assigned appropriate license(s) such as Exchange Online (Plan 2), Microsoft Defender for Office 365 (Plan 1) Go over to [Microsoft 365 admin center](https://admin.microsoft.com) where you'll then navigate to **Users | Active users** tab.  In this example, I have three users: - Michael Aldridge - Andre Smith - Joe Bloggs If needed assign appropriate licensing (e.g. Enterprise Mobility + Security E5) from the **Licenses & apps** tab of the user's profile.  #### Step 1.3: Verify you’re licensed for Power Platform In order to complete these labs, you need to verify that your organization has the right licenses. From your administrative role center in Power Platform admin center 1. On the left navigation pane select Licenses > User + Cloud App Assignments. 2. Navigate to the App > SharePoint > SharePoint Licensed Users tile. 3. Verify that one or more users are assigned a SharePoint license. A SharePoint license is required for creating an environment from a Microsoft Dataverse solution package (.zip) file. ### Step 2: Create application registration in Azure AD (if required) If you don't already have an application registration then follow these steps: 1. Start by navigating to [Azure Active Directory](https://aad.portal.azure.com/) where you'll then select **App registrations** under **Manage**: