Home
%3CLINGO-SUB%20id%3D%22lingo-sub-289589%22%20slang%3D%22en-US%22%3EUPDATED%20-%20Updates%20to%20Microsoft%20Flow%20and%20PowerApps%20for%20Office%20365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-289589%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EOver%20the%20past%20two%20years%2C%20we%20have%20helped%20drive%20the%20transformation%20of%20business%20processes%20with%20Microsoft%20365%20by%20helping%20you%20create%20innovative%20business%20apps%20based%20on%20tools%20such%20as%20Microsoft%20Flow%2C%20PowerApps%2C%20SharePoint%20lists%2C%20Microsoft%20Forms%2C%20and%20Power%20BI.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EWe%E2%80%99ve%20invested%20heavily%20and%20will%20continue%20to%20invest%20in%20enhancing%20and%20extending%20the%20value%20of%20Flow%20and%20PowerApps%20and%20over%20the%20next%20several%20months%20we%20plan%20to%20release%20new%20capabilities%20including%3A%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3ECustom%20reusable%20canvas%20controls%20for%20PowerApps%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EResponsive%20design%20for%20PowerApps%20canvas%20apps%20%26nbsp%3B%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EEnhancing%20SharePoint%20document%20libraries%20with%20PowerApps%20and%20PowerApps%20forms%20%26nbsp%3B%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EAvailability%20of%20PowerApps%20and%20Flow%20in%20the%20US%20Government%20sovereign%20cloud%20(%E2%80%9CGCC%E2%80%9D)%20%26nbsp%3B%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3EWe%E2%80%99ve%20been%20amazed%20to%20see%20how%20you%E2%80%99ve%20extended%20the%20Microsoft%20365%20platform%20to%20build%20the%20next%20generation%20of%20business%20applications%20with%20low%20code%20or%20no%20code%20requirements.%20We%20have%20some%20great%20examples%20showcased%20in%20our%20%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Fodsp-bacs%22%20target%3D%22_blank%22%20data-cke-saved-href%3D%22https%3A%2F%2Faka.ms%2Fodsp-bacs%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3EBusiness%20Apps%20Resource%20Center%3C%2FA%3E.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EOffice%20365%20plans%20include%20PowerApps%20and%20Flow%20capabilities%20to%20help%20organizations%20extend%20Office%20365.%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3EBeyond%20Office%20365%2C%20PowerApps%20and%20Microsoft%20Flow%20Plans%201%20and%202%20offer%20additional%20capabilities%20including%20integrating%20data%20outside%20of%20Office%20365%20into%20Office%20365%20experiences%20and%20standalone%20apps.%20We%20are%20introducing%20some%20changes%20to%20simplify%20the%20distinction%20between%20the%20version%20of%20PowerApps%20and%20Flow%20for%20Office%20365%20plans%20and%20PowerApps%20and%20Flow%20Plans%201%20and%202%20(P1%20and%20P2)%20by%20making%20the%20following%20changes%3A%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EEffective%20February%201%2C%202019%2C%20the%20following%20capabilities%20will%20only%20be%20available%20with%20PowerApps%20and%20Flow%20Plan%201%20and%20Plan%202%3A%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CSPAN%3ECreation%20and%20publication%20of%20custom%20connectors%20in%20PowerApps%20and%20Microsoft%20Flow%20%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EHTTP%20custom%20actions%20integrated%20into%20Flow%20outside%20SharePoint%20and%20OneDrive%3C%2FSPAN%3E%3C%2FLI%3E%0A%3CLI%3E%3CSPAN%3EIntegration%20of%20on-premises%20data%20through%20the%20on-premises%26nbsp%3B%20data%20gateway%3C%2FSPAN%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3ECustomers%20with%20active%20users%20of%20these%20features%20will%20get%20an%20automatic%20extension%20until%20January%2031%2C%202020%20or%20the%20expiration%20of%20their%20existing%20Office%20365%20subscription%20term%20(whichever%20is%20longer).%20%26nbsp%3B%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EOtherwise%2C%20if%20you%20have%20no%20active%20usage%20but%20still%20would%20like%20to%20use%20the%20features%20listed%20above%2C%20you%20can%20submit%20a%20ticket%20to%20request%20an%20extension%20via%20Microsoft%20Support%20before%20January%2031%2C%202019%20to%20ensure%20uninterrupted%20service.%26nbsp%3B%20Extensions%20will%20run%20for%20twelve%20months%20or%20the%20expiration%20of%20your%20existing%20Office%20365%20subscription%20term%20(whichever%20is%20longer).%20Your%20ability%20to%20request%20an%20extension%20will%20expire%20on%20April%2030%2C%202019.%26nbsp%3B%20After%20that%2C%20unless%20previously%20extended%2C%20use%20of%20these%20services%20will%20require%20PowerApps%20and%20Flow%20Plan%201%20or%20Plan%202.%20%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EFor%20any%20questions%20about%20the%20specific%20availability%20of%20any%20PowerApps%20or%20Flow%20capability%20in%20Office%20365%2C%20please%20see%20%3CA%20href%3D%22https%3A%2F%2Fpowerapps.microsoft.com%2Fpricing%2F%22%20target%3D%22_blank%22%20data-cke-saved-href%3D%22https%3A%2F%2Fpowerapps.microsoft.com%2Fpricing%2F%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fpowerapps.microsoft.com%2Fpricing%2F%3C%2FA%3E.%20%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EWe%20recognize%20that%20these%20changes%20can%20be%20disruptive%20to%20some%20organizations.%20%26nbsp%3BHowever%2C%20we%20believe%20this%20will%20help%20simplify%20and%20provide%20clarity%20about%20the%20best%20way%20to%20deliver%20tailored%20experiences%20both%20within%20Office%20365%20and%20across%20the%20greater%20ecosystem.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId-1455728994%22%20id%3D%22toc-hId-1569176717%22%3EDecember%202018%20Update%3C%2FH3%3E%0A%3CP%3E%3CSPAN%3EIn%20response%20to%20questions%20we've%20received%2C%20here%20are%20some%20additional%20clarifications%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EAlthough%20makers%20do%20not%20require%20a%20specific%20license%20to%20create%20PowerApps%20and%20Flows%20that%20use%20custom%20or%20premium%20connectors%2C%20users%20of%20Apps%20and%20Flows%20that%20are%20based%20on%20custom%20or%20premium%20connectors%20require%20Plan%201%20or%20Plan%202%20licenses.%26nbsp%3B%3C%2FLI%3E%0A%3CLI%3EOffice%20365%20users%20and%20makers%20do%20not%20require%20elevated%20licensing%20to%20access%20Office%20data%20from%20the%20Graph%20through%20Flow.%26nbsp%3B%20We%20have%20key%20scenarios%20for%20Graph%20exposed%20to%20Flow%20and%20PowerApps%20users%20through%20our%20standard%20Graph%20connectors.%20These%20are%20available%20to%20all%20Office%20365%20users.%26nbsp%3B%20Advanced%20developers%20who%20want%20to%20connect%20to%20Graph%20via%20a%20raw%20HTTP%20call%20have%20been%20able%20to%20do%20so%20since%20September%202017%20with%20the%20premium%20HTTP%20with%20Azure%20AD%20connector.%20This%20has%20been%20a%20premium%20connector%20since%20its%20release%20and%20we%20have%20no%20plans%20to%20change%20this%20requirement%20at%20this%20time.%3C%2FLI%3E%0A%3CLI%3EOffice%20365%20users%20and%20makers%20do%20not%20require%20any%20additional%20licensing%20to%20access%20on%20premises%20data%20from%20Power%20BI%20through%20the%20on%20premises%20data%20gateway%3B%20additional%20licensing%20is%20only%20required%20for%20users%20using%20PowerApps%20and%20Flow%20against%20on%20premises%20data.%3C%2FLI%3E%0A%3CLI%3EOffice%20365-licensed%20users%20and%20makers%20do%20not%20require%20any%20additional%20licensing%20to%20use%20HTTP%20custom%20actions%20inside%20the%20SharePoint%20connector.%3C%2FLI%3E%0A%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-289589%22%20slang%3D%22en-US%22%3E%3CP%3EEffective%20February%201st%2C%202019%20w%3CSPAN%3Ee%20are%20introducing%20some%20changes%20to%20simplify%20the%20distinction%20between%20the%20version%20of%20PowerApps%20and%20Flow%20for%20Office%20365%20plans%20and%20PowerApps%20and%20Flow%20Plans%201%20and%202.%3C%2FSPAN%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E
Microsoft

Over the past two years, we have helped drive the transformation of business processes with Microsoft 365 by helping you create innovative business apps based on tools such as Microsoft Flow, PowerApps, SharePoint lists, Microsoft Forms, and Power BI.

 

We’ve invested heavily and will continue to invest in enhancing and extending the value of Flow and PowerApps and over the next several months we plan to release new capabilities including:

  • Custom reusable canvas controls for PowerApps
  • Responsive design for PowerApps canvas apps  
  • Enhancing SharePoint document libraries with PowerApps and PowerApps forms  
  • Availability of PowerApps and Flow in the US Government sovereign cloud (“GCC”)  

We’ve been amazed to see how you’ve extended the Microsoft 365 platform to build the next generation of business applications with low code or no code requirements. We have some great examples showcased in our Business Apps Resource Center.

 

Office 365 plans include PowerApps and Flow capabilities to help organizations extend Office 365.  Beyond Office 365, PowerApps and Microsoft Flow Plans 1 and 2 offer additional capabilities including integrating data outside of Office 365 into Office 365 experiences and standalone apps. We are introducing some changes to simplify the distinction between the version of PowerApps and Flow for Office 365 plans and PowerApps and Flow Plans 1 and 2 (P1 and P2) by making the following changes:

 

Effective February 1, 2019, the following capabilities will only be available with PowerApps and Flow Plan 1 and Plan 2:

  • Creation and publication of custom connectors in PowerApps and Microsoft Flow
  • HTTP custom actions integrated into Flow outside SharePoint and OneDrive
  • Integration of on-premises data through the on-premises  data gateway

Customers with active users of these features will get an automatic extension until January 31, 2020 or the expiration of their existing Office 365 subscription term (whichever is longer).   

 

Otherwise, if you have no active usage but still would like to use the features listed above, you can submit a ticket to request an extension via Microsoft Support before January 31, 2019 to ensure uninterrupted service.  Extensions will run for twelve months or the expiration of your existing Office 365 subscription term (whichever is longer). Your ability to request an extension will expire on April 30, 2019.  After that, unless previously extended, use of these services will require PowerApps and Flow Plan 1 or Plan 2.  

 

For any questions about the specific availability of any PowerApps or Flow capability in Office 365, please see https://powerapps.microsoft.com/pricing/.

 

We recognize that these changes can be disruptive to some organizations.  However, we believe this will help simplify and provide clarity about the best way to deliver tailored experiences both within Office 365 and across the greater ecosystem.

 

December 2018 Update

In response to questions we've received, here are some additional clarifications:

 

  • Although makers do not require a specific license to create PowerApps and Flows that use custom or premium connectors, users of Apps and Flows that are based on custom or premium connectors require Plan 1 or Plan 2 licenses. 
  • Office 365 users and makers do not require elevated licensing to access Office data from the Graph through Flow.  We have key scenarios for Graph exposed to Flow and PowerApps users through our standard Graph connectors. These are available to all Office 365 users.  Advanced developers who want to connect to Graph via a raw HTTP call have been able to do so since September 2017 with the premium HTTP with Azure AD connector. This has been a premium connector since its release and we have no plans to change this requirement at this time.
  • Office 365 users and makers do not require any additional licensing to access on premises data from Power BI through the on premises data gateway; additional licensing is only required for users using PowerApps and Flow against on premises data.
  • Office 365-licensed users and makers do not require any additional licensing to use HTTP custom actions inside the SharePoint connector.