Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge to publish #193

Merged
merged 2 commits into from
Aug 23, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file modified tutorials/images/power-automate/dynamic-content.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified tutorials/images/power-automate/flow-formula.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
4 changes: 2 additions & 2 deletions tutorials/includes/power-automate/01-intro.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,8 +13,8 @@ This lab covers both of the scenarios above. First, you will create a custom con

To complete this exercise in this post you will need the following:

- Administrator access to a Microsoft 365 tenancy. If you don't have a Microsoft 365 tenant, you might qualify for one through the [Microsoft 365 Developer Program](https://developer.microsoft.com/microsoft-365/dev-program); for details, see the [FAQ](/office/developer-program/microsoft-365-developer-program-faq#who-qualifies-for-a-microsoft-365-e5-developer-subscription-). Alternatively, you can [sign up for a 1-month free trial or purchase a Microsoft 365 plan](https://www.microsoft.com/en-us/microsoft-365/try).
- Access to [Microsoft Power Automate](https://powerautomate.microsoft.com/).
- Administrator access to a Microsoft 365 tenancy. If you don't have a Microsoft 365 tenant, you might qualify for one through the [Microsoft 365 Developer Program](https://developer.microsoft.com/microsoft-365/dev-program); for details, see the [FAQ](/office/developer-program/microsoft-365-developer-program-faq#who-qualifies-for-a-microsoft-365-e5-developer-subscription-). Alternatively, you can [sign up for a 1-month free trial or purchase a Microsoft 365 plan](https://www.microsoft.com/microsoft-365/try).
- Access to [Microsoft Power Automate](https://powerautomate.microsoft.com/) with a Premium license. See [Power Automate licensing FAQ](/power-platform/admin/power-automate-licensing/faqs) for details. If you do not have a Premium license, you can sign up for a 90-day trial.

## Feedback

Expand Down
8 changes: 3 additions & 5 deletions tutorials/includes/power-automate/03-create-connector.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,7 @@

In this exercise, you will create a new custom connector which can be used in Microsoft Power Automate or in Azure Logic Apps. The OpenAPI definition file is prebuilt with the correct path for the Microsoft Graph `$batch` endpoint and additional settings to enable simple import.

Open a browser and navigate to [Microsoft Power Automate](https://powerautomate.microsoft.com/). Sign in with your Microsoft 365 tenant administrator account. Choose **Data** on the left-hand side menu, and select the **Custom Connectors** item in the drop-down menu.

![A screen shot of the drop-down menu in Microsoft Power Automate](../../images/power-automate/custom-connectors.png)
Open a browser and navigate to [Microsoft Power Automate](https://powerautomate.microsoft.com/). Sign in with your Microsoft 365 tenant administrator account. Choose **Custom connectors** on the left-hand side menu. If **Custom connectors** isn't present in the menu, select **More**, then **Discover all**.

There are two options to create a custom connector for Microsoft Graph:

Expand Down Expand Up @@ -91,10 +89,10 @@ Choose **Create Connector** on the top-right.

---

After the connector has been created, copy the generated **Redirect URL**.
After the connector has been created, copy the generated **Redirect URL** from the **Security** tab.

![A screen shot of the generated Redirect URL](../../images/power-automate/redirect-url.png)

Go back to the registered application in the [Azure Portal](https://aad.portal.azure.com) you created in the previous exercise. Select **Authentication** on the left-hand side menu. Select **Add a platform**, then select **Web**. Enter the redirect URL copied from the previous step in the **Redirect URIs**, then select **Configure**.
Go back to the registered application in the Microsoft Entra Portal you created in the previous exercise. Select **Authentication** on the left-hand side menu. Select **Add a platform**, then select **Web**. Enter the redirect URL copied from the previous step in the **Redirect URIs**, then select **Configure**.

![A screen shot of the Reply URLs blade in the Azure portal](../../images/power-automate/update-app-reg.png)
4 changes: 1 addition & 3 deletions tutorials/includes/power-automate/04-authorize-connector.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,9 +5,7 @@ The final configuration step to ensure the connector is ready for use is to auth
> [!IMPORTANT]
> The following steps requires that you are logged in with administrator privileges.

In [Microsoft Power Automate](https://powerautomate.microsoft.com), go to the **Data** menu item on the left and choose the **Connections** page. Choose the **New Connection** link.

![A screen shot of the New connection button](../../images/power-automate/new-connection.png)
In [Microsoft Power Automate](https://powerautomate.microsoft.com), choose **Connections** on the left-hand side menu. If **Connections** isn't present in the menu, select **More**. Select the **New connection** link.

Find your custom connector and complete the connection by selecting it, then choosing **Create**. Sign in with your Microsoft 365 tenant administrator's Azure Active Directory account.

Expand Down
14 changes: 7 additions & 7 deletions tutorials/includes/power-automate/06-create-flow.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,15 +6,15 @@ In the end your flow will look similar to the following image:

![A screen shot of the completed flow](../../images/power-automate/completed-flow.png)

Open [Microsoft Power Automate](https://flow.microsoft.com) in your browser and sign in with your Office 365 tenant administrator account. Choose **My flows** in the left-hand navigation. Choose **New**, then **Instant--from blank**. Enter `Create Team` for **Flow name**, then select **Manually trigger a flow** under **Choose how to trigger this flow**. Choose **Create**.
Open [Microsoft Power Automate](https://flow.microsoft.com) in your browser and sign in with your Office 365 tenant administrator account. Choose **My flows** in the left-hand navigation. Choose **New flow**, then **Instant cloud flow**. Enter `Create Team` for **Flow name**, then select **Manually trigger a flow** under **Choose how to trigger this flow**. Choose **Create**.

Select the **Manually trigger a flow** item, then choose **Add an input**, select **Text** and enter `Name` as the title.

![A screen shot of the Manually trigger a flow trigger](../../images/power-automate/manually-trigger.png)

Choose **New step** and type `Batch` in the search box. Add the **MS Graph Batch Connector** action. Choose the ellipsis and rename this action to `Batch POST-groups`.
Choose **+** under the **Manually trigger a flow** item, then select **Add an action**. Type `Batch` in the search box, and set the **Runtime** dropdown to **Custom**. Add the **MS Graph Batch Connector** action. Choose the ellipsis and rename this action to `Batch POST-groups`.

Add the following code into the **body** text box of the action.
In the **Advanced parameters** dropdown, select **body**. Add the following code into the **Body** text box of the action.

```json
{
Expand All @@ -41,11 +41,11 @@ Replace each `REPLACE` placeholder by selecting the `Name` value from the manual

![A screen shot of the dynamic content menu in Microsoft Flow](../../images/power-automate/dynamic-content.png)

Choose **New step**, search for `delay` and add a **Delay** action and configure for 1 minute.
Choose **+** under the **Batch POST-groups** item, then select **Add an action**. Search for `delay` and add a **Delay** action and configure for 1 minute.

Choose **New step** and type `Batch` in the search box. Add the **MS Graph Batch Connector** action. Choose the ellipsis and rename this action to `Batch PUT-team`.
Choose **+** under the **Delay** item, then select **Add an action**. Add the **MS Graph Batch Connector** action. Choose the ellipsis and rename this action to `Batch PUT-team`.

Add the following code into the **body** text box of the action.
In the **Advanced parameters** dropdown, select **body**. Add the following code into the **Body** text box of the action.

```json
{
Expand Down Expand Up @@ -92,7 +92,7 @@ Choose **Save**, then choose **Test** to execute the flow.
> [!TIP]
> If you receive an error like `The template validation failed: 'The action(s) 'Batch_POST-groups' referenced by 'inputs' in action 'Batch_2' are not defined in the template'`, the expression is incorrect and likely references a flow action it cannot find. Ensure that the action name you are referencing matches exactly.

Choose the **I'll perform the trigger** action radio button and choose **Save & Test**. Choose **Continue** in the dialog. Provide a name without spaces, and choose **Run flow** to create a Team.
Choose the **Manually** action radio button and choose **Test**. Provide a name without spaces, and choose **Run flow** to create a Team.

![A screen shot of the Run flow dialog](../../images/power-automate/run-flow.png)

Expand Down