u/heartgoldt20

I’m building a Copilot Studio agent that needs to answer questions using a local/on-premises SQL database containing more than 80,000 records.
In my current setup, I can only retrieve 2,048 records in one go. The concern is that the agent answers based on that subset, even when the relevant records could be elsewhere in the database.
Users should be able to ask questions in natural language, and the agent needs to filter across the full dataset to return an accurate answer. For example:
What is the oldest record for a particular machine?
Which records mention a specific fault or maintenance activity?
How many matching records are there within a given date range?
I don’t necessarily need to send all 80,000+ rows to the agent. I need the filtering, sorting, and counting to consider the entire database before returning the relevant results.
What’s the recommended approach for this in Copilot Studio?

Nou laat jullie voorspellingen maar eens horen. Hoe zal de wedstrijde verlopen, wie zal er als eerst scoren en het eind resultaat.

Today I handled my first confirmed account-compromise incident involving an adversary-in-the-middle (AiTM) phishing attack.

Normally, our Conditional Access policies restrict access based on approved locations. We have seen risky sign-ins from other countries before, but those attempts were blocked because they originated from locations that were not allowed and then changed the user's password. (they could not lgoni despite ahving credentials because of conditional access)

This time, however, the attacker connected from a country that was permitted by our Conditional Access policy. The attacker also had the user’s credentials and triggered an MFA request. Even though the user was not trying to sign in, they approved the notification anyway.

As a result, the attacker successfully authenticated and gained access to the account. Because this involved an AiTM phishing flow, we also had to assume that the authenticated session or token could have been captured.

I was quick to notice 10 minutes at most before handlign the situation, disablign accounts, revoking sessions, removing any MFA devices, check send e-mails and inbox rules, oauth applications or requests.

It did get my heart beating for a minute.

Let’s hear everyone’s plan, since so many people keep saying we need more players but when asked what, where and who most people fall quiet so for anyone feel free to share your thoughts and ideas.

So part of my job is running phishing simulations to test how our staff respond. Normally I keep it pretty tame fake shipping notifications, "your password expires today," that kind of thing. This time I decided to go for realism (Template from the campaign solution we use that was edited a bit). I spoofed our CEO's email using a classic homoglyph trick swapped the "m" for "rn" and the "i" for "l" in the domain, so at a glance it looked completely legit unless you were really staring at it. Subject line: something about an upcoming reorganization.

The trick was in the header and CEO behaviour. I sent it to every high-risk profile in the org, but the message body/header made it clear it was only meant for management as in, "this is confidential, intended for leadership only." Turns out that's basically catnip. People who technically weren't supposed to see it were the most curious to open it and see what they "weren't supposed to know." Classic forbidden-fruit effect, and it worked way better than I expected. Besides also the CEO never e-mailing these people directly which is already alien behaviour.

The email said the attached file had details on the restructuring, but to view it you'd need to log in with your credentials "for confidentiality reasons." Urgency + exclusivity + authority + a little FOMO, all in one shot.

the click-through and credential-entry rate was rough. Genuinely uncomfortable to look at in the report. A few people who definitely weren't management were the fastest to click, which tells you everything about the "not meant for you" trigger.

Multiple people got really angry at the phishing e-mail that was sent even tho I personally think if you really looked at it.

1. Our name convention was incorrect.

2. l instead of i and rn instead m

3. The ceo would never contact them through e-mail

I did get an earful from my supervisor about it. (Apparently in one of our branches there really is a reorganization going on. Which I knew nothing about.

So part of my job is running phishing simulations to test how our staff respond. Normally I keep it pretty tame fake shipping notifications, "your password expires today," that kind of thing. This time I decided to go for realism (Template from the campaign solution we use that was edited a bit). I spoofed our CEO's email using a classic homoglyph trick swapped the "m" for "rn" and the "i" for "l" in the domain, so at a glance it looked completely legit unless you were really staring at it. Subject line: something about an upcoming reorganization.

The trick was in the header and CEO behaviour. I sent it to every high-risk profile in the org, but the message body/header made it clear it was only meant for management as in, "this is confidential, intended for leadership only." Turns out that's basically catnip. People who technically weren't supposed to see it were the most curious to open it and see what they "weren't supposed to know." Classic forbidden-fruit effect, and it worked way better than I expected. Besides also the CEO never e-mailing these people directly which is already alien behaviour.

The email said the attached file had details on the restructuring, but to view it you'd need to log in with your credentials "for confidentiality reasons." Urgency + exclusivity + authority + a little FOMO, all in one shot.

the click-through and credential-entry rate was rough. Genuinely uncomfortable to look at in the report. A few people who definitely weren't management were the fastest to click, which tells you everything about the "not meant for you" trigger.

Multiple people got really angry at the phishing e-mail that was sent even tho I personally think if you really looked at it.

1. Our name convention was incorrect.

2. l instead of i and rn instead m

3. The ceo would never contact them through e-mail

I did get an earful from my supervisor about it. (Apparently in one of our branches there really is a reorganization going on. Which I knew nothing about.

Goodmorning,

We are trying to setup SSO within Netsuite and Entra idP.

But to our avail we are constantly getting this error:

Notice

Exception while processing SAML response: This service provider is not the intended audience.

Does anybody have the same problem and if so how did you resolve it?

We’ve got the usual stack in place (Defender for O365, SPF/DKIM/DMARC, Purview labels, user awareness training) but obviously nothing catches 100% of it. I’m thinking about building a Copilot/Power Automate agent that reviews flagged or borderline mail and scores it on classic phishing signals like urgency/pressure language, sender-domain mismatches, spoofed display names, weird links, etc.

Not trying to replace the SEG, more like a second-opinion layer for the stuff that already got through or landed in a gray zone. Curious if anyone’s actually done this and whether it’s worth the effort vs. just tuning what we have.

(Sick of also telling people if you don’t expect an email I would not trust it)

Ik denk het toch stiekem wel dat we een aardig team al hebben zo. Misschien nog extra op het middenveld maar de rest is wel prima zo.

So this is something that’s been sitting on my chest and I need an outside perspective because I genuinely don’t know if I was wrong here.
Last night I went out around 11pm to be with my younger brother. He was facing a major life decision something that could genuinely change the trajectory of his life and even though he already had his agent and my dad with him, I felt like I needed to be there. That’s just the dynamic our family has. I wanted to be his voice, his mediator, someone in his corner who wasn’t just there professionally.
My wife didn’t want me to go. But I went anyway. Before I left, I handled everything put the baby to sleep, fed him, showered with him. He was out for the night. My wife was almost asleep herself. I figured it was fine.
I came home and she was angry. Said I chose my family over her.
Honestly? That annoyed me. I didn’t really see the problem. But she kept pushing it, and eventually I snapped. And here’s where I might be the asshole.
I said: “You chose your family over me too you went back to your home country while you were pregnant, and then called me saying you wanted an abortion.”

That’s something we’ve never really talked about properly. When she went back to visit her family during the pregnancy, I was on the other side of the planet. And she called me saying she was thinking about an abortion. I felt completely helpless. Scared. Alone. I couldn’t get to her. I couldn’t even be close to her. And that feeling has never really left me.
I want to be fair I know it was hard for her too. Going back, talking to her parents, processing everything she was processing. I don’t want to dismiss that.
But I was thousands of miles away, unable to do anything, receiving that call. And I never said anything about it. Until last night, when I was annoyed, and I just… let it out.

So, AITAH. Was I wrong to snap and bring that up?

Additional info:

It is just a one time thing her not wanting me to go. The reason was simply because she didn’t want me to go.

She didn’t run to her country but more forced we did talk beforehand about not having an abortion but I guess when she was alone her parents got to her she did not end up doing it. Which was the reason I did not want her to go.

Idk why I said it just came out maybe just something that lingered deep within me she doesn’t know nor I guess really cared about how I felt during that time. I didn’t mean to hurt her ofcourse and apologized after.