Copilot Studio

Microsoft IQ gone missing from new experience

(0) Share

Report

Posted on by SB-05081215-0

Hi all,

Microsoft IQ was previously surfaced in the new experience as below:

I have been away from the designer for a few days and upon returning today, I notice that Microsoft IQ is no longer appearing in the new experience:

I had connected my agent to a Foundry IQ knowledgebase previously.
When I run a preview interaction with the agent, I can see the knowledgebase is still present and being called by the agent, however, the connection no longer appears in the designer.

Is anyone else seeing this behaviour?

Thanks

Categories:

Model context protocol

General topics

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

sannavajjala87 826 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi,

I'm seeing something very similar in the new experience.
Previously, Microsoft IQ appeared as a separate configuration area in the agent designer. imageturn17search59†image.png(Image: Microsoft IQ section visible in designer)
More recently, some environments appear to show only Model, Skills, Tools, Knowledge, Connected agents, and Memory, with the Microsoft IQ section no longer visible. imageturn17search60†image.png(Image: Microsoft IQ section missing from designer)
The interesting part is that your agent is still successfully querying the Foundry IQ knowledge base during preview. That suggests the underlying connection and configuration still exist, even though the authoring experience is no longer exposing the Microsoft IQ configuration pane.
My guess is that this is related to an ongoing UI/feature rollout in the new Copilot Studio experience rather than a problem with your agent. We've seen several preview features move between sections or temporarily disappear while Microsoft updates the designer.
A few things I'd check:

Verify whether the behavior is the same in another browser or InPrivate session.

Compare the affected agent with a newly created agent in the same environment.

Check whether the Foundry knowledge source now appears under Knowledge or another configuration area instead of Microsoft IQ.

Verify with another maker in the same environment to determine whether it's tenant-wide or user-specific.

Since the knowledge base is still being invoked successfully during preview, I wouldn't remove or recreate the connection. The runtime configuration appears to be intact; it's the designer representation that's missing.

I'm curious whether others are seeing the same thing. It would be useful to know if Microsoft IQ has been folded into another section of the new experience, or if this is simply a temporary regression in the current UI.

Thanks & Regards,

Manoj Annavajjala

www.powerplatformengineer.com

Was this reply helpful? Yes No
SB-05081215-0 2 on at

Like
a
(0)

Report
Copy link

Link copied!

@sannavajjala87

Thank you for your reply.

To answer your additional queries below:

Verify whether the behaviour is the same in another browser or InPrivate session.
The scenario is the same regardless of browser or machine.

Compare the affected agent with a newly created agent in the same environment.
The scenario is the same for a newly created agent in the same environment.

Check whether the Foundry knowledge source now appears under Knowledge or another configuration area instead of Microsoft IQ.
I cannot locate any reference to the Foundry IQ resource anywhere within the agent designer.

Verify with another maker in the same environment to determine whether it's tenant-wide or user-specific.
All makers experience the same symptoms regardless of environment

I have noticed that the new Copilot Studio experience is changing frequently, so as you say, perhaps Microsoft IQ is being moved elsewhere...

Thanks
SB

Was this reply helpful? Yes No
Dua Sadiq 10 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi SB,

One thing worth flagging before you go further: since the Foundry IQ binding is invisible in the designer but still live at runtime, the risk is what happens if you republish. Publishing may overwrite the agent definition from what the designer currently shows which no longer includes the IQ binding and silently drop your grounding.

I'd test this carefully in a non-critical copy first: republish, then run a preview interaction and confirm the knowledge base is still being called. If it survives, it's a cosmetic UI issue. If it doesn't, the takeaway is don't republish until Microsoft restores the pane.

Also worth checking whether the binding is still visible in the solution/connection references layer, even though it's gone from the designer.

Thanks,

Dua

Was this reply helpful? Yes No