We have now connect to Microsoft Teams and Outlook,
By connecting Microsoft Teams and Outlook with Dynamics 365, we can now work seamlessly from both platforms. This integration brings communication, tasks, and customer data together in one place, making collaboration faster and more efficient. It reduces context switching, saves time, and improves visibility, all while solving real business needs and supporting smarter, more productive ways of working.
We’ve shown you the concept. The roles. The flows. The tech stack. Now let’s talk about how this actually lands in enterprise.
The simple Steve logs into an external portal. Rents recipes. Publishes tenders to print from manufacturing vendors. Monitors production and delivery status. All from the portal interface.
Works great.
But enterprise Steve, the one working at Equinor, IKEA, or Siemens -+doesn’t just browse marketplaces. Enterprise Steve has:
An ERP system
A CRM system
Procurement workflows
Approval chains
Compliance requirements
IT policies
Enterprise Steve needs CraftPortal connected to his world. His tenant. His systems. His processes.
The ISV package bridges these two worlds. Customer data stays in customer tenant. CraftPortal handles the marketplace, IP Owners, Manufacturers, the recipe catalog.
No workflow fragmentation. No copy-paste between systems. No “let me check the other portal.” One flow. Connected.
What Customer Get
Power Platform Components
Component
CraftPortal Examples
Tables
Tenders, Recipes, Vendors, Manufacturers, Bids, Projects, Parts
Dashboards
Tender Overview, Production Status, Vendor Performance
AppSource listing = discoverability, Microsoft co-sell, enterprise credibility
Do this right and CraftPortal becomes invisible infrastructure — always there, impossible to replace
That’s not a customer. That’s a permanent relationship.
The tech stuff
Our ISV package includes two data integration flows. Custom Connector for on-demand requests — direct calls to CraftPortal API when you need real-time actions. Cached Core Data for near real-time sync — we push core data into the customer’s environment via Azure EventGrid into Azure SQL and Dataverse. Why both? Cached data enables full delegation in Power Apps. No query limits. Instant performance. Citizen developers query local tables instead of external APIs. CraftPortal data that feels like their own.
The Code
Azure Function Trigger & Interface
Trigger Type
1) HTTP-triggered Azure Function (API Gateway)
Used for synchronous operations and for publishing events
Secured via Azure AD authentication
2) Event Grid–triggered Azure Function (Event Processor)
Subscribes to Event Grid topic events
Processes vendor integration asynchronously
Updates Dataverse with final status/result
Interface Characteristics
REST-style endpoints
JSON request/response payloads
Versioned route (example):
/api/v1/vendor/operation
The Release
Power Platform Environment Strategy
Source control strategy
Repo structure (example)
/solutions/<SolutionName>/ (exported source using Power Platform CLI/PAC)
/pipelines/ (YAML for CI/CD)
/tests/ (integration test scripts, Postman collections, Playwright scripts, etc.)
/docs/ (release notes templates, runbooks)
CI Pipeline
CD Pipeline
Building the ISV package deliverable
An ISV-style deliverable usually includes:
Managed solution ZIP(s)
Core solution (managed)
Installation guide
Required licenses and prerequisites
Import steps
How to set environment variables
How to create/bind connections
Security roles to assign
Configuration workbook
List of env vars, defaults, required values
Connection references mapping
Any URLs/endpoints
Release notes + known issues
What changed, what to verify
Support / troubleshooting
Common import errors
How to re-run failed flows
Health check steps
Infrastructure as a code
In our solution, we are using both managed power platform ISV and dedicated cloud infrastructure for them.
It means that each customer should deploy his own Azure infrastructure to unlock Power Platform solution distributed via the AppSource.
We are introducing it via the one click Azure infra deployment process. Model driven app has dedicated admin App which is Allowing user run call the deployment by himself after the main package installation.
Note: The selection of the resourcegroup is not part of the BICEP / ARM template. It expects a resource is available. This selection is provided by the portal.
To support that scenarios, We need to provide the all the required bicep files, which are the blueprints for the Azure Services.
Benefits of Bicep
Bicep provides the following advantages:
Support for all resource types and API versions:
Orchestration
Repeatability
The following examples show the difference between a Bicep file and the equivalent JSON template. Both examples deploy a storage account:
Directory Structure
Deployment.
We are using couple of Docker compose files for prod and dev deployment.
It allow us simplify the infrastructure for the local development setup.
Keep in mind that the main rule of using docker-compose: No sensitive data should be hardcoded inside, all environment specific details must be placed to the .env file.
We are following a classic approach with private azure docker registry (ACR) to store frontend and backend docker images.
How to convince IP Owners?
The idea behind is receive all the benefits of owning the infrastructure + extra features of the Platform owner(LogiQraft) like dedicated, specifically designed AI services, Proactive monitoring system, etc…
To make it work, we are using Azure Lighthouse + Managed Identity.
How it works:
The customer delegates a scope (subscription / resource group) to you via Azure Lighthouse.
Your identity in your tenant (this can be:
a Managed Identity, or
a service principal/app)
is granted a role on their resources through that delegation.
You then query their Application Insights / Log Analytics data using your identity, and Azure enforces the delegated RBAC.
Why Lighthouse is ideal:
No need to create/maintain identities in every customer tenant
Customers can revoke access easily
Scales across many tenants
We assume that IP Owners would be careful to share their IP and by following this approach we are addressing their concerns
Categories: Redstone Realm , Governance & Best Practices , Code Connoisseur , Digital Transformation
Badges: Power Of The Shell, ACDC Craftsman, Plug N’ Play
Our CCCP Factory runs on automated AI harvesters working 24/7 in Minecraft. These digital comrades needed real-time visibility into what they should be working on, but they had zero access to operational data. They’d constantly ping managers asking “What should I work on?” or “Is this order urgent?”
The factory management dashboard works great for managers, but harvesters needed their own workspace.
The Solution: Farm Operations Portal
I built a Microsoft Teams app called “Farm Operations Portal” that lives directly inside our Harvester Team channel. It’s basically an operational console for the workforce.
The app shows:
Real-time stock levels for wheat, potatoes, and carrots
Active order queue with customer info
Detailed order breakdowns
Incident reporting (the game changer!)
That last one is huge. Harvesters can now report equipment failures, production bottlenecks, and resource shortages directly into a Dataverse table. Before this, incidents just got lost in chat messages or never reported at all.
Why Teams?
The harvesters are already hanging out in Teams all day. By embedding the portal as a native Teams app, they don’t need to switch platforms. Everything’s in one place: chat, operational data, meetings, and files.
The Results
Before: Constant manager interruptions, lost incidents, confusion about priorities.
After: Harvesters are self-sufficient. Manager interruptions dropped by about 70%. Incidents get logged and tracked. Everyone sees the same data, so coordination improved massively.
The incident reporting alone makes this worth it. We now have a proper feedback loop from the workforce to management that didn’t exist before.
Latest integration is our incident reporting where the harvesters will be able to report incidents directly if something happens in the fields
Our autonomous geological report agent sometimes finds interesting information that our users should be notified about, and given the opportunity (…) to create an opportunity in CRM without having to burn more calories than neccessary.
To achieve this, and to comply with the strict guardrails implemented by the company we work for, we had to utilize a quite alternative approach.
In addition to creating a file in one our trusted SharePoint libraries, a record is written to a table in a storage account in a seperate – more relaxed – tenant… All this is done in a flow:
The flow:
Our awesome proactive bot – created using Teams SDK 2.0 in M365 Agents Toolkit (🪦TeamsFX) will poll this table to see if there have been any new reports made. It will then send messages to users, and making sure a user only receives this notification once – to avoid spam…
Using adaptive cards, the user can choose to either ignore the findings or act upon them by creating an opportunity in CRM.
Adaptive Cards with limitless possibilities (once our map-generating service is ready)
We built an AI agent skill that helps ACDC teams identify their best badge targets and create action plans. It works with Claude Code, VS Code Copilot, and ChatGPT.
What it does
Fetches live ACDC data (badges, teams, claims, rankings)
Matches your project to optimal badge targets
Creates time-boxed checklists with evidence requirements
Generates 30-60 second judge pitch scripts
Installation and usage
Claude Code Drop the `acdc-badge-sniper` folder into your skills directory and invoke it.
VS Code Copilot Copy `copilot-instructions.md` to `.github/copilot-instructions.md` in your project, or paste it directly into Copilot Chat.
ChatGPT / OpenAI Use openai-system-prompt.md as your system prompt or Custom GPT instructions.
Data sources The skill uses live ACDC data and updates regularly to reflect new badges and team standings!
Quick start
Tell your AI assistant: 1. Your team name 2. What you’ve built (2-6 bullets) 3. Your stack (M365, Azure, Power Platform, etc.) 4. Time remaining 5. Constraints (no admin, no external APIs, shorthanded, etc.)
It will return your top 5 badge targets with checklists, evidence requirements, and judge pitches.
Whoever decided that Minecraft had to be blocky and ugly clearly never tried hard enough.
For our solution, we wanted more than just a functional interface. we wanted something you actually enjoy looking at. ooooor something that just pops in your face. Something shiny. Does it add any function? no, but it looks nice.
Is it a little chic? Absolutely. Is it almost too pretty?
Maybe….Pixels well spent. ✨
Plug N`Play
AAAAND, since this mod is a custom plugin we modified for Minecraft (microsoft owned) we can also claim the Plug N’ Play badge 🙂
Whats the business need? making the product pretty to look at of course!
if no one wants to look at it, no one buys it…and thats the truth
In our application, we need to use a plugin for a specific part of our challenges. One of our games involves potion brewing, where we need potion ingredients that are added to an inventory table, which is related to the contact that navigates our tasks.
Greetings, magical developers and hackathon judges! ✨
At Team PowerPotters, we’re always striving to make complex processes simpler and more user-friendly. By embedding key apps directly into Dynamics 365 Finance and Operations (D365FO), we’ve improved usability and responsiveness for potion masters, installers, and approval managers alike. With these integrations, users can now complete tasks faster, more intuitively, and directly from the system they know best.
How We Fulfilled Plug N’Play
1. Incorporating the Resco Component
The Resco PCF component has been embedded into the Installation Details section of production orders in D365FO.
Value Delivered:
Streamlines scheduling and coordination by providing intuitive Resco functionality directly in the F&O interface.
Eliminates the need to switch platforms, ensuring users can manage production and installation workflows seamlessly.
2. Embedding the Alchemy Approval App
Our Canvas Approval App, previously a standalone tool, is now directly incorporated into F&O.
Value Delivered:
Snape and other approval managers can review potion requests, check ingredient availability, and approve or reject orders—all without leaving F&O.
The app retains its dynamic design and responsiveness, allowing approvals on any device or screen size.
3. Developing a Material Consumption Feature in F&O
We’ve created an easy-to-use feature within F&O for adjusting material consumption during potion production.
Value Delivered:
Provides users with a visual representation of ingredient ratios, ensuring precise adjustments to potion recipes.
Improves decision-making by offering a clear view of how changes impact production outcomes.
Why This Fulfills Plug N’Play
Embedded Usability:
All three features—Resco, the approval app, and the material consumption tool—are directly integrated into the D365FO interface, allowing users to stay within one platform to complete critical tasks.
Enhanced User Experience:
By embedding these tools into F&O, we’ve reduced friction for users, enabling them to work intuitively and efficiently.
Responsiveness and Accessibility:
Both the Approval App and the material consumption feature are responsive and user-friendly, ensuring ease of use across devices and user types.
The Impact of Plug N’Play Integration
These integrations have transformed D365FO into a powerful, all-in-one potion production and management hub:
Potion Masters: Can adjust ingredient ratios visually, ensuring precise material consumption and potion quality.
Installers: Benefit from Resco’s scheduling and coordination capabilities, seamlessly integrated into their production workflows.
Approval Managers: Save time and stay productive with the embedded Approval App, designed for quick and informed decision-making.
Why This Earns the Plug N’Play Badge
Our solution perfectly embodies the Plug N’Play philosophy by:
Integrating Directly Into F&O: Embedding apps and features ensures users can complete tasks without leaving the platform.
Improving Usability: Intuitive and responsive tools streamline workflows and enhance productivity.
Delivering Real Business Value: From approvals to material adjustments, these integrations solve real-world challenges and empower users.
With our integrated solutions, we’ve turned D365FO into a user-centric platform that simplifies potion production and management. We humbly submit our case for the Plug N’Play Badge and invite you to explore how Team PowerPotters continues to innovate: acdc.blog/category/cepheo25.
Greetings, fellow wizards and witches of the digital realm!
This afternoon, we are thrilled to announce that our magical journey through the enchanted forest of user interfaces has led us to claim two prestigious badges: Glossy Pixels and Chameleon. 🪄✨
Glossy Pixels: Just like the shimmering surface of the Mirror of Erised, our Power App user interfaces are crafted with a spellbinding glossiness that captivates the eye. These interfaces are not only visually stunning but also resilient, ensuring they won’t shatter like fragile glass on smaller screens. Whether you’re viewing them on a Muggle’s smartphone or a wizard’s enchanted tablet, the glossy charm remains unbroken.
Chameleon: Much like the Animagus who can transform at will, our solutions are incredibly responsive. They adapt seamlessly to all devices and screen sizes, from the smallest of handheld devices to the grandest of desktop monitors. This badge signifies our commitment to creating interfaces that are as versatile as a Polyjuice Potion, ensuring a smooth and consistent experience for all users, regardless of their device.
With these badges, we continue to push the boundaries of digital enchantment, creating user experiences that are as magical as a Patronus charm. Stay tuned for more spellbinding updates as we continue our quest to bring a touch of magic to the world of technology.
Plug N’ Play: In the spirit of the Weasleys’ Wizard Wheezes, we have conjured an app that seamlessly integrates with both Microsoft Teams and SharePoint, bringing a touch of magic to our daily business operations. This app is not just a mere spell; it is a powerful tool designed to solve a crucial business need, ensuring our workflows are as smooth as a well-brewed potion.
Our app, much like the Room of Requirement, adapts to the needs of its users. It enhances collaboration and communication within Teams, allowing us to pull information from various systems, have meaningful conversations about it, and take action—all within the enchanted walls of Teams. Additionally, we have woven our magic into SharePoint, creating a unified experience that ensures seamless access to documents, data, and collaboration tools.
🗺️ Interactive Map: Mapping the Shadows in Style ✨
Our Interactive Map WebApp has masterfully combined modern technology, responsive design, and captivating aesthetics. Developed with React, TypeScript, SCSS, and enhanced with fancy CSS animations, this map is the perfect companion for tracking the mystical operations of the Dark Ledger. With seamless integrations into Microsoft Teams and SharePoint, paired with automated deployments via GitHub Actions, this tool bridges functionality and style, solving critical business needs like a pro.
🔮 Magical Features
1. Interactive Tracking with Google Maps API 🌍
Dynamic Positioning: Real-time tracking shows the locations of both targets and hitmen.
Reward Insights: Visualize mission rewards directly on the map for clarity and motivation.
Custom Styling: The map is tailored to reflect the Dark Ledger’s mystical theme.
2. Cross-Platform Accessibility 🔗
Teams App: Add it directly to Microsoft Teams for quick and easy collaboration.
SharePoint Integration: Embed seamlessly into SharePoint sites to streamline workflows.
Responsive Design: Optimized for desktops, tablets, and smartphones—effortlessly adapting to any screen size.
State Management: Redux or Context API ensures dynamic updates without skipping a beat.
Streams: Real-time syncing keeps the map fresh and up-to-date.
SCSS: Powers cohesive, flexible, and maintainable styling.
4. Dazzling CSS Animations ✨
Fluid Transitions: Map markers and interface elements move gracefully, like spells in motion.
Hover Effects: Intuitive highlighting guides users effortlessly through the map.
Polished Touches: Every button, icon, and menu interaction feels alive and engaging.
5. Automated Deployments with GitHub Actions 🤖✨
The app is built for agility and reliability:
CI/CD Pipeline: Changes pushed to GitHub are automatically deployed to our Azure-hosted web app using GitHub Actions.
Efficiency: Ensures the latest features and fixes are available to users without manual intervention.
Azure Hosting: Provides a robust, scalable platform to support the app’s responsiveness and performance.
💼 Solving Real Business Needs
This isn’t just an enchanting app; it’s a powerful business tool:
Operational Insights: Tracks locations and rewards in real time, empowering decision-making.
Collaboration Simplified: Embeds directly into Teams and SharePoint, making it easily accessible for all users.
Efficiency Boost: Automates key processes and eliminates the manual hassle of location tracking.
🌟 Built for Versatility and Performance
Why It Stands Out:
Responsive Design: Ensures usability across all devices and screen sizes.
Modern Tech Stack: Leverages React, SCSS, and state management for a seamless experience.
Automated Deployments: GitHub Actions streamline updates and ensure consistent quality.
Azure Hosting: Provides a stable and scalable backend for flawless performance.
🖤 Enchanting Efficiency
With React, SCSS, Google Maps API, and Azure-hosted automation, our Interactive Map WebApp stands as a spellbinding example of innovation. Whether you’re plotting missions or tracking rewards, this tool ensures you’re always ahead, wrapped in elegance and functionality.
“When modern magic meets technical wizardry, the results are simply spellbinding.” 🧙✨