<p>Please see <a href="https://m365chicago.com" target="_blank">the M365 Chicago website</a> for the latest information about this event!</p>

<p>Visit&nbsp;<a href="https://m365chicago.com/">Microsoft 365 Chicago Virtual Event (m365chicago.com)</a>&nbsp;to see who our sponsors are!</p>

M365 Chicago

Power Platform - Water Tower

Is it enough just not to assign a license to the user? Unfortunately not, because the many options with self-service purchase, free licenses and trials give the user many options to access the Power Platform that do not correspond to their own company roadmap. In this session, we want to take a closer look at the conditions under which people can use the Power Platform, how various settings affect access to the Power Platform, and what other options there are for complying with governance and control instances.

Power Platform Governance - Control access to the Power Platform

X (Twitter)

LinkedIn

Blog

Company Website

Sessionize

You will learn how to create curated experiences in Teams based on your organizations personas.  You will see how 4 different types of employees experience Teams: Deployment Team; Information Workers; Firstline Workers; and Executives.

Create a Curated Experience in Teams!

In this session, we will look at a common budget allocation problem that involves seasonality. Seasonality has a major influence on many businesses. The ability to factor in seasonality in budgets and forecasts could help to create clear and meaningful comparisons with actuals. 

Allocating a high level budget to lower levels of granularity, on the other hand, can be difficult. I'll demonstrate how to split seasonal budgets utilizing Power Query. This will allow us to compare the budget on a quarterly, monthly, and even daily basis. At the end, I'll demonstrate how to use dynamic DAX calculations for effective budget-to-actual comparisons.

Allocation and Visualization of Budgets with Seasonality using Power Query and DAX

Twitter

Citizen Developers can be some of the best product and change champions your organization will ever have - if motivated and managed correctly. In this session, we'll show how many of the tools and techniques we have used in Champion programs in the past should be tailored to motivate and educate citizen developers. We'll also discuss how to help Citizen Devs accept and stay within your governance guardrails. You'll leave with an step-by-step 8 week program, including meeting agendas and a Citizen Developer Guide to make your own.

An 8-week Plan for Engaging, Supporting, and Governing Citizen Developers

In this session, we will review the process of submitting a Power Platform custom connector to the Independent Publisher Connector program for certification. You'll learn the steps required for this community program as well as tips and tricks to build connectors faster and with fewer errors to fix. And by the end of the session, we'll submit a pull request for our connector to the Microsoft repo and start the certification process.

Build and Submit an Independent Publisher Connector in Under 50 Minutes

Microsoft Dataverse for Teams delivers a no code / low code  out of the box data platform for Microsoft Teams. You get relational data storage, rich data types, enterprise-grade governance, and one-click solution deployment. Dataverse for Teams enables everyone to easily build and deploy apps. Come see what Dataverse for Teams is all about and how to get started building databased apps within Teams. 

Getting Data from Dataverse inside of Teams

Taking advantage of the tools such as the CoE Starter Kit's Innovation Backlog application to create practical and useful measures along with some design thinking techniques for creating that master innovation list of solutions that are candidates for Low Code Development in the Power Platform.

Measuring Success in Power Platform with Power Platform Tools

The problem: we expect everyone to adapt and be able to analyze and explore our visualizations. The reality: you’re forcing end-users to adapt to the viz rather than adapting it to their needs.

Key Meeting Insights:
You need to know your audience when building a dashboard. Think about:
-- What does your audience do? What is their role?
-- Why are they coming to you? What do they need?
-- What drives the decisions they make?
Your visuals should behave like text does: context is key.
-- Is the visual help driving the decision? If it’s just nice to look at- then take it out.
-- Everything in a dashboard should help drive a decision.
-- Where can things go wrong in a dashboard?
-- Too much focus on visuals and not on context.
-- Don’t go too broad with your dashboard, have an audience in mind.
-- Understand that not everyone is analytically minded.
How can you win over dashboard users?
-- Do a discovery phase and interview stakeholders in advance.
--Understand their current state and get an idea of their ideal outcome
-- Know what you need to show in advance- what are the requirements
-- How are they going to use the data?
-- Sandbox and version- test out your dashboards in advance. Show all stakeholders how to use and interact with the dashboard. Get feedback and make edits.