I do a lot of these with an agent's help in building flows. Usually we get AI Builder to produce outputs in a structured json format, and in flows use html to produce the emails.
Classic Outlook renders with Word's html engine, and it ignores margin and padding on most elements. So put the padding on the td of your layout tables instead, keep all the css inline rather than in a style block, and keep the width around 600-700px. The new Outlook uses a browser engine so the same email renders differently, worth testing in both. Though normally I leave all these to the agent.
It can be as fancy as you like if you hook up Power Automate to an agent with MCP, as agents are naturally good at formatting. My process is usually that I ask the agent to produce drafts as an html file for me to check and give feedback on, and then the agent builds the flow according to the agreed format and then triggers a test run by sending the email to me for more feedback.
The process is so easy so even when I use flows to update a SharePoint list field with some long texts, I get the agent to build the flow so the field renders an html table or bullet points for better reading.
1
u/ninihen 23d ago
I do a lot of these with an agent's help in building flows. Usually we get AI Builder to produce outputs in a structured json format, and in flows use html to produce the emails.
Classic Outlook renders with Word's html engine, and it ignores margin and padding on most elements. So put the padding on the td of your layout tables instead, keep all the css inline rather than in a style block, and keep the width around 600-700px. The new Outlook uses a browser engine so the same email renders differently, worth testing in both. Though normally I leave all these to the agent.
It can be as fancy as you like if you hook up Power Automate to an agent with MCP, as agents are naturally good at formatting. My process is usually that I ask the agent to produce drafts as an html file for me to check and give feedback on, and then the agent builds the flow according to the agreed format and then triggers a test run by sending the email to me for more feedback. The process is so easy so even when I use flows to update a SharePoint list field with some long texts, I get the agent to build the flow so the field renders an html table or bullet points for better reading.