{"id":1303,"date":"2019-07-31T19:14:32","date_gmt":"2019-08-01T02:14:32","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/july-updates-for-microsoft-flow\/"},"modified":"2019-07-31T19:14:32","modified_gmt":"2019-08-01T02:14:32","slug":"july-updates-for-microsoft-flow","status":"publish","type":"power-automate","link":"https:\/\/www.microsoft.com\/en-us\/power-platform\/blog\/power-automate\/july-updates-for-microsoft-flow\/","title":{"rendered":"July Updates for Microsoft Flow"},"content":{"rendered":"
Last week we released the new Copy and Paste feature and streamlined flow experience<\/a>. This week we have several other key updates that are now available.<\/p>\n First, we have added several highly-request features to the SharePoint connector:<\/p>\n <\/p>\n Additionally, don\u2019t forget that you can always call any action by using the Send and HTTP Request to SharePoint<\/b>\u00a0action on the standard SharePoint connector, even if it is not available as a built-in action.<\/p>\n We are delighted to announce the public preview of\u00a0PowerApps and Flow Build Tools<\/a>\u00a0available\u00a0here<\/a>. As the deployment of Microsoft Flow expands across the enterprise, so does the requirements for being able to automate the lifecycle of the Apps and Flows, manage them through source control with proper versioning and generally leverage DevOps for deployments.<\/p>\n This initial release is the first step towards a more comprehensive, yet simplified story around ALM for Microsoft Folw. A story we will continue to augment by adding features based on feedback, but equally important \u2013 by continuing to invest in more training and documentation with prescriptive guidance. Read more here on the PowerApps blog<\/a>.<\/p>\n We are announcing public preview of guest access, which enables users to assign approvals to guest users who are not full members of the tenant. This preview also includes support in the SharePoint<\/strong> and Approvals<\/strong> connectors for building automated, instant or scheduled flows.<\/p>\n First, guest users can be invited to a tenant through the Azure AD admin portal:<\/p>\n <\/p>\n An Office 365 plan (or any plan that contains a Microsoft Flow license) will need to be assigned to the guest user.<\/p>\n <\/p>\n The invited user then may accept the email invitation to join the tenant:<\/p>\n <\/p>\n The maker of the flow can create an approval as they normally would and assign it to the guest user that was added.<\/p>\n The guest user can click the link in the approval notification\u00a0 email to approve or reject. This will route them to the approval in the guest tenant. From the approvals page, the guest can approve or reject the approval as they normally would.<\/p>\n To return to their home tenant, the guest can go to the My Flows or Approvals page and click the Go to your org\u2019s default environment<\/strong> link in the notification:<\/p>\n <\/p>\n Alternatively, they can use the sign out link in the top right corner and re-sign in.<\/p>\n Note that if the guest has not been granted a license by an administrator in the target tenant, they will receive an error like the below:<\/p>\n <\/p>\n Clicking the link will return them to their home tenant.<\/p>\n In addition to participating in approvals, guest users can also create and run flows if they are invited to the tenant. However, except for SharePoint and Approvals, connections to any other Azure AD backed services are currently created in the context of the user\u2019s home tenant, not the tenant that the user is logged into.<\/p>\n Support for more connectors in the context of the guest tenant will gradually come online between August and October.<\/p>\n Users should be aware when creating connections in a different tenant that tenant administrators have control of those flows and connections. Do not creating flows and connections in untrusted tenants is strongly discouraged.<\/p>\n There are a few specific areas that do not work for guest users currently. First, the Flow notification<\/strong> connector\u2019s Send a Mobile Notification action does not support guest users because the Flow app for iOS or Android cannot sign users in as guests.<\/p>\n Second, people picker experiences will not work for guest users because they should not be able to query and enumerate members of the tenant. For example:<\/p>\n <\/p>\n Instead, users need to type the full email address and press enter. Once they do so, the email will be accepted. If it is incorrect, flows like the Request Signoff flow may fail since they are unable to find the user. Additionally, actionable Emails for Approvals are not supported for guest users.<\/p>\n Third, links from Flow into PowerApps and the Admin Portal will be in the context of the home tenant.<\/p>\n Fourth, there is no button or menu in the user interface for switching between tenants. The only way to access the flow portal as a guest is to receive and click a link to an approval or flow in an email.<\/p>\n Finally, guest users do not qualify for self-serve trial plans, so creating trials will not work. Instead, users should request tenant administrators give them a plan from the Azure portal.<\/p>\n In addition to the other improvements, there are two minor authoring improvements available:<\/p>\n First, one of the powerful aspects of automated flows is that any action can use data output by any trigger or action above it in the flow. However, this presents a challenge if you want to change a step at the top of the flow on which other actions depend. Previously, the flow designer would block you from making such a change because doing so would break other actions in the flow. Now, you can delete or rename actions on which other steps depend. Use the Flow checker<\/strong> to fix the issues that arise.<\/p>\n Second, when we introduced automated flows in CDS solutions, we imposed the same restrictions that exist for classic CDS workflows – in particular, in order to edit a running flow you would need to first disable it. This ensured that you would not impact something running in production. However, this approach slowed down development and testing of your automated flows, so this restrictions has been removed. Now, you can edit running flows directly.<\/p>\n Finally, in the past month we released four new partner connectors:<\/p>\n There are several key improvements releasing this week. First, there are a number of new SharePoint connector actions, including working with Doc Sets, permissions, and creating Folders. Second, Flow now supports version control with Azure DevOps. Third, guest users can participate in approval processes and create flows. There are a couple authoring and solution improvements, and we also released four new connectors.<\/p>\n","protected":false},"author":347,"featured_media":0,"comment_status":"open","ping_status":"open","template":"","power-automate-category":[2752],"power-automate-tag":[],"coauthors":[2913],"class_list":["post-1303","power-automate","type-power-automate","status-publish","hentry","power-automate-category-product-updates"],"yoast_head":"\nNew SharePoint connector actions<\/h2>\n
\n
Use Flow with Azure DevOps<\/h2>\n
Guest user support<\/h2>\n
Walkthrough of guest support for Approvals<\/h3>\n
Using Connectors in Flows<\/h3>\n
\n
Known Issues and Limitations<\/h3>\n
\n
Two authoring improvements<\/h2>\n
Four New Connectors<\/h2>\n
\n