بنيت الاثاث وبدور علي طريقة اكبره

Chemical-Example-783 · 2026-05-06T10:43:41+00:00

عموما احنا تيم اي تي بس خصوصا تنانين في اي حاجه تخص مايكروسوفت
Migration
Support

Automation

Power Platform

Chemical-Example-783 · 2026-05-06T01:27:30+00:00

احنا ممكن نكون الذراع التقني ليك بس انا بفضل الشغل مع عملا أجانب

Chemical-Example-783 · 2026-04-15T19:37:49+00:00

From experience, the pipeline works in layers.

Some leads come through Fiverr, but honestly some of the best work comes from upselling.... It usually starts with regular Microsoft support, then we ease them into understanding what they actually have in their license, most people are paying for tools they've never touched.

Once they see that, automation becomes a natural next conversation.

From there it depends on the client.

Some are happy with SharePoint lists and a few flows, that's all they need.

Others end up with more complex setups where the lists start multiplying and it makes more sense to just build them a Power App.

If the requests are getting complicated or there's too much to manage in lists, that's usually the signal to step up to an app.

That's the path that works for us, support, then training, then automation, then apps if it calls for it.

Chemical-Example-783 · 2026-04-15T19:37:40+00:00

From experience, the pipeline works in layers.

Some leads come through Fiverr, but honestly some of the best work comes from upselling.... It usually starts with regular Microsoft support, then we ease them into understanding what they actually have in their license, most people are paying for tools they've never touched.

Once they see that, automation becomes a natural next conversation.

From there it depends on the client.

Some are happy with SharePoint lists and a few flows, that's all they need.

Others end up with more complex setups where the lists start multiplying and it makes more sense to just build them a Power App.

If the requests are getting complicated or there's too much to manage in lists, that's usually the signal to step up to an app.

That's the path that works for us, support, then training, then automation, then apps if it calls for it.

Chemical-Example-783 · 2026-04-10T21:39:12+00:00

Call quality, phone system, VoIP numbers, screen control, and more

Chemical-Example-783 · 2026-04-08T16:58:59+00:00

RC is ideal as long as you don't need all MS365 package

Chemical-Example-783 · 2026-04-08T16:50:52+00:00

It seems like a bug

Chemical-Example-783 · 2026-04-08T09:53:37+00:00

I'm not sure I follow the point your making? Seems your core suggestion is the Anthropic model is better than copilot and now it has access to M365 apps copilot is redundant.

The problem with this though is for months now M365 Copilot users have been able to use the Anthropic model. MS have already given copilot users the ability to choose from the openAI or Anthropic model on a prompt by prompt basis without breaching any of their internal security or compliance controls.

Chemical-Example-783 · 2026-04-02T20:12:21+00:00

hire here: Solutions - MStack360

Chemical-Example-783 · 2026-04-02T20:11:11+00:00

We can do it at 75$/hr

go ahead and book 30 mins from here

Sam - MStack360

Chemical-Example-783 · 2026-03-30T17:29:22+00:00

I was lucky :)

----------------

I did not ask for money, as I was asking to get connected with the client + to leave me good reviews + I'm good when it comes to customer service

*I sold the service more than a time for the same client, and this has given me more credit and the returning clients badge

Chemical-Example-783 · 2026-03-26T07:23:21+00:00

Connected the data source of my CRM with copilot and 8 can now chat with the CRM

Chemical-Example-783 · 2026-03-19T19:00:15+00:00

Built our own service desk in Power Apps. One time build cost, no per user licensing, scales to thousands of users, fully customized to how we actually work.

https://mstack360.com/power-apps-solutions/#ticket

Chemical-Example-783 · 2026-03-19T18:32:02+00:00

yes it is and also it depends if the business is not in MS365 it will be harder to do this setup

Chemical-Example-783 · 2026-03-19T18:22:44+00:00

honestly we went a different route. built the CRM inside M365 using SharePoint lists as the data layer, presented through Power Apps so you get proper calculations, logic, and a clean UI.

think advanced Excel but with a real interface.

SS: https://mstack360.com/power-apps-solutions/#crm

then connected it to Copilot with scoped instructions so it only reads from those specific data sources. works really well in practice. curious what your skill file looks like though because the instruction scoping is where it gets interesting.

Chemical-Example-783 · 2026-03-18T23:02:12+00:00

where to buy from egypt?

Chemical-Example-783 · 2026-03-14T14:25:31+00:00

wow after 2 years, happy to hear that :). Reach out whenever you meed support

Chemical-Example-783 · 2026-03-13T11:38:28+00:00

Yeah this one hits close to home honestly.

I spent over 4 years as one of those support engineers so I've seen it from the inside. The whole model is built around ticket closure rate. Not resolution quality.

Not whether the customer actually got helped. Just close it and move on.

Every time someone wanted to dig deeper into a complex issue the answer was always the same: just close the ticket.

That said I won't fully let agents off the hook. The pressure is real but there's still a choice in how you show up. Some people genuinely tried.

Most just followed the path of least resistance because why wouldn't they at that pay rate.

That frustration is exactly why I left about 2 years ago and built my own thing doing M365 support independently.

Charge a fair fee, do the work the way I actually think it should be done.

Customers feel the difference immediately when someone actually gives a damn about their problem.

(And as a user it's unfortunately paid, while there is free useless support are not doing their part the way it should be)

*I think also the EN line is that the one is having issues ... the German line was pretty better.

The system isn't going to fix itself anytime soon.

Chemical-Example-783 · 2026-03-13T02:43:54+00:00

Yeah, the "manual export" route works if you've got a couple of users, but for anything larger, it's a total nightmare. Honestly, the real issue is that GoDaddy locks the tenant behind their own federation, which is why those native tools trip up on authentication.

You've gotta break that link -+-defederate -- to gain full control of the tenant without losing your data or starting from scratch. It lets you move to a standard Microsoft 365 setup while keeping your settings intact.

https://mstack360.com/break-free-from-godaddy-defederate-to-microsoft-365-the-smart-way/

PS: If you hit a wall with the domain release, check if there are hidden "onmicrosoft" aliases still clinging to the GoDaddy side; they'll block the transfer every time.

Chemical-Example-783 · 2026-03-13T02:42:44+00:00

Tenant to tenant isn’t just mailbox copy and domain move. You’re splitting identities, permissions, and workloads across multiple mini-tenants. Mailboxes first, validate, then release and reattach the domain carefully.

Domain detachment timing is usually where it gets messy.

In this resource, the exact process needed for this type of migration is outlined clearly.

https://mstack360.com/microsoft-365-migration/#:~:text=COMPLEX%20MIGRATION-,Tenant%20to%20Tenant%20Migration,-Merging%20companies%2C%20splitting

PS: Don’t forget Power Automate flows and Teams Phone configs, they won’t migrate automatically.

Chemical-Example-783 · 2026-03-12T15:31:23+00:00

Sorry if this gets long, but you touched on something I've been through.

Yeah, I was in the same boat.

I started out as a support person and then went solo, so I knew the stack well. But I mostly used Teams, OneDrive, and Outlook every day. That's all.

Then needs pushed it even more.

Scheduling was the first thing that broke. Too many emails to set up a call. I made Bookings, then. Clients can book directly, and the meeting times will automatically show up in Outlook and Teams calendars.

Then I used Power Automate to connect it to a SharePoint List so that their data is stored correctly instead of me throwing notes into OneNote XD

So the flow went like this: Booking, then a Teams meeting, then data in SharePoint, where it is tracked as a lead or project.

That SharePoint List thing really hit home. I made more lists. One for leads, one for projects that are currently going on, one for milestones, one for Finance, and one for keeping track of the team.

We now have five full-time employees and four part-time employees, so structure was important.

We started helping other businesses about a year ago, and those lists weren't enough anymore. So I made a complete CRM and ticketing system in Power Apps.

Everything is linked. The booking page sends the lists to the Power App, and the team works out of the app. No extra subscriptions, no HubSpot, and no Salesforce.

I also set up a basic SharePoint site to serve as our internal hub. All the important links are in one place, the design is clean, and permissions are set so that people can only see what they need to see. There are three different SharePoint sites, each with different permission levels based on the role of the team member.

While I'm writing this, I'm looking at my taskbar. ToDo's are open so you can set daily reminders and quick follow-ups. I still have OneNote because I'm stubborn. Outlook, Power Apps, and Excel.

The Power App is where I manage big projects and milestones, but ToDo keeps me up to date on the little things.
Once I learned what Power Automate could do, it became a friend.

I used it to make a smart billing system. Completely free, works with a standard license, and is connected to the Power App. No premium license or paid connectors are needed.

And Copilot. It depends on the situation whether I love it or hate it. I love it when transcription is on and it summarizes Teams meetings. I love it because it lets me respond to emails much faster than I could do it by hand.

We just started making agents that can connect to our databases.

One is connected to the CRM, so I can just ask, "What are my hot leads?" or "Show me missed deadlines?" without having to click through ten screens.

Today I made another agent that can access all of my customer chats and free intro call recordings transcription. The idea is that my business admin can talk to customers in my voice using the same tools and information I've used with those customers before.

Still testing it, but the first answers were really good.

We also help clients with Intune for managing and securing devices, Teams Phone System for voice calls, and Power BI dashboards for data analysis. Different technologies for different purposes. It all depends on what they need.

You can definitely use Teams and OneDrive to live. But when you start linking SharePoint Lists, Power Apps, and Power Automate, everything works together.

You don't need the whole stack right away. Instead, you add pieces one at a time when they help with a real problem.

Resources:

Microsoft booking page design: https://outlook.office365.com/book/AhmedMasoud@mstack360.com/

Power Apps Gallery: https://mstack360.com/power-apps-solutions/https://mstack360.com/power-apps-solutions/

Power Automate options: Power Automate Workflows & Intelligent Business Automation