For those who've also been invited to participate in the M365 Copilot Early Access Program and but rejected, I'd like to understand why? For those who accepted the invite, what have you discovered as best practices?

Applications & PlatformsEnterprise Applications
8.8k viewscircle icon2 Upvotescircle icon2 Comments
Sort by:
IT Manager in Finance (non-banking)a year ago

Got access to it only last week but I am hugely underwhelmed.

For one, it cannot even complete a Word memo for me, it keeps crashing and saying it couldn't finish. This is basic text generation.

Secondly, when it gives you "updates from [person]", it looks at all documents that person has touched that you by chance have access to as well, not necessarily documents you are involved in. This means there is a clutter of info, but also that it would require you to have full control and transparency around your Sharepoint access rights.....

And don't get me started on the bad Powerpoints it creates... 

The idea is there, this might become the thing. But right now it is vastly overpriced imho.

Lightbulb on1
CIOa year ago

Still M365 Copilot is at nascent stage.  Pricing is not clear. It is impossible to calculate TCO as of now.  No clear value add & ROI. 

Content you might like

As technology leaders, where are you seeing the most challenges or gaps?

Executive Support10%

Projects vs. Operations68%

Building a culture of Security15%

Team Completeness5%

View Results

Thinking about non-optimal technology solutions your organization uses today, what are their most common shortcomings?

Insufficient integrations34%

Valuable features are complex to use37%

Rigid and non-customizable/configurable48%

Support and service are hard to access / benefit from34%

Expensive compared to alternatives20%

Other (please comment)7%

View Results

We are dealing with a specific issue in our VDI non-persistent environment, which operates using Omnissa Horizon (formerly VMware). We are employing a hybrid join for authentication that integrates ADFS and Entra ID.   Here are the details of our problem:   1. **Environment**: VDI non-persistent using Omnissa Horizon 2. **Authentication Method**: Hybrid join with ADFS and Entra ID 3. **Issue**: Users are experiencing difficulties authenticating to Microsoft 365 apps within the virtual machine. The authentication process gets stuck in a loop when attempting to access the smartcard. I would appreciate any insights or experiences from others who have encountered similar issues or have a similar environment working successfully.

Has anyone implemented Zelle directly with EWS (Enterprise Web Services) instead of going through a reseller-hosted experience? What were the biggest architectural, compliance, and operational challenges you encountered, and how did you address them? Can you please share your views on below...

1. Integration Complexity (How did you handle real-time messaging and settlement flows with Zelle via EWS & what middleware or orchestration layers were required?)

2. Compliance & Risk: What additional regulatory or fraud controls did you need to implement without the buffer of a reseller? How did you manage OFAC screening, KYC, and transaction monitoring?

3. Customer Experience: Were there any trade-offs in terms of UI/UX or mobile app integration? How did you handle customer support and dispute resolution? 
4. Operational Overhead: What internal capabilities did you need to build or scale (e.g., 24/7 support, reconciliation, exception handling)? How did you manage updates and changes to the Zelle network?  
5. Cost-Benefit Analysis: Was the direct integration more cost-effective in the long run? How did you measure ROI compared to a hosted solution?

6. Vendor & Network Relationships: What was your experience working directly with Early Warning Services (EWS)? Were there onboarding or certification hurdles?

What do you think are the top 3 enterprise-level social media management tools that can compete with Sprinklr?