AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

foundry-iq

Foundry IQ knowledge bases. WHEN: make local or Blob documents searchable; create/diagnose KBs; triage unsupported connectors or multi-source KB creation/reconfiguration (even with classic-search terms); connect existing KB to agents (including multi-source KBs); create/reuse a Search service; retrieve from an existing knowledge base with citations; no brand words needed. Read its procedure before query/target questions. NOT: other KB providers, repository-file search, classic Azure AI Search index/query/app work with no Foundry IQ KB or connector request, generic agent creation.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--foundry-iq at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 45

references/owner.md

Resource owner default

Use for an unresolved owner in File, Blob/ADLS or KB intake. An explicit supplied owner wins. Preserve a resolved owner through handoffs and exact reuse; never replace it just because the current caller differs. Example owner strings are placeholders, not defaults.

Reuse the already-read az account show result: user.name, user.type and tenantId together, retaining their Azure caller provenance. If account context has not been read, the normal intake can read az account show once. Do not repeat successful discovery just to populate an owner or fetch an access token.

For user.type: user, default the owner proposal to the observed UPN/name or suitable stable user identifier. Show that value and its caller/tenant context in the consolidated plan/confirmation, allow override, and do not add a separate redundant owner question. Do not infer an owner from OS/git identity or guess an email address. Avoid extraneous Graph lookup when account readback supplies a suitable owner.

For a service principal or managed identity, never invent a human owner. Use an observed stable principal owner label only when a nonhuman owner is appropriate to the task or explicitly selected. A generic label such as systemAssignedIdentity alone is not a stable principal identifier. Otherwise, ask one focused owner decision, retaining all other resolved choices. An application ID is not automatically a role-assignment principal object ID.

Missing, failed, malformed or ambiguous caller readback: explain exactly what is unknown and ask one focused owner decision. Unknown caller type or uncertain tenant applicability is not evidence of a human identity. No silent fake fallback, login or context switch. An explicit owner resolves this metadata choice, not a separate authentication/access blocker.

Owner metadata is NOT proof of resource ownership, deletion rights, role-assignment permission or consent. Keep actual ownership/access readbacks, concrete-plan approval and separate cleanup approval unchanged. The default is a proposal, not permission to mutate; helpers still receive an explicit owner.