Tag Archives: SharePoint

Exploring agent development

I’ve been using AI to build software for a while now, including Keepit’s MCP server, a PowerShell module for managing Keepit, Flightmap, M365Mutator, and a variety of other goodies. Recently I’ve started digging into actually developing agents, and this has been an adventurous experience given my lack of experience with most of Microsoft’s developer-platform tools. I thought it would be useful for me to document some of what I’ve learned along the way.

One of the first things I had to get straight is understanding how agents are identified and get access. Within Microsoft’s Agent 365 and Entra Agent ID model, there are three basic access patterns. They differ in whose identity the agent uses and how persistent that identity is.

Delegated agents

A delegated agent acts as you, using your delegated permissions, so it can only reach what you can reach. Its access is ephemeral and tied to the request. If you ask Copilot or Claude to organize your inbox, you’re using a delegated agent; the agent does its work using your identity, governed by whatever policy is attached to your user account. The agent can never do more than your user account can. In the real world, a travel agent is a good example of a delegated agent: she can’t spend more than my credit card limit, and in general can’t do things that exceed my own limits (like sending me to a country where I don’t have a visa).

Autonomous agents

These agents are the type people most often think about. They use their own agent identity, with scoped application permissions, and no user in the loop (although they may be built to require or allow human approval for some actions). For example, a background agent that generates reports on a schedule, or automatically triages support tickets, would fall into this category. For autonomous agents, the policy attaches to the agent identity (or its blueprint, something I’ll talk more about in a future post). Microsoft describes these as “agents operating behind the scenes.” To stay on my travel theme, the rebooking agents that United and Delta operate work this way: they have a policy that controls what the agent may do when there’s a flight disruption, and the agent will make changes to my flights within the bounds of that policy when there’s a delay, cancellation, etc. I may be able to review and approve the change, but I don’t have to trigger it, and the agent’s scope of actions have nothing to do with me as an individual flyer.

AI teammate agents

An AI teammate is an agent with its own Entra user account, which gives it a mailbox, calendar and Teams presence. It takes part in team workflows the way a colleague would, for example in Teams chats. The Planner agent in Microsoft Planner is a good example; I can @-mention it, assign tasks to it which it will try to perform, and so on, exactly as I might work with a real human. Microsoft’s docs say an AI teammate always uses the Agentic-User authentication. Its access is persistent and accumulative, and policy attaches to the agent’s user account. Microsoft’s partner agents from Zendesk, Genspark, Manus and others are deployed this way.

The short version

A delegated agent borrows your identity, an autonomous agent has its own application identity, and an AI teammate has its own user identity. Agent 365 governs all three from one control plane, but the access model, and so the risk profile, is different for each. In addition, you may build, deploy, manage, and monitor these agent types in very different ways, something I’ll have plenty to more to say about in the future.

2 Comments

Filed under General Stuff, General Tech Stuff, Office 365

Fixing SharePoint Online OneNote “something went wrong” errors

I recently ran into a problem with a SharePoint Online site that had previously been created on BPOS and moved around through various iterations of Office 365. None of the site users had ever used the OneNote notebook associated with the site, but the link was present in the side navigation bar. When I tried to access it, I got the infamous “sorry, but something went wrong” error page. (For another day: discuss the Fisher-Price-ization of service error messages; the low information content doesn’t scare end users but makes it impossible to troubleshoot problems.)

A little binging turned up a plausible solution: “SharePoint 2013 OneNote Notebook something went wrong error“. I was a little leery of turning off the feature for fear that it wouldn’t turn back on. However, I took the plunge. After disabling the feature and re-enabling it, I was able to open the OneNote Online notebook, but I wasn’t able to use the “open in OneNote” link until I added some content in OneNote Online. All’s well that ends well. This may not be the only solution for this problem, but it has a 100% success rate for me so far.

1 Comment

Filed under Office 365, UC&C

SharePoint task list shows “read only” when opened in Project 2013

SharePoint Online has a nifty set of features for managing project tasks, but I don’t like its web interface. I prefer Microsoft Project (which makes me a bit of a heretic, but there you have it). SharePoint has a button that will take the current task list and give it to you as an .mpp file, then open it in Project so you can edit it. Sadly, this button only works in IE for Windows; it doesn’t work on my machine when I use Chrome, and of course since there’s no Project version for Mac OS X, it doesn’t work there either.

Anyway, I’ve been using this button a lot, but the other day it just quit working. I’d click the button, the .mpp would open, but Project would see it as read-only, so I couldn’t save edits back to the SharePoint site. I did some digging and found that other users had reported success opening the .mpp directly from the “recently used” file list, but that didn’t work for me. So I posted this thread. Meanwhile, as I waited for an answer, I tried a variety of things, none of which worked. Then, in a completely unrelated set of operations, I signed out of Office 365, changed my account password, and signed back in… and then it worked. Perhaps this fix will prove useful for future generations.

3 Comments

Filed under Office 365

Office 365 beta exams: a few thoughts

Last week I took the beta versions of the two MCSA exams for Office 365: 71-346 is Managing Office 365 Identities and Requirements and 71-347 is Enabling Office 365 Services. I thought it might be useful to write up a few NDA-safe notes on the exams and the topics they cover. Keep in mind that the questions on the beta exam are there because they’re being tested; the objective domains (ODs), or areas of knowledge being tested, won’t change but the specific questions probably will as the beta identifies “bad” questions (those that everyone gets right or everyone gets wrong are immediately suspect!) The Microsoft exam development process is really complicated; to summarize, by the time the exams hit beta, the knowledge areas to be tested are set in stone but the questions themselves can be modified, or thrown out, based on beta exam feedback.

First, be forewarned that there are no formal study materials for these exams. I hear that Office 365 Admin Inside Out from MS Press is decent, but haven’t read it yet. Be prepared to do a lot of binging to look up specific things that you want to know how to do.

Second, the absolute best way to prepare for the exam is to sign up for a trial Office 365 E3/E4 tenant and make sure that you know how to do everything mentioned in the exam objectives in both PowerShell and the GUI. This is baloney, and it has been a hot topic of debate in the MVP community. IMHO there is little value in asking an examinee to show that they know how to do something in PS which is trivial to do in the GUI, especially if it’s a one-time task like setting up Azure RMS. Nonetheless, that’s the requirement.

For 346, specific things you should probably know include:

  • How to add a new tenant, from scratch. This includes choosing a region (and what effect that has), setting the domain purpose, and confirming domain ownership.
  • How to configure DNS records and firewall settings: SRV, CNAME, and MX records, what they point to, etc.
  • How to design ADFS: how to size it, when to use SQL Server instead of WID, and so on. Note that actually doing HA or DR with ADFS is not one of the topics listed in the OD, but you’ll need to know how to do it anyway. The ADFS 2.0 documentation content map is very helpful here.
  • How to administer (parts of) ADFS, including installing it (prerequisites too) on both Windows 2008 and 2012 (but not R2), controlling filtering, and managing dirsync. I have heard that there are questions in the pool that cover ADFS 3.0 but don’t know if that’s true.
  • How you’d conduct a pilot, including how to use connected accounts and mail forwarding.
  • What the different administrative roles in 365 are for and what they can do, including how to manage delegated admins.
  • How to provision / license users through the 365 Admin Center.
  • Basic account management through PowerShell: creating users, modifying their properties, licensing them, etc. Nothing too exotic; I expect most Exchange and Lync admins can do these types of things now without difficulty.
  • How to provision, enable, and administer AD RMS, a surprisingly cool technology that Brian Reid has written about at length already.
  • What the mail flow/message hygiene reports are and what you can do with them
  • How to do daily admin tasks: checking service health, using the RSS feeds, opening service tickets, etc.
  • Troubleshooting using the Remote Connectivity Analyzer and MOSDAL

347 is a little more of a mixed bag because it contains both admin-level material similar to ODs in 346 plus a smorgasbord of other stuff. The most important thing to know here: you must know how to do stuff with SharePoint Online. Out of the 53 questions on my beta exam, 12 of them (22.6%) were related to SPO.  Given that about 0.5% of my actual knowledge relates to SPO, that was a problem. I don’t use it, and I haven’t worked on the SPO-related parts of any deployments for Dell customers, so I was unprepared. Don’t be like me. Be prepared to demonstrate that you know:

  • All about Click-to-Run, including how it differs from MSI installations, how you customize what gets installed, how the installs themselves work, etc.
  • All about Office Telemetry. Never heard of it? Neither had I. Its inclusion in these exams seems a bit odd, since I suspect you’d see people running it before deploying Office 2013 on-prem too. It’s been a while since I was directly involved in the world of desktop deployment, though, so maybe everyone but me knows about them.
  • How to manage SPO site collections, including how to share and unshared them, set quotas, etc.
  • How to provision (including how to license) Excel and Visio Services
  • How to manage proxy, reply-to/default addresses, resource mailboxes, external contacts, and groups in Exchange— standard stuff for working Exchange admins.
  • How to work with archiving policies on both Exchange and Lync, including integration with Exchange 2013’s in-place hold mechanism
  • How to set up Lync settings for external access, including visibility of presence and per-user access to PIC

Again, you need to know how to do these things in both PowerShell and the GUI, despite the fact that many of the tasks in the ODs will be things you do once (or maybe quarterly, at most).

Should you take the beta exams? It depends, I guess. They cost the same as the “real” exam, and they’re subject to the same “Second Shot” MS program that grants you one retake of a failed exam. So you could sign up and take the beta now for $150, then take the real exam for free if you don’t pass. Based on the state of the exam questions I saw, and the lack of structured training materials, I don’t recommend that you rush to take the exam, though; the real version goes live on 17 February. Until then, your time would probably be better spent setting up a scratch tenant that you can play with, then running through the list of ODs to make sure that you know how to do the things on the list.

I’d be interested in hearing from people who took the exam to see how well you think the exam actually matches up with what Office 365 admins and designers need to know in the real world.

1 Comment

Filed under Office 365, UC&C