Session 3 — Based on the course by Barbara Andrews, Lead Microsoft Technical Trainer
Manufacturing companies give suppliers a secure portal to access inventory data, update delivery timelines, and share logistics plans — replacing scattered emails.
Staff independently access HR documents, submit leave requests, enroll in benefits, or complete training without relying on HR or management.
Customers submit support tickets, track orders, or update account profiles without human intervention — improving satisfaction and reducing overhead.
Faculty check payroll, submit professional development requests, or organize course schedules. Students access enrollment info via an AI agent.
Agents and brokers access shared property listings, marketing assets, and transactional details to collaborate and close deals faster.
Government employees access policy documents, submit expense claims, or register for workshops — simplifying previously manual processes.
| Method | Best for | How it works |
|---|---|---|
| AI-powered Copilot | Non-developers wanting fast setup | Describe site purpose, users, and features in natural language. Copilot generates site name, address, homepage layout, and additional pages. Then refine in Design Studio. |
| Manual from scratch | Users wanting full control | Start with a blank canvas and design every detail to meet specific, unique requirements. |
| Developer / pro-code | Advanced scenarios needing custom code | Access tools like Visual Studio Code, GitHub, and Azure DevOps. Integrate custom APIs and advanced functionality beyond low-code scope. |
Input a natural language description of the site (e.g., "create a site for project management"). Copilot interprets the intent and generates a site structure.
Copilot presents layout options aligned with the described use case. Choose the visual structure that best fits the need. Can regenerate for more options.
Specify initial pages to include (e.g., dashboard, contact forms, resource libraries). Common templates like About Us and FAQ are offered. Site is generated and opens in Design Studio.
Create, edit, and arrange web pages and site navigation
Theming, color palettes, fonts, buttons, branding
Connect to Dataverse, manage tables, forms, and views
Site settings, performance, integrations, security
| Provider | Best for | Example scenario |
|---|---|---|
| Microsoft (Entra ID) | Internal / employee portals | Corporate intranet restricting access to verified company accounts |
| Partner / professional portals | Event registration site where professionals log in with existing credentials | |
| Public-facing / consumer portals | Customer service site where consumers log in with familiar credentials | |
| Other third-party | Specialized audience needs | Custom OAuth providers for specific industry or regional requirements |
Navigate to powerpages.microsoft.com. Paste the Copilot prompt to describe the event management site. Set name to "Contoso Event Management" and URL to "eventmanagement." Click Next to pick a layout, then add pages (About Us, FAQ, and others). Click Done — site is generated and opens in Design Studio.
Upload the Contoso logo image to the header. Change the site background by uploading a background JPG from the GitHub lab assets. Use the Paintbrush panel for overlay, border, and layout adjustments.
Open the Data workspace → Forms tab. Create two forms on the Event table: (1) "Create Event" — for adding new event records, and (2) "View Event" — for viewing records (includes a subgrid showing Active Event Sessions with Show Related Records enabled). Save and Publish both forms.
Create four new pages using Copilot: New Event (form mode: Create new record), View Event (form mode: Read-only), Edit Event (form mode: Update existing records), Events (list mode — displays Active Events with Create New Event, See Event, and Edit Event action buttons). Clean up extra sections on each page, keeping only the form and copyright footer.
Events page list: Permission name "Events," table = Event, access = Read, roles = Administrators + Anonymous + Authenticated. New Event page: table = Event, access = Read + Create, same roles. Edit Event page: table = Event, access = Read + Update, same roles.
Reorder pages: Events moved below Contact; New Event, View Event, and Edit Event nested as subpages under Events. Sync the site, then use Preview to see desktop and mobile views.
| Form name | Table | Data mode | Page used on |
|---|---|---|---|
| Create Event | Event | Create new record | New Event page |
| View Event | Event | Read-only (+ Event Sessions subgrid) | View Event page |
| Edit Event (based on Create Event) | Event | Update existing records | Edit Event page |
| Permission name | Table | Access type | Roles assigned |
|---|---|---|---|
| Events | Event | Read (global) | Administrators, Anonymous, Authenticated |
| Create Events | Event | Read + Create | Administrators, Anonymous, Authenticated |
| Edit Event | Event | Read + Update | Administrators, Anonymous, Authenticated |
Click to reveal answers ↓