79 posts tagged with "Microsoft"

A SharePoint site is where lists, libraries and pages live. When a site only needs to hold data or publish information, you don't want a Microsoft 365 group, a shared mailbox or a team created along with it. A communication site is that plain site, with nothing else attached.

Microsoft 365 only knows who reports to whom if somebody tells it. That "somebody" is the Manager field on each person's account, next to their Job title. Fill them in, and Outlook, Teams and the apps you build all know who someone's manager and direct reports are, and what their role is.

Before anyone can sign in to Microsoft 365, they need their own user account. An account on its own isn't enough, though: until it has a license, the person can't use Outlook, Teams, SharePoint or Power Apps. The Microsoft 365 admin center creates the account and assigns the license in one short wizard. You'll use it here.

Power Apps keeps numbers the way a calculator does — 123456.789 — but the people using your app expect to read 123,456.79. The Text() function converts a number or integer to text and formats it in the same step, as long as you know the one situation where it silently does nothing.

Team addresses such as support@ or sales@ are often distribution lists, and a customer should get the answer from that address — not from whichever teammate happened to pick the message up. Outlook on the web can send from the list, but the From line you need is hidden until you ask for it.

A team address like support@ is usually a distribution list — and creating the list is only half the job. Until someone has Send As permission on it, the team can receive mail at that address but cannot reply from it, and that permission lives in a different admin center from the one where you create the list.

Sooner or later a flow needs to find a person — the manager to notify, the owner of a request, the account behind an email address. The Search for users (V2) action from the Office 365 Users connector does exactly that: give it part of a name or an email address and it returns every matching Microsoft 365 user.

Power Automate is strict about data types. If you try to concatenate a number into a message, save it into a text column, or pass it to a connector that expects text, the flow fails with a type mismatch. The fix is the built-in string() expression, which converts a number or integer into its text or string representation.

When creating an AdapterWithErrorHandler class that inherits from CloudAdapter, you might encounter this compile error:

Argument 3: cannot convert from 'Microsoft.Extensions.Logging.ILogger<Microsoft.Agents.Hosting.AspNetCore.IAgentHttpAdapter>' to 'Microsoft.Extensions.Logging.ILogger<Microsoft.Agents.Hosting.AspNetCore.CloudAdapter>'

This happens because you're passing ILogger<IAgentHttpAdapter> to the CloudAdapter base constructor, but it expects ILogger<CloudAdapter>.