The NIC MAP agent lets Microsoft 365 Copilot call the NIC MAP API directly from inside your Microsoft 365 tenant. Once it's deployed, anyone you give it to can ask Copilot questions in plain English, in Microsoft 365 Copilot or in Teams, and have it pull live NIC MAP senior-housing data into the answer: market analyses, competitive sets, occupancy and rent trends, sales comparables, construction pipeline, and more.
Who can use the connector? The connector currently supports Market Insight + Local Property Search subscribers. We hope to add support for Industry Insight and Trends in the future.
How it works
A Microsoft 365 administrator builds a small agent in Copilot Studio that points to NIC MAP's Model Context Protocol (MCP) endpoint, then publishes it to Copilot and Teams. Each user signs in to NIC MAP once over OAuth, so every request is authorized against that user's own NIC MAP entitlements. There are no shared service accounts, and each person sees only the data their own subscription includes.
What you'll need
Administrator
Copilot Studio access, with Copilot Studio credits or pay-as-you-go billing enabled.
AI Administrator or Global Administrator role, plus the Teams Administrator role.
A NIC MAP login with MCP access, to connect and test the agent.
nicmap-icon.png, the NIC MAP agent icon. Download nicmap-icon.png
End users
Microsoft 365 Copilot Chat, which is included in most Microsoft 365 business plans. A paid Copilot license is not required.
Their own NIC MAP credentials. These are the same email and password used to sign in to nicmap.com.
MCP server details: https://api.nicmap.com/mcp Name it NIC MAP · OAuth 2.0 · Dynamic (with discovery)
This guide is in two parts:
Part 1 · Admin setup: One-time, about 30 minutes, plus up to 24 hours for the agent to reach users. Done by a Microsoft 365 administrator in Copilot Studio and the Microsoft 365 admin center.
Part 2 · User setup: Per user, about 2 minutes. The first time someone asks NIC MAP a question, Copilot walks them through signing in to their own NIC MAP account. After that, the agent is live in every chat.
Before you start: how pricing works
Using NIC MAP in Copilot involves two separate costs, billed by two different companies.
| NIC MAP | Microsoft |
What you pay for | Your NIC MAP subscription, including MCP access. | Copilot Studio credits, used each time the NIC MAP agent answers a question. |
Who bills you | NIC MAP. | Microsoft, through your Copilot Studio capacity packs or pay-as-you-go billing. |
Who it applies to | Each user, per your NIC MAP subscription. | Every user of the agent, including users with a paid Microsoft 365 Copilot license. |
Limits | A daily quota on creating new analyses. Reading data from existing analyses doesn't count against it. | Your credit balance, plus any monthly limit you set in Step 10. |
Good to know:
A paid Microsoft 365 Copilot license is not required, and it does not cover this agent's credit usage. Licensed and unlicensed users both consume credits.
Microsoft sets credit rates, not NIC MAP. See Microsoft's Copilot Studio billing and licensing page for current pricing.
Credit usage grows with how much your users ask. Set a monthly limit and track usage in Step 10.
Questions about your NIC MAP subscription go to your NIC MAP account team. Questions about credits and billing go to your Microsoft admin or reseller.
Part 1 · One-time admin setup
These ten steps create the agent in Copilot Studio, connect it to NIC MAP, and deploy it to your users in Microsoft 365 Copilot and Teams. When they're done, your users will find NIC MAP under Agents.
Step 1: Create the agent
Go to Copilot Studio › Create › New agent.
Name the agent NIC MAP (select the pencil to the right of the name).
Under Knowledge, select the X on Search all websites to remove it, so answers come from NIC MAP data only.
Under Instructions, replace the sample text with:
Use the NIC MAP tool for any senior housing market data. Never estimate or invent figures.Select Save (the disk icon in the toolbar at the top right).
Save before moving on: Unsaved changes can be lost when you set up the connection in Step 3.
Step 2: Set the icon and color
Hover over the agent icon and select it (Edit agent icon).
In Change agent icon, select the Upload tab, then drag in or click to upload nicmap-icon.png. The file must be a PNG under 100 KB.
Select Set accent color, enter
072028in Hex, and select Apply. Then select Apply again to close the dialog.
Step 3: Connect NIC MAP
Select + next to Tools.
In Add a tool, select + Add › Model Context Protocol (MCP).
In Add MCP server, fill in the fields exactly as shown below, then select Add.
Field | Value |
Server name |
|
Server description |
|
Server URL |
|
Authentication | OAuth 2.0 |
Configuration type | Dynamic (with discovery) |
In Select a connection, open the Connection drop-down and select Create new connection.
Select Create. The display name is optional.
Sign in to NIC MAP if asked, then select Allow on the Authorize access screen.
When the connection shows a green check, select Add.
About the consent screen: It says Credential Manager is requesting access. That's Microsoft's sign-in service for Copilot connections, and it's expected.
Step 4: Confirm the tool uses each user's own login
After you select Add, the Edit tool window opens. (To reopen it later, select NIC MAP under Tools.)
Confirm Authentication is set to End user account.
Confirm about 22 tools are listed under Tool permissions with Allow all on. Fewer tools means your NIC MAP subscription doesn't include those modules, which is expected.
Select Done.
Authentication must be End user account. Otherwise, every user's requests run under your NIC MAP account.
Optional: To make the agent read-only, turn off Nicmap create analysis. It's the only tool that creates new analyses and uses NIC MAP quota.
Step 5: Test
Select Preview (top center) and ask: What's my NIC MAP quota?
You should see Used tool: nicmap_get_quota and your quota details.
Raw data in Preview: You may see a fragment of raw data at the end of answers in Preview. Users won't see it.
Step 6: Publish to Teams and Microsoft 365 Copilot
Select Publish (top right).
Confirm Teams + Microsoft 365 is selected and Make agent available in Microsoft 365 Copilot is checked.
Don't set up any other channels (Demo website, Web app, MCP client, A2A client).
Select Save and publish.
Editing later? If you edit the agent later, publish again, or users will keep the old version.
Step 7: Share and submit to your org catalog
Share
Select the Share icon in the toolbar at the top of the page.
Set Everyone in your organization to End user access. This is required for the org catalog. You'll choose who actually receives the agent in Step 8.
Select Share.
Sharing is not data access: Allowing everyone to use the agent doesn't give them NIC MAP data. Each user still has to sign in with their own NIC MAP account.
Submit to your org catalog
Select the arrow next to Publish (top right) › Teams + Microsoft 365.
Scroll down to Show in the store and select Submit to org catalog.
Select Yes, submit. The status changes to Waiting for approval. Continue to Step 8 to approve it.
Step 8: Approve and deploy
Go to Microsoft 365 admin center › Agents › All agents › Requests tab. NIC MAP shows as Pending review.
Select the ⋮ menu next to NIC MAP › Publish to store.
Under Select users or groups who can install the agent, choose Specific users/groups and add the users or group who should have NIC MAP.
Under Select users or groups who will have the agent pre-installed, choose Specific users/groups and add the same users or group. This installs NIC MAP for them in both Copilot and Teams, so they don't have to add it themselves.
Select Next.
On Policy template, keep Default policy template for agents, leave the Custom options unchecked, and select Next. (If your organization has built its own agent policies in Microsoft Entra, you can apply them here.)
On Review permissions, NIC MAP shows No required permissions. Select Next.
On Review and finish, confirm the users or group, then select Publish.
Select Done.
Use a group where you can: With a group, new members get NIC MAP automatically. People added to the group later can take up to 24 hours to receive it. For same-day access, add the user directly.
Step 9: Pin it for users
Step 8 installs NIC MAP for your users. Pinning puts it where they'll see it right away, in both Microsoft 365 Copilot and Teams.
Microsoft 365 Copilot
Go to Microsoft 365 admin center › Agents › All agents, select NIC MAP, select the pin icon at the top right of the details pane, add your users or group, and select Save.
If NIC MAP is listed twice, select the one with Publisher type Your org.
The pin icon is only available after the agent is deployed in Step 8.
Admins can pin up to 3 agents per user.
Teams
Go to Teams admin center › Teams apps › Setup policies, create a policy, select Add apps, and add NIC MAP under Pinned apps. Then assign the policy to your users or group.
Users get only one setup policy: Copy any apps pinned in your Global policy into the new one, or those users will lose them.
Step 10: Cap Copilot credit spending (recommended)
Every NIC MAP question uses Copilot Studio credits, so set a monthly limit before rolling out widely.
Set a limit: Go to Power Platform admin center › Licensing › Copilot Studio › Summary › Manage Agents › NIC MAP and set a monthly limit.
See usage by user or agent: On the same page, go to Summary › Top 5 agents and users, or select Download report.
How long until users see it
Action | Allow up to |
Copilot pin | 6 hours |
Teams setup policy | 24 hours |
User added to a group later | 24 hours |
Users can sign out of Teams and back in to see it sooner.
That's it for admin setup. The NIC MAP agent is now deployed. The first time each user opens NIC MAP, they'll connect their own NIC MAP account. Send them Part 2 of this guide before rollout.
Part 2 · Per-user activation
Each user runs through these eight steps once. After that, the NIC MAP agent is live in every chat: in Microsoft 365 Copilot on the web, in the desktop app, and in Teams.
Step 1: Open the NIC MAP agent and ask it anything
Open Microsoft 365 Copilot (or Teams) and select NIC MAP under Agents in the left sidebar. Type any question. "What is my daily quota?" is a good first one. Because your account isn't connected yet, Copilot replies with a Connection Required card. Click Set up connection.
A browser tab opens: Set up connection opens a page called Manage your connections in a new browser tab. It can take up to 30 seconds to load, which is normal. If you see an orange Connection bindings unavailable banner at the top, you can ignore it. It's a Microsoft display notice and doesn't affect the connection.
Step 2: Click Connect next to NIC MAP
On the Manage your connections page, NIC MAP is listed with the status Not connected. Click Connect in the Actions column.
Step 3: Create a new connection
In the Create or pick connections dialog, open the Connection drop-down (it reads Not connected) and click Create new connection.
Step 4: Name it "NIC MAP" and click Create
A NIC MAP connection window opens. The display name is optional, but we suggest NIC MAP so it's easy to recognize later. Click Create.
Step 5: Sign in with your NIC MAP credentials
A NIC MAP Login pop-up appears. Enter the email you use for nicmap.com, click Continue, enter your password, and complete two-factor authentication. This is a standard OAuth flow, so Microsoft never sees or stores your NIC MAP password.
Pop-up blocked? If nothing appears after you click Create, check your browser's address bar for a blocked pop-up notice, allow pop-ups from copilotstudio.microsoft.com, and click Create again.
Step 6: Click Allow on the Authorize access screen
NIC MAP asks you to confirm the access being granted. Credential Manager is Microsoft's sign-in service for Copilot connections, so seeing it here is expected. Click Allow.
Step 7: Click Submit. Your account is connected
The pop-up closes and you're back in Create or pick connections, where NIC MAP now shows a green check. Click Submit. The connections list updates to Connected.
Step 8: Back in Copilot, click Retry. You're live!
Switch back to Copilot and click Retry on the Connection Required card (or just ask your question again). Copilot calls NIC MAP and answers. You won't be asked to connect again on the web, in the desktop app, or in Teams.
Try one of these prompts:
"Produce an analysis of the senior-housing market opportunity around 2105 Blue Oak Terrace."
"Pull the construction pipeline for the Atlanta CBSA and summarize inventory growth risk."
"What is my NIC MAP daily quota?"
Troubleshooting & support
A few quick checks that resolve almost every issue we've seen so far.
For administrators
Issue | What to do |
Fewer than ~22 tools | Your NIC MAP subscription doesn't include those modules. This is expected. |
403 or "authorization" error | Your NIC MAP organization doesn't have MCP access turned on. Contact your NIC MAP account team. |
Agent stops responding or shows a capacity error | Copilot Studio credits ran out or hit the Step 10 limit. Check the Power Platform admin center. |
"Connection bindings unavailable" | This is a Microsoft display issue. Select Retry; the connection still works. |
User doesn't see NIC MAP yet | See How long until users see it above. A user added to a group can take up to 24 hours. Signing out of Teams and back in helps. |
For end users
Issue | What to do |
I don't see NIC MAP under Agents | Your administrator hasn't finished deploying the agent, or you were added recently. It can take up to 24 hours. Try signing out of Teams and back in. |
Login says "invalid credentials" | Use the same email and password you use for nicmap.com. If you've never set a password, use Forgot password on the NIC MAP login screen or email [email protected]. |
Still shows Connection Required | Make sure you clicked Submit in Part 2, Step 7 and the status reads Connected. Then click Retry or start a new chat. |
"NIC MAP quota exceeded" | NIC MAP applies a daily limit on creating new analyses. Reading existing analyses doesn't count. The quota resets daily. Contact your NIC MAP account team if you need more. |
Tables show as raw | characters | Teams has limited table support. Ask the same question in Microsoft 365 Copilot for table-heavy answers. |
Still stuck? Contact the client success team at [email protected].

