Video Watch

Summary

• OAuth 2.0 is viewed as complex and problematic. The transition to OAuth 2.0 is necessary for Microsoft services as legacy authentication methods are being deprecated, raising concerns about its complexity.
• Microsoft is moving away from legacy authentication methods. This shift includes the requirement of app passwords for automation, particularly with shared mailboxes, which complicates integration.
• WebAssembly is being adopted for enhanced performance. The adoption of WebAssembly is aimed at modernizing the IDE and improving application performance.
• AI capabilities in the IDE can automate tasks. AI can facilitate form conversion to HTML and provide quick access to drug contraindications without incurring API fees.
• GDPR compliance is prompting the use of internal LLMs. Clients are concerned about GDPR compliance when using AI, leading to the development of internal LLMs to protect proprietary information.
• The new system for drivers is cost-effective and efficient. The structured form for drivers to report gas tank status includes offline functionality and automatic geolocation, with a planned go-live in January.
• Switching to managed services is preferred for cost efficiency. The decision to move from on-premises SQL Server to managed services aims to reduce costs and maintenance responsibilities.
• Version control and GitHub usage are under discussion. There is interest in scheduling a session on version control, with inquiries about integrating Wasabi or AWS for file retrieval.

Event Date: 11/21/2025

Title: Professional Developer Forum

Topic Outline:

1. OAuth 2.0 complexities
2. Transition from legacy authentication
3. WebAssembly adoption
4. AI capabilities in IDE
5. GDPR compliance and internal LLMs
6. New system for drivers
7. Switch to managed services
8. Version control discussion

Keywords: OAuth 2.0, Microsoft, Google, SparkPost, WebAssembly, AI