It just takes a few seconds to connect your Dataverse environment to Git. You can connect and use Git integration within Power Apps, Microsoft Copilot Studio, Power Automate, and Power Pages. You’ll also need access to an Azure DevOps Git repository.

Rollout is in-progress. Git integration is currently available in public geos outside the US. Your environment must be enabled for early access and accessed at https://make.preview.powerapps.com.

As the team develops, Dataverse tracks everyone’s changes. When ready, commit your changes to a branch in the connected Azure DevOps Git repository. A commit link is provided to view the changes within the repository and compare diffs. You’ll notice solutions and solution objects are now stored in human readable formats in the repo.

Professional developers can work in source control while others work in one or more environments. It’s easy to pull others’ changes into other development environments which are connected to the same source code location. This allows team members to build without others editing in their environment and share changes once they’re ready. Connect multiple development environments using the same repo, branch, and folder. Then, in each environment create or import an unmanaged solution with the same name and publisher.

When committing and pulling changes, conflicts may be detected – meaning someone else made conflicting changes to the same object. You’ll need to choose whether to keep the version that’s in your environment or bring the version from source control into your environment. You can also revert changes in the repository, then pull the prior version into your environment.

When the team is ready to deploy to test or production, you can use Pipelines in Power Platform for the release. Building and deploying using developer tools isn’t available yet for this new format.

We hope you enjoy the preview. There are many current limitations and you shouldn’t use this feature in environments or Git folders where you’re developing production solutions. Please leave your feedback below, in the community forums, on social media, or another outlet of choice. We look forward to hearing what you’d like to see prioritized next.

Learn more

Overview of Power Platform Git integration

Setup Git integration

The post Introducing Git Integration in Power Platform (preview) appeared first on Microsoft Power Platform Blog.

With Microsoft 365 Copilot, makers can develop powerful agents directly within Teams. These agents can be tailored to meet specific organizational needs, providing seamless integration and enhanced functionality. But the innovation doesn’t stop there. Now, through Microsoft Copilot Studio now included in Microsoft 365 Copilot, makers can extend the capabilities of these agents, creating robust solutions that drive efficiency and effectiveness.

Once these agents are created, administrators can apply a comprehensive set of features to govern their generative-AI solutions. This includes granular control over sharing and data extensibility, ensuring that sensitive information remains secure and accessible only to authorized users. Additionally, admins gain visibility into usage patterns, enabling them to monitor and optimize the performance of their AI solutions. With tools designed to enforce governance strategies, organizations can confidently deploy and manage their AI initiatives, knowing they have the necessary controls in place.

Key Governance Features

• Copilot governance page in the Microsoft Power Platform admin center: a central administration page to empower admins with guidelines, visibility and controls to manage their Copilots and Copilot agents adoption at scale.
• Data Policies – managing Power Platform connectors: Data policies play a crucial role in ensuring data security and compliance. Data Policies allow IT administrators to permit or restrict the use of specific Power Platform connectors, to prevent the use of unauthorized data sources. See Configure data loss prevention policies for copilots – Microsoft Copilot Studio | Microsoft Learn to learn more.
• Data Policies for blocking Anonymous Access, blocking Publish and more: Data Policies offer admins to configure a set of additional policies dedicated for Microsoft Copilot Studio, these policies allow IT to set access controls and prevent makers from building copilots for non-authenticated users, restrict makers from publishing to specific channels like Facebook, or block makers from publishing their solution all together before certifying the solution by IT.
• Sharing Limits: IT administrators can configure limits to prevent makers from sharing non-certified solutions too broadly. IT can ensure that copilots are shared only with a limited set of users until the solutions are reviewed and are certified, ensuring makers have followed the organization guidelines. This capability is in preview and will be made publicly available shortly.

• Environment Rules, Groups, and Routing: These features allow IT administrators to create environment groups, define environment-specific rules, and route makers to personal development environments to build their copilots. Enterprises can use these features to adopt an advanced environment strategy that allows makers to create copilots and agents in personal environments. And with Pipelines and Solutions Explorer, makers can easily mature the copilots and agents they build from development to production using the streamlined application lifecycle management (ALM) experience, where IT can certify solutions before, they are shared broadly. To learn more about how to manage adoption of copilots at scale using these capabilities see Develop a tenant environment strategy to adopt Power Platform at scale | Microsoft Learn.
• Maker Onboarding: Maker Onboarding simplifies the process of onboarding new makers and developers. IT can provide a custom welcome message to greet makers with step-by-step guidance and resources to help them start building and managing copilot applications. Admins can provide customized welcome content to help makers get started. This content can replace the default first-time help experience and include company-specific resources, training guides, and links to internal events.
• Advisor: Advisor offers administrators a set of out-of-the-box recommendations and best practices guidance to help admins stay on top of the ongoing adoption of copilots and agents. The system continuously scans your environment and identifies copilots and agents that need IT attention. Administrators are provided with regular recommendations on gaps to go address with clear actions to perform to properly respond to these gaps. It helps IT administrators make informed decisions and ensures that their copilot implementations align with organizational guidelines and compliance requirements.
• Catalog: Catalog provides a centralized repository for IT and Center of Enablement teams to offer standard and sharable controls, such as certified custom connectors, official organizational templates and more. IT administrators can easily manage, categorize, and certify reusable controls that then can be easily consumed by makers, simplifying the creation of more complicated solutions, promoting reusability and adherence to company guidelines.
• MIP Labels: Microsoft Information Protection (MIP) Labels provide an additional layer of security and compliance. IT administrators can integrate the Microsoft Copilot Studio with Microsoft Purview sensitivity labels, forcing copilot content to get tagged with labels based on the MIP labels of the Microsoft 365 content, and ensure that sensitive data is properly labeled and managed according to organizational policies.
• Audit Logging to Microsoft Purview:   Copilot audit logging to Microsoft Purview captures interactions and activities within the Copilot environment. This includes logging user commands, responses generated by Copilot, and any administrative actions taken. These logs are securely stored and accessible through the Microsoft Purview compliance portal, allowing for thorough auditing and compliance checks. This ensures transparency, security, and accountability in the use of Copilot, aligning with organizational compliance and security policies.
• Copilot Security checker: Each copilot is designed to be secure by default, but there is a possibility for makers and their admins to adjust settings for specific needs, potentially without being aware of the risks involved. We’re excited to introduce a new feature in Copilot Studio that alerts makers to security concerns.
  Copilot Studio will now automatically perform security assessments and provide warnings to makers before they publish a copilot.
• Security page: in the Power Platform admin center – a consolidated experience that help administrators to navigate the complexities of managing security for Power Platform workloads, including Copilots and Copilot agents, at enterprise scale.

Enhancing Governance Strategy for AI

Including Copilot Studio as part of Microsoft 365 Copilot significantly enhances the governance strategy for AI in your organization. By leveraging these governance features, IT administrators can ensure that all copilot experiences are managed, monitored, and governed effectively. This comprehensive approach to governance not only enhances data security and compliance but also empowers organizations to innovate and scale their AI-powered solutions with confidence.

Leading AI Growth through Governance

The governance capabilities of Microsoft 365 Copilot, combined with the powerful tools available in Microsoft Copilot Studio and the Power Platform admin center, provide IT administrators with unparalleled control and oversight. These features not only ensure that generative-AI solutions are deployed securely and efficiently but also empower organizations to expand their AI footprint with confidence.

IT admins play a pivotal role in this journey, acting as the architects of innovation and the guardians of data integrity. By leveraging the rich set of governance tools, they can manage sharing and data extensibility, gain visibility into usage patterns, and enforce robust governance strategies. This level of control fosters a secure and compliant environment, allowing organizations to fully embrace the transformative potential of generative AI.

As we look to the future, the possibilities are boundless. With the right governance in place, organizations can unlock new levels of productivity, creativity, and efficiency. Microsoft 365 Copilot, along with Microsoft Copilot Studio and the Power Platform admin center, is not just a set of tools—it’s a catalyst for growth and innovation. Together, we can build a future where AI-powered solutions are seamlessly integrated, responsibly managed, and poised to drive success in the digital age.

Learn more:

• Overview – Microsoft Copilot Studio | Microsoft Learn
• Security and governance – Microsoft Copilot Studio | Microsoft Learn
• Develop a tenant environment strategy to adopt Power Platform at scale – Power Platform | Microsoft Learn

The post IT Governance Controls for Your Copilot agents appeared first on Microsoft Power Platform Blog.

As organizations expand their Microsoft Power Platform footprint to meet the needs of their users for application modernization and the inclusion of Microsoft Copilot, administrators can utilize premium features such as managed environments to govern at-scale quickly and easily, while increasing visibility and control. However, as more environments are deployed, administrators need a way to streamline governance and ensure consistency.

Explore more about environment groups and rules in the official documentation.

Making governance at-scale even easier
Environment groups empower admins to establish governance policies through customizable rules, ensuring consistency across environments and eliminating chaos. Microsoft Power Platform administrators can create environment groups. These groups serve as holders for related environments. You can use environment groups to organize your environments by department, project, cost center, or any other relevant criteria, offering a systematic way to manage collection of environments in aggregate.

In each environment group, administrators can uniformly apply six key capabilities of managed environments to all associated environments. These include setting sharing restrictions for canvas apps, utilizing AI to generate app and solution summaries, and enforcing best practices with solution checker—eliminating the need for manual solution checking. This initial suite of rules is just the beginning, with plans to expand in the near future, providing Microsoft Power Platform administrators even greater control over their environment groups.

By joining a group, an environment automatically follows all of the group’s rules. You don’t need to set it up manually. This makes sure that all environments in the group are aligned with the basic standards from the start. To ensure that each environment in an environment group maintains the configuration settings determined at the environment group level, the administrators of those single environments within the group will not be able to alter those settings and fall out of compliance with any configured rules.

Why is environment routing important?

Thanks to environment groups, these environments come preloaded with essential admin settings, including sharing limits and solution-checker, making adoption a breeze for Microsoft Power Platform admins. Previously, new makers had to figure out which environment to work in. With default environment routing, this decision happens automatically. Environment routing is a feature that automatically directs new makers to their personal developer environments instead of the default environment.

Personal developer environments are individual workspaces, similar to Microsoft OneDrive, where makers can confidently build apps and solutions using Microsoft Dataverse without worrying about others accessing their work, assets, and artifacts. Admins no longer need to be concerned about makers accidentally working in the default environment, where their work might conflict with others.

When combining with environment groups and rules, these environments come preconfigured with environment-level governance settings, including sharing limits and solution checker. This feature helps new makers to avoid confusion and conflicts when working in Microsoft Power Platform and helps admins to manage their environments more easily. Learn more about environment routing here.

Next steps
Environment groups and rules streamline management with efficient oversight over multiple environments using a centralized, consistent approach. This ensures uniform standards and configurations across all environments, significantly enhancing developer efficiency by providing ready-made, pre-configured environments that eliminate the need for manual setup. Consequently, this uniform governance simplifies administration and reduces overhead, leading to a more efficient development process. We’re excited to see how organizations continue to develop their Microsoft Power Platform adoption, build centers of excellence, and provide the tools needed for organizations to build modern, enterprise-scale solutions safely and securely.

We value your feedback and want to hear from you on what features and improvements you would like to see added to environment groups and rules. Throughout 2024, we’ll be enhancing environment groups based on user input. Stay tuned for exciting updates.

The post Announcing General Availability of environment groups and environment routing appeared first on Microsoft Power Platform Blog.

Power Platform admins always want to ensure that both current and new users of Microsoft Power Apps can access the resources they need to easily and productively use Power Platform. In the past, admins used welcome emails, made wikis, or established internal portals to assist makers with their learning journey and to help them have a good start.

With the maker welcome content feature, admins can easily customize the welcome content that Power Apps maker portal users see when they first sign in to stay updated on important messages, such as security policies, knowledge bases, the environment’s purpose, and support information that makers need to address their use cases and succeed.

To use this feature, Managed Environments must be enabled. The settings panel for Managed Environments gives you the ability to customize Markdown content and define a URL for the welcome content:

Once a welcome message is set up, makers will see a modal pop up in the maker portal when they enter an environment where this feature is enabled.

Makers can choose not to see this again, and will be able to access it on the Learn page at any time.
Any updates admins make to the content will override the “do not see this again” checkbox and show the updated modal to makers. Because of this behavior, admins can also use the maker welcome content as a “push notification” system. Organizations can use it to provide updated information on policies, prompts to fill out surveys, or information on popular apps. The possibilities are endless!

What’s next?

We are excited to expand the maker welcome content feature to cover the other products in the Power Platform family (e.g., Power Automate, Copilot Studio, and Power Pages). Keep an eye out for more news about this !

We’d like to hear from you
To learn more about the maker’s welcome content, see our documentation here. If you have any feedback to share, please visit our community forum. We’d love to hear how you’re using the maker welcome content!

The post Announcing General Availability of Power Apps maker welcome content appeared first on Microsoft Power Platform Blog.

Today we are excited to announce the public preview of the Microsoft Purview integration with Microsoft Dataverse. Microsoft Purview Data Map will enable automated data discovery and sensitive data classification. The integration will help customers to better understand and govern their business applications data estate, safeguard that data, and improve their risk and compliance posture.

Microsoft Purview integration with Dataverse

With this integration, customers can:

• Create a holistic, up-to-date data map across Microsoft Dynamics 365, Microsoft Power Platform, and other sources supported by Microsoft Purview.
• Automatically classify data assets based on built-in system classifications or user-defined custom classifications and it helps to identify and understand sensitive data.
• Empower data consumers to discover valuable, trustworthy data.
• Enable data curators and security administrators to manage and keep data estate secure, reduce data exposure, and better protect sensitive data.

What is Microsoft Purview?

Microsoft Purview is a family of data governance, risk, and compliance solutions that can help your organization govern, protect, and manage your entire data estate. Microsoft Purview solutions provide integrated coverage and help address the recent increases in remote user connectivity, the fragmentation of data across organizations, and the blurring of traditional IT management roles. These solutions help your organization to:

• Gain visibility into data assets across your organization.
• Enable access to your data, security, and risk solutions.
• Safeguard and manage sensitive data across clouds, apps, and endpoints.
• Manage end-to-end data risks and regulatory compliance.
• Empower your organization to govern, protect, and manage data in new, comprehensive ways.

The post Govern your business applications data with Microsoft Purview appeared first on Microsoft Power Platform Blog.

We are excited to announce the public preview of Default Environment Routing, a new Managed Environments feature that allows Power Platform admins to automatically direct new makers into their own personal developer environment when they visit make.powerapps.com for the first time. Default environment routing offers new makers a personal, safe space to build with Microsoft Dataverse, without the fear of others accessing their apps or data.

Default Environment Routing will allow admins to place their makers in a healthy Application Lifecycle Management (ALM) state from day one by directing them into their own personal developer environment instead of the default environment. With Power Platform pipelines, admins can also create a release pipeline from the created personal developer environment to production. This feature will help customers streamline their environment strategy and offer administrators more control over their makers.

For new makers up until now, the default environment serves as their home environment, which offers a seamless experience and accelerates innovation with the Power Platform. Establishing the same governance guardrails for all the makers in a single shared environment, however, gets more challenging as the maker base of any business grows. Administrators also have a challenge monitoring and managing all the assets in the default environment at scale.

Default Environment Routing is an essential tool for tenant administrators, providing them with the ability to manage their makers’ environment according to their specific governance requirements. This feature will help them to optimize their environment strategy, making it more efficient and secure for both makers and the organization. Admins can customize the governance rules and policies for each individual maker or business unit in their own developer environment as per their needs.

Prerequisites

Default environment routing is a tenant-level, admin setting that:

• Is enabled by Power Platform admins only.
• Requires that the Developer environment assignment setting is enabled for Everyone

• Requires the use of Managed Environment, since all of the newly created environments will be managed. Users in a managed developer environment will require premium licenses to run Power Platform assets.

Enable the Default environment routing setting

The Default environment routing setting is disabled by default and must be enabled using Power Platform admin center or PowerShell.

Enable the feature in Power Platform admin center

1. In the Power Platform admin center, in navigation pane, select Settings.
2. On the Tenant settings page, select Environment routing (preview).
3. In the Environment routing pane, turn on the Create personal developer environments for new makers option.

This feature enables the automatic creation of a personal, developer environment for all of your Power Apps new makers when they first launch make.powerapps.com. The definition of a new maker is limited to the makers who visit make.powerapps.com for the first time. Returning makers who have visited the site before aren’t impacted. The created developer environment will be managed by default and the new makers are assigned the admin role in their newly created developer environments.

IMPORTANT

• Any maker can build apps in the managed developer environments created through default environment routing without requiring a premium license. Nevertheless, since Managed Environments is not included as an entitlement in the Developer Plan, every user who runs assets in these environments will require a premium license. More information on the Managed environments and the Developer plan can be found here
• Non-managed Developer environments are unaffected by the above stated premium license requirements. You can learn more about the developer environment and developer plan here.

Looking forward

Our roadmap includes configuring user roles as well as the automatic configuration of Managed Environments and DLP settings for all new Development environments created through environment routing. Keep an eye out for our release notes where we announce Power Platform new features. We are committed to providing our customers with the best possible experience on the Power Platform, and we are excited to see how our customers will use Default Environment Routing to optimize their environment strategy. To learn more, please check out our updated documentation for the Default environment routing here

See related

Managed Environments Overview

Overview of pipelines in Power Platform

About the Power Apps Developer Plan

The post Streamline your governance and environment strategy using Default Environment Routing (preview) appeared first on Microsoft Power Platform Blog.

The shortcut for this blog post is https://aka.ms/PowerPlatformResources.

I am NEW, help me get started

• Building Tech Intensity with Microsoft Power Platform – Satya Nadella
• The future of App Development – Charles Lamanna
• Overview sites – Power Platform | Power Apps | Power Automate | Power Pages | Power BI | Power Virtual Agents | Dataverse | Security and Governance | Connectors
• Announcements – Low-code announcements at Build | Latest Power Apps features
• Customer stories – 100+ stories | 75+ videos | 25+ hero profiles | Pro-dev stories | Automation stories
• Create your first – Canvas App | Model-driven app | Flow | Dashboard | Chatbot
• Training labs – Power Platform “In a Day” trainings | App in a Day | Automation in a Day | Power Pages in a Day | Power Virtual Agents in a Day | Training modules on Learn
• Take the free Power Platform course on Udacity – https://aka.ms/UdacityPower, #Udacity
• Browse documentation – Power Apps | Power Automate | Power Pages | Power Virtual Agents | Power BI | Dataverse | Connectors
• Sign-in and explore samples and templates – Power Apps | Power Automate | Power Virtual Agents
• Power Platform Admin Center – documentation | portal
• Microsoft Mechanics videos – Power Platform playlist 
• YouTube channels – Power Platform | Power Apps | Power Automate | Power BI | Power Virtual Agents | Power Platform on Microsoft Mechanics
• Community – Community Home | User groups
• Get expert help from partners – https://powerapps.microsoft.com/partners/
• Licensing – Understanding Power Platform licensing article | licensing guide | FAQ
• Resources curated by the community each week – Power Platform Weekly

I have SOME EXPERIENCE

• *new* Power Platform Adoption – homepage | workbook | best practices | maturity model 
• Power Platform Guidance Center – documentation | architecture video series
• 2021 updates – April 2021 launch event | Demo by Charles Lamanna
• 2021 release waves: Wave 2 (Oct 2021 – Apr 2022) | Wave 1 (Apr 2021 – Sep 2021)
• Latest shipped features – Weekly release notes
• Conference sessions – Ignite 2021 | Power Platform Community Conference | Ignite 2020
• Intermediate / advanced architecture series – Power CAT Live
• Useful Power Apps reference – Controls and properties | Formulas
• Power Apps Component Framework (PCF) gallery – community gallery
• Additional labs – Power Platform labs and challenges | Power Platform labs
• Power Automate how-to videos – webinars and videos gallery
• Power Automate guidance – Enterprise automation techniques for RPA | Planning a Power Automate project
• Real-world usage patterns – architecture patterns | scenario patterns | index of stories by scenario category

I am interested in ADMINISTRATION & GOVERNANCE

• Power Platform Admin Center – video | documentation
• Power Platform Governance – whitepaper | Admin in a Day lab | blog posts
• Establishing a Center of Excellence – CoE Starter Kit | videos | adoption maturity model
• Power Platform Governance Enhancements – Feb 2021 – blog post
• Power Platform Guidance Center: documentation | architecture video series
• Conference presentations: Ignite 2020 | MBAS 2019 |
• Build a customized Admin experience using the Power Apps admin connectors – blog post with sample admin dashboard | admin connector documentation
• Strategies for improving app discoverability in your enterprise – part 1 | part 2 | part 3
• Security and certifications – Microsoft Trust Center
• Manage Power Apps licenses in your organization – documentation | FAQ | licensing guide | planning and managing licensing and capacity (Ignite 2019)
• Pricing and licensing – Summary | Licensing documentation
• Licensing Terms & SLA information of Microsoft Power Apps and other online Services – Online Services
• Microsoft’s approach to deploying Power Apps for all employees – blog post |  Pat Dunn’s presentation at Biz Apps Summit

Resources for PRO DEVELOPERS and FUSION TEAMS

• Microsoft Power Platform is the best way for teams to build together – blog post with resources
• Pro-dev features and learning paths – webinar | learning path | ebook | BUILD session
• New Power Apps developer plan – get started | documentation
• Microsoft Mechanics episode on pro-dev adoption of Power Platform – blog | video
• Low code application development on Azure – landing page | YouTube video playlist | tours
• Power Apps and Microsoft Azure better together – landing page | TEI report | ROI calculator
• POWERful Devs virtual conference and ongoing videos – video series
• Additional pro-dev topics:
  • Azure APIM Connector on the Power Platform – blog post
  • GitHub actions for Power Platform – blog post
  • Power Apps for enterprise developers – documentation
  • Register and use custom connections – documentation
  • Build and certify your own connector – blog post | documentation
  • Power Apps Component Framework (PCF) – documentation | community gallery
  • Calling Azure AD protected Azure Functions using a Custom Connector – blog post | documentation
  • Register and use custom connectors in Power Apps 

I am a MICROSOFT PARTNER

• Start at https://powerapps.microsoft.com/partners/
• Join the Power Apps Partner Program
• Become a Recognized Solution Architect
• You can also sign-up to deliver trainings for our customers
• View Power Platform partner stories

Show me REAL WORLD CUSTOMER STORIES

• The curated stories list is now being maintained at – https://aka.ms/PowerPlatformStories
• Additional links – customer story videos | pro-dev stories | automation stories | hero profiles

How do I GET INVOLVED and STAY CONNECTED

• Ways to collaborate with the Power Apps team – blog post
• Stay updated – product team blog | webinars
• Community sites – main community page | forums | community blog | best practices & app gallery
• Get support – blog post | support page
• Submit an idea

COPILOT AND GENERATIVE AI

CONNECTORS AND DATA INTEGRATION

• Power Platform connectors – documentation | Power Automate connectors list
• Data integrator – documentation
• Power Query – documentation
• On-premises data gateway – documentation
• Common Data Model – documentation and printable CDM poster
• Microsoft Dataverse and Power BI – documentation
• Introduction to the Microsoft Common Data Model – Ignite 2019 talk

I use SHAREPOINT, how can I integrate with Power Apps

• SharePoint welcomes Power Apps and Flow
• Integrate Power Apps with SharePoint Online
• The Power Platform for SharePoint people (Ignite 2019)
• Power Apps, the successor to InfoPath | Modernize InfoPath forms with Power Apps
• Custom list forms in SharePoint with Power Apps – blog post | demo | documentation
• Reinvent business processes in SharePoint – blog post
• Pro tips for transitioning from InfoPath to Power Apps – part 1 | part 2
• Embed Power Apps in SharePoint pages – blog post
• SharePoint Online document libraries supported in Canvas apps – blog post | documentation

I use ACCESS WEB APPS, how can I leverage Power Apps

• Introduction to Microsoft Power Apps for Access web apps developers
• Access Services in SharePoint Roadmap

LABS, CERTIFICATIONS, COURSES & BOOKS

• Summary list of labs and training content – https://aka.ms/PowerPlatformLabs
• Microsoft certifications – Power Platform Exams & Certifications | PL-100 | PL-200 | PL-400 | PL-900 |
• Pluralsight – Microsoft Power Platform Fundamentals
• LinkedIn Learning – Power Platform classes
• Udemy – Power Platform classes | Power Apps | Power Automate | Power BI
• Power Platform Academy by Rory Neary – free courses
•  Books:
  • Pro Microsoft Power Platform (published by Apress)
  • Learn Microsoft Power Apps (by Matthew Weston)

BEST PRACTICES & COMMON USE CASES

• Community content – community app and component gallery | working with data | design discussion
• UX/UI design tips – video | UX patterns | managing fonts and colors
• Performance best practices: documentation | optimization techniques | performance considerations | more tips
• Power Apps accessibility guidelines – blog post
• Customize list forms in SharePoint with Power Apps – blog post | demo | documentation
• Access web apps migration to Power Apps – whitepaper
• Approval workflows – blog post |documentation | guided learning
• Using the on-premises gateway – overview | installation & FAQ | proxy configuration
• Build an offline app – blog post
• Creating dialogs in Power Apps – blog post | video
• Display a map using the Image control – step-by-step walkthrough | video
• Send an email from your Power Apps app – video
• Connect to Microsoft Cognitive Services – video
• Implement role-based security – blog post
• Build a customized interactive calendar – step-by-step guide
• Notify user that new data is available – step-by-step guide | push notifications feature
• Deep link into an app using URL parameters – step-by-step guide
• Audit scenario solution – blog post from community member

PRODUCT PAGES

Power Apps

• Website | Blog | Documentation | Community | Suggest Ideas | Webinars
• Product updates
• Guided Learning | YouTube playlist
• Licensing / Pricing
• Support – known issues | view/report issues | create a support ticket

Power Automate

• Website | Blog | Documentation | Community | Suggest Ideas | Webinars
• Product updates
• Guided Learning | YouTube Playlist
• Licensing / Pricing
• Support

Copilot Studio

• Website | Blog | Documentation | Community | Suggest Ideas 
• Licensing / Pricing

Power BI

• Website | Blog | Documentation | Community 
• Product updates
• Guided Learning | YouTube Playlist
• Licensing / Pricing

The post Microsoft Power Platform: Learning Resources appeared first on Microsoft Power Platform Blog.

Microsoft Power Platform empowers you to do more with less by making it easier than ever to securely scale low-code adoption, increase organizational collaboration, and infuse AI and automation into all your business processes. Microsoft Power Platform comes with advanced risk and compliance features that give you an easy cost-effective way to cover your risks and compliance needs.

Protecting your data and meeting your compliance needs

CMK allows customers to meet their data and privacy regulatory requirements, and to meet the enterprise promise on enabling customers with greater control over the security of their data.

Encryption is one of several defenses-in-depth that are available to secure storage. All the customer data and configuration information stored in Power Platform is encrypted at rest with strong Microsoft-managed encryption keys by default. Using CMK provides added data protection control, by allowing customers to manage their own encryption keys. When managed key encryption is used, all business-critical data is encrypted with a user-provided Azure Key Vault key. This provides the ability for customers to rotate/swap the encryption key on demand. It also provides the ability for customers to revoke Microsoft’s access to sensitive information by revoking the access to the key, at any time.

The control and management of using your own key to encrypt data at-rest is one of the main risks and compliance requirements for enterprises using Cloud software-as-a-service applications. Power Platform provides this CMK service in a cost-effective way to help you meet your needs.

Mercedes Benz has found success with CMK in Dataverse overarchingly, as it’s made it easier for them to build more complex solutions on their enterprise-data. 

“Preventing other parties from accessing data stored in the cloud has been a key concern for Mercedes-Benz from the beginning. This is becoming even more important as we embraced the “cloud-first” paradigm striving to make the most out of cloud capabilities. We deem the risk so severe that we do not allow confidential data to be stored in the cloud if that risk is not mitigated properly. This made the use of Dataverse and the low-code/no-code capabilities complex using the Power Platform. Microsoft’s new security features help a lot in this regard, CMK being the key aspect but not underestimating the rest like IP-based cookie binding and IP firewall, subnet delegation, and others. While the features in [themselves] are changing the game, the support, consulting, and help implementing these are a constant boon for our security efforts and just one more reason why we place our trust in Microsoft’s Power Platform.”

—Patric Liebelt, Lead Center of Enablement Microsoft Power Platform, Mercedes-Benz

How do you control and manage your encryption key

The Azure Key Vault admin creates a key vault and generates an encryption key. A Power Platform Enterprise policy is then created which points to the key. The key vault admin grants the Power Platform Enterprise policy access to the key vault to read the key, and then grants a Power Platform local admin Read access to the Power Platform Enterprise policy.

The Power Platform local admin logs into the Power Platform Admin Center (PPAC) and add the Power Platform environment to the Power Platform Enterprise policy. All the environment data is automatically encrypted with the encryption key.

You can choose to add one environment or multiple environments for each Enterprise policy. And you can remove the environment from the Enterprise policy at any time to revert the encryption back to Microsoft-managed key.

Customer has total control of the encryption key that resides in their own Azure Key Vault. Microsoft Support staff does not have access to your key vault and/or your key, and therefore you have overall control over how and when your data can be used. If you delete or revoke access to your key vault and/or the key, all the environment(s) that is encrypted with the key will be disabled and can no longer be accessible by your users and/or Microsoft.

Learn more

Manage your customer-managed encryption key in Power Platform – Power Platform | Microsoft Learn

The post Announcing General Availability for Power Platform Customer-managed key (CMK) appeared first on Microsoft Power Platform Blog.

To use this feature, Managed Environments must be enabled. The settings panel for Managed Environments gives you the ability to customize Markdown content and define a URL for the welcome content:

Once a welcome message is set up, makers will see a modal pop up in the maker portal when they enter an environment where this feature is enabled.

Makers can choose to not see this again, and will be able to access it on the Learn page at any time.

Any updates admins make to the content will override the “do not see this again” checkbox and show the updated modal to makers. Because of this behavior, admins can also use the maker welcome content as a “push notification” system. Organizations can use it to provide updated information on policies, prompts to fill out surveys, or information on popular apps. The possibilities are endless!

We’d like to hear from you

To learn more about the maker welcome content, see our documentation here. If you have any feedback to share, please visit our community forum. We’d love to hear how you’re using the maker welcome content!

The post Announcing admin-configured maker welcome experience in Power Apps appeared first on Microsoft Power Platform Blog.

We’ve put together a simple solution (Power Platform Administration Planning) that is designed to help you better:

• Plan your team structure
• Review where you spend time and look for automation or innovation opportunities

The solution is built on Microsoft Dataverse and is a new stand-alone component in the CoE Starter Kit. Admin tasks are defined in a model-driven app and insights are provided in a Power BI dashboard.

You can start either by adding your own tasks or by importing a set of example tasks from an Excel spreadsheet, populated with some of the most common administration tasks covering:

• AI Builder
• Environments and connectors
• Power Apps
• Power Automate
• Power Pages
• Power Virtual Agents

You’ll need to review the tasks and populate task metadata to get the best out of the Power BI dashboard.

Plan your team structure

If you’re getting started, you might find importing the sample tasks spreadsheet a great starting point for inspiration. Where possible, we added in the most common administrative tasks that administrators perform and supplied links to supporting/ instructional documentation.

Task metadata is used by the dashboard to provide useful information about your team structure and the level of expertise required to complete your administrative work.

Review where you spend time

You may already be administrating the platform and looking for ways to increase your maturity, looking for automation or innovation opportunities.

When you add your own estimation of which tasks you need, how much time you’ll spend doing them, and who will do them, the dashboard will indicate if the size of your team is sufficient, roles and experience levels and an estimate of how much time to expect to spend administering the platform. After your team has been doing the work for a while, you can update with the exact data.

Admin tasks in the model driven app

Tasks can be imported from the sample spreadsheet or manually created.

Tasks have the following schema:

Power BI dashboard

The structure of the dashboard is designed to help you focus on what you do, how reactive your team is, and the impact that automation and outsourcing (if your organization does) has on your overall efficiency.

Team, outsourcing and automation

Team, outsourcing and automation aggregates administrative task data, indicating:

Team workload – enter the number of staff in your team. Based on aggregated effort, the required hours (per team member) to complete the tasks are estimated.

Outsourcing – what, if any, impact outsourcing is having on your workload. How many resources, and what level of expertise is required.

Automation – This section provides insights into how much time you’re saving by automating tasks and the expertise that would be required.

Task breakdown – proactive & reactive balance

Task breakdown – proactive & reactive balance helps focus on the balance between tasks that are ad-hoc, or reactive. By displaying the percentage of tasks that have been categorised as ad-hoc, and providing a filtered list, it encourages you to look for automation, outsourcing or innovation opportunities.

Team breakdown – experience & personas

Task breakdown – experience & personas aggregates the duration for all tasks by frequency and provides insight on:

Experience levels required – illustrates the experience required across all tasks. This can be useful in estimating training requirements for your existing team

Insight for each ‘core admin persona’ & ‘peripheral persona’ – is useful to understand how many of your tasks rely on additional teams to complete. For example: creating an environment may also require Azure AD Security groups to be created for managing access.

Task overview: experience, persona & categorization

Administrative tasks are categorized, which is useful in understanding where your team spends the most time. Tasks have two categories to provide deeper insight. For example: selecting ‘Reporting’ will not only filter the list of administrative tasks to display tasks categorized with reporting, it will also display tasks by their secondary category. Especially useful to understand what type of reporting your team is focusing on, and how much time they are spending completing this.

Where you can get it

Microsoft Power Platform Administration Planning is a standalone module in the CoE (Center of Excellence) Starter kit, which means it’s open sourced and available for download from the same GitHub repository as the toolkit is. Setup guidance and further information is available.

Watch the Power CAT Live! video where we go into more detail about this solution:

The post Power Platform Administration Planning appeared first on Microsoft Power Platform Blog.