Microsoft 為 Foundry IQ 加入知識圖譜、Microsoft-Retriever-1 及自動資源配置
Microsoft adds knowledge graphs, retrieval model to Foundry IQ for better AI grounding
Microsoft 為 Foundry IQ 加入知識圖譜、Microsoft-Retriever-1 檢索模型及自動資源配置,協助開發者建立可連接企業資料的 AI 智能體。
Microsoft is enhancing its Foundry IQ knowledge retrieval service with knowledge graphs, a specialized retrieval model and automatic infrastructure provisioning, seeking to make it easier for developers to build AI agents that can access, understand and reason over enterprise data.
Grounding AI agents in organizational data is critical for enterprises to ensure they can deliver responses based on accurate, relevant, and up-to-date business information as they look to increasingly automate business workflows.
The new knowledge graphs in Foundry IQ, announced at the Microsoft Ignite conference, will help agents connect related entities and facts across documents and organize enterprise content into topics, allowing them to answer questions that require information from multiple sources, the hyperscaler wrote in a blog post.
In order to map relationships across documents, developers can add a graph configuration containing their ontology to an existing Foundry IQ knowledge source or bring an existing graph into the service. Foundry IQ then uses the ontology to map how documents, contacts, and information relate, while recording the source of each connection, it added.
Alongside knowledge graphs, which are currently in public preview, the hyperscaler is adding a new retrieval model named Microsoft-Retriever-1 to reduce the number of searches and the reliance on large language models (LLMs) for retrieval planning in an effort to help developers lower latency and token consumption.
The new model, according to the hyperscaler, interprets user queries, reformulates them using terminology found in enterprise documents, and determines whether additional searches are needed to retrieve relevant information.
Developers can enable it on existing Foundry IQ indexes and knowledge bases without requiring additional provisioning or document reindexing, the hyperscaler wrote.
Additionally, to simplify deployment of Foundry IQ, Microsoft is adding a capability that will automatically provision a managed Foundry IQ resource in every new Foundry project.
This means developers will no longer have to provision or manage a separate Azure AI Search resource to create knowledge bases and connect AI agents to enterprise data, the hyperscaler wrote.
The managed service, which will enter public preview in December 2026, will handle the underlying retrieval infrastructure through a usage-based, serverless pricing model, it added.
Reduced developer workload
The combination of the three new capabilities is expected to simplify how developers build AI applications and agents and ground them in enterprise data, analysts pointed out.
“Until now, retrieval could find documents that resembled a question, but it could not follow the connections between them. In response to a question about which products a new regulation affects, a standard search returns the regulation and perhaps a few documents that mention it, leaving the developer to stitch together the chain from rule to supplier to product,” said Ashish Chaturvedi, executive research leader at HFS Research.
“In contrast, knowledge graphs let agents trace that chain themselves and cite each link along the way, reducing the need for developers to manually connect information and build retrieval logic for complex questions,” Chaturvedi added.
The Retriever-1 model, too, could reduce the effort developers spend on building retrieval logic for agents searching across multiple enterprise data sources, according to Stephanie Walter, practice lead of the AI stack at HyperFrame Research.
“It handles decisions such as where to look, what to ask next, and when enough evidence has been gathered, eliminating the need for developers to write that logic manually,” Walter said.
Similarly, automatic resource provisioning is likely to help developers reduce their efforts in building AI agents grounded in enterprise data by eliminating the need to set up the underlying retrieval infrastructure, according to Chaturvedi.
“Grounding agents in company data usually means provisioning a search service, connecting sources, and configuring indexes before any real work begins. Having it ready from the start, on pay-as-you-go pricing, lets developers prototype grounded agents immediately and pay only for what they use,” he said.
Boosting the scalability of enterprise AI
Beyond simplifying development, the three updates could help CIOs improve the reliability, economics, and scalability of deploying AI agents across enterprise workflows, analysts noted.
Knowledge graphs, for one, could help CIOs scale enterprise automation by giving AI agents richer context across enterprise documents, enabling better-informed decisions and more reliable execution of complex workflows, according to Chaturvedi.
Potential applications include regulatory compliance, supply chain risk, contract analysis, and M&A due diligence, where decisions often depend on connecting information across multiple sources, Chaturvedi said.
The Retriever-1 model, too, could help CIOs scale automation as it can help improve the economics of running AI agents at scale, Walter pointed out.
“By using a specialized model for retrieval rather than relying on larger, general-purpose models for every task, enterprises could reduce the overhead of agent-driven applications while improving their responsiveness. This could make it more economically viable to deploy agents across a wider range of enterprise workflows,” Walter said.
Similarly, automatic resource provisioning could help CIOs establish a more consistent and governed approach to connecting AI agents to enterprise data.
“When every project starts with the same retrieval service, CIOs get more consistency in how agents access information and fewer homegrown search setups to secure and maintain,” Chaturvedi said.
The usage-based pricing model could also lower the cost of experimentation, since unused projects would not carry standing infrastructure charges, Chaturvedi added.
Accuracy and cost concerns
However, the three capabilities are also likely to introduce trade-offs.
For knowledge graphs, the primary concern is the accuracy of the entities and relationships identified across documents, Chaturvedi said: “Automated extraction can misinterpret industry jargon, abbreviations, or inconsistent naming, potentially leading agents to draw incorrect conclusions.”
“Developers, therefore, will need to verify that the graph reflects actual business relationships and keep it updated as documents change. Graph-based answers can also take longer and cost more to generate than conventional searches, making them better suited to complex queries than routine lookups,” he added.
For CIOs, though, the bigger worries will be around Microsoft-Retriever-1 and automatic resource provisioning, particularly their implications for cost predictability and dependence.
“The Microsoft-Retriever-1 model could introduce additional latency and processing costs through iterative searches, as each additional retrieval round requires more search operations and processing. That means its benefits will depend on how effectively it determines when enough evidence has been gathered,” Chaturvedi said.
“Hence, enterprises should also test it against their own data, as Microsoft has not published detailed performance comparisons. The model’s retrieval decisions may also be harder to inspect than developer-written search logic”, he added.
Automatic resource provisioning, meanwhile, could deepen enterprises’ dependence on Microsoft’s retrieval stack by making it the default starting point for new Foundry projects, the analyst pointed out.
There could be concerns around its usage-based pricing as well, according to Walter.
“Usage-based pricing could also become less predictable as agents run continuously, requiring CIOs to establish spending limits and eligibility criteria for which projects use the service,” she said.
來源:InfoWorld · infoworld.com