InfoPath Retirement: What IT Professionals Need to Know

Microsoft InfoPath, a forms tool that has been in use for over two decades, is officially retiring. With InfoPath Forms Services scheduled to be removed from Microsoft 365 in July 2026, organizations still relying on InfoPath forms need to understand the timeline and prepare for transition.

The Retirement Timeline

Here are the critical dates for InfoPath retirement:

Microsoft 365 (Cloud) Environments

• July 14, 2026: InfoPath Forms Services completely removed from SharePoint Online
• Applies to all Microsoft 365 tenants (Commercial, GCC, GCC High, DoD)
• No extensions or exceptions will be granted by Microsoft
• InfoPath Client 2013 reaches end of extended support on the same date

On-Premises Environments

InfoPath support varies by SharePoint Server version:

• SharePoint Server 2016: InfoPath Forms Services support ends July 14, 2026
• SharePoint Server 2019: InfoPath Forms Services support ends July 14, 2026
• SharePoint Server Subscription Edition: InfoPath Forms Services support ends July 14, 2026

Important note: Unlike some other Microsoft products, on-premises environments receive no extended support beyond this date for InfoPath.

Configuration Changes Already in Effect

Microsoft has already begun restricting InfoPath capabilities:

• Creating new custom InfoPath forms in SharePoint Online is being phased out
• Configuration options are being removed from the SharePoint Admin Center
• New tenants created after the retirement announcement have limited InfoPath functionality

What Happens on July 15, 2026?

Understanding the immediate impact is critical for planning:

For End Users:

• Will be completely unable to submit new form responses using InfoPath service
• Cannot fill out InfoPath forms through web browsers
• Existing form data remains in SharePoint lists but forms become non-functional
• Can download InfoPath templates (.xsn) or form data (.xml) to view with InfoPath Client 2013 (if they have file permissions)

For Designers/Publishers:

• Completely disallowed from creating, modifying, or publishing InfoPath templates
• Cannot make any changes to existing InfoPath forms
• All form design capabilities removed from SharePoint Online

For Business Processes:

• Critical workflows dependent on InfoPath forms will immediately break
• Data collection processes (surveys, requests, intake forms) will halt
• Approval processes using InfoPath will stop functioning
• Integration with other systems relying on InfoPath data will fail

What Remains:

• Historical form data stored in SharePoint lists persists
• Form templates (.xsn files) can be downloaded for archival purposes
• Raw XML data from submitted forms remains accessible

Why There's No Extension Coming

Microsoft has explicitly stated there will not be an option to extend InfoPath Forms Services in SharePoint Online beyond July 14, 2026. The reasons are clear:

• InfoPath was last updated in 2013—over a decade ago with no new features
• The technology doesn't support modern requirements for mobile, cross-platform, or cloud-native experiences
• Microsoft has invested heavily in Power Apps as the official successor
• Maintaining legacy infrastructure creates security and compliance risks
• Industry feedback indicates businesses need integrated forms experiences that InfoPath cannot provide

The Migration Challenge

Unlike some Microsoft migrations, there is no automated migration tool for InfoPath to Power Apps. Every InfoPath form must be:

1. Analyzed for functionality, data connections, and business logic
2. Manually rebuilt in the new platform (typically Power Apps)
3. Tested thoroughly before deployment
4. Validated with end users and business owners

This reality makes early planning essential. Organizations with dozens or hundreds of InfoPath forms face months of migration work.

Immediate Actions for IT Teams

If your organization still uses InfoPath forms, take these steps immediately:

This week:

1. Run the Microsoft 365 Assessment Tool to scan your tenant for all InfoPath usage
2. Generate the Power BI InfoPath Report to identify:
• All InfoPath forms across site collections and sites
• Recency and volume of form usage
• Lists, libraries, and content types using InfoPath
3. Identify business owners for each form
4. Categorize forms by business criticality

This month:

1. Prioritize forms for migration based on business impact
2. Assess which forms can be retired instead of migrated
3. Evaluate Power Apps licensing requirements for your organization
4. Determine if you need external consulting assistance
5. Create a detailed migration timeline working backward from July 2026

Within 90 days:

1. Begin rebuilding your highest-priority forms in Power Apps
2. Establish design patterns and governance for new Power Apps forms
3. Pilot migrated forms with small user groups
4. Document standard approaches for common form patterns
5. Train power users and form designers on Power Apps

Microsoft's Recommended Alternatives

Microsoft suggests migrating to their modern Power Platform tools based on your specific scenarios:

Microsoft Forms:

• Best for: Simple surveys, polls, quizzes, and basic data collection
• Key capabilities: Quick deployment, built-in analytics, automatic Excel integration
• Limitations: Limited customization, basic data connections, no complex business logic

Power Apps:

• Best for: Complex forms with business logic, data connections, and integration requirements
• Key capabilities: Full customization, connects to 1,000+ data sources, advanced validation, offline capability
• Microsoft's official recommendation: Primary successor to InfoPath
• Consideration: Requires learning curve and potentially Premium licensing for advanced features

Power Automate (complementary):

• Use case: Automate workflows triggered by form submissions
• Integration: Works seamlessly with both Forms and Power Apps
• Replaces: SharePoint Designer workflows often paired with InfoPath

Common migration patterns:

• Simple data collection: InfoPath → Microsoft Forms
• Complex business forms: InfoPath → Power Apps
• Forms + workflows: InfoPath + SharePoint Designer → Power Apps + Power Automate
• Multi-source data: InfoPath with data connections → Power Apps with connectors

Common InfoPath Form Scenarios and Solutions

To help plan your migration, here are typical InfoPath use cases and their modern equivalents:

Scenario 1: Employee Onboarding Forms

• Legacy: InfoPath form collecting employee information
• Modern: Power Apps form with data connections to HR systems, automated workflows via Power Automate

Scenario 2: IT Service Request Forms

• Legacy: InfoPath form for help desk requests
• Modern: Power Apps integrated with Microsoft Teams, automated ticket creation in service management system

Scenario 3: Approval Workflows (PO approvals, time-off requests)

• Legacy: InfoPath form + SharePoint Designer workflow
• Modern: Power Apps form + Power Automate approval flows with email/Teams notifications

Scenario 4: Survey or Feedback Collection

• Legacy: InfoPath form for simple surveys
• Modern: Microsoft Forms (for basic needs) or Power Apps (for complex scenarios)

Scenario 5: Multi-Source Data Integration

• Legacy: InfoPath with data connections to SQL, SharePoint lists, web services
• Modern: Power Apps with connectors to databases, SharePoint, APIs, and 1,000+ other sources

The Reality of InfoPath Migration

Based on lessons learned from other Microsoft retirements, organizations should expect:

Timeline considerations:

• Discovery phase often reveals more forms than initially known
• Each complex form can take days or weeks to rebuild and test
• User acceptance testing and training add significant time
• Organizations with 50+ forms should plan 6-12 months for complete migration

Resource requirements:

• Internal IT staff need training on Power Apps development
• Business users need training on using and managing new forms
• Consider Microsoft partners for large-scale migrations
• Budget for Power Apps Premium licensing if advanced features are needed

Common pitfalls:

• Underestimating the number of forms in use
• Attempting last-minute migrations in late 2025/early 2026
• Not involving business owners early in the process
• Treating migration as purely technical rather than business transformation
• Ignoring the opportunity to modernize and improve forms during migration

Why You Can't Wait

The July 2026 deadline may seem distant, but successful InfoPath migrations are complex and time-intensive:

Risk of delay:

• High demand for migration resources as deadline approaches (expect consultant scarcity in 2025-2026)
• Rushed migrations lead to errors and business disruptions
• Missing the deadline means immediate business process failures
• Forms stop working mid-process with no warning or grace period

Opportunity of early action:

• Time to modernize processes, not just replicate old forms
• Ability to consolidate redundant forms
• Properly train users on new tools
• Avoid emergency mode and last-minute workarounds
• Negotiate better rates with consultants before market demand peaks

The Bottom Line

July 14, 2026 is a firm deadline with no extensions. InfoPath forms will completely stop functioning in Microsoft 365 on July 15, 2026. Organizations waiting until 2025 to begin planning face serious risks of business disruption.

The transition from InfoPath to Power Apps isn't just about maintaining existing functionality—it's an opportunity to modernize your forms, improve user experience, and build on a platform that Microsoft is actively developing and supporting.

Start your InfoPath assessment and migration planning now. The organizations that begin early will have time to do it right, while those who wait will face costly emergency migrations.

Resources:

• InfoPath Forms Services Retirement Announcement

SharePoint 2013 Workflow Retirement: What IT Professionals Need to Know

Microsoft is retiring SharePoint 2013 workflows, and the timeline is firm with no extensions available. If your organization still relies on these workflows, it's time to understand the critical dates and plan your next steps.

The Retirement Timeline

Here are the key dates that matter for your planning:

Microsoft 365 (Cloud) Environments

• April 2, 2024: SharePoint 2013 workflows disabled for all newly created Microsoft 365 tenants
• April 2, 2026: Complete retirement—SharePoint 2013 workflows removed from all existing tenants
• Applies to all Microsoft 365 environments including Commercial, GCC, GCC High, and DoD
• No extensions or exceptions will be granted
• All workflows stop functioning immediately after this date

On-Premises Environments

SharePoint 2013 workflow support varies by version:

• SharePoint Server 2016: Support continues until July 14, 2026 (end of extended support)
• SharePoint Server 2019: Support continues until July 14, 2026 (end of extended support)
• SharePoint Server Subscription Edition: Support continues beyond July 2026

Third-Party Workflow Solutions

• Nintex Workflow for Office 365: Support ends December 31, 2025
• This is several months before Microsoft's deadline
• Organizations using Nintex need to act even sooner
• Consider Nintex Automation Cloud as a migration path

What Happens on April 3, 2026?

Understanding the immediate impact helps prioritize your migration efforts:

Workflows will:

• Stop executing completely across your entire tenant
• Fail to trigger on any new items or changes
• Leave in-progress approvals and processes incomplete
• Become inaccessible through the SharePoint interface

What remains:

• Workflow definitions saved as raw XML files (not executable)
• Historical workflow data retained in lists (if previously configured)
• SharePoint lists and libraries remain unaffected

What you lose:

• All automation based on SharePoint 2013 workflows
• Ability to run or modify existing workflows
• Access to workflow history unless previously archived

Why No Extension Is Coming

Microsoft has been clear about this timeline for strategic reasons:

• SharePoint 2013 workflows rely on legacy infrastructure incompatible with modern cloud architecture
• The technology has been superseded by Power Automate, which offers significantly more capabilities
• Maintaining dual automation platforms creates security and compliance risks
• The workflow engine technology is over a decade old and cannot support modern integration requirements

Immediate Actions for IT Teams

If you're still running SharePoint 2013 workflows, take these steps now:

This week:

1. Run the Microsoft 365 Assessment Tool to inventory all SharePoint 2013 workflows in your tenant
2. Identify business owners for each workflow
3. Document which workflows are mission-critical

This month:

1. Assess the complexity of your workflows and determine migration approach
2. Review Power Automate licensing requirements
3. Create a prioritized migration timeline working backward from April 2026
4. Consider whether workflows should be migrated to Power Automate or retired entirely

Within 90 days:

1. Begin migrating or rebuilding your highest-priority workflows
2. Test migrated workflows thoroughly in a non-production environment
3. Train workflow owners on Power Automate if pursuing manual rebuilds
4. Engage Microsoft partners or consultants if needed for complex migrations

The Bottom Line

April 2, 2026 is a hard deadline. There will be no last-minute extensions, and workflows will simply stop working. Organizations that wait until late 2025 to begin migration efforts risk business disruptions, incomplete migrations, and emergency workarounds.

The good news is that you have time to plan and execute a thoughtful migration—but only if you start now. Use this retirement as an opportunity to modernize your automation capabilities while ensuring business continuity.

Refrences:

• SharePoint 2013 Workflow Retirement Announcement

Fixing the “Refinement Filters Limit (100)” Issue in SharePoint Search Using JavaScript

Issue:

Receently we were working PNP search webparts. When working with SharePoint Search refiners, you may eventually run into a frustrating limitation: by default, SharePoint only returns up to 100 refinement values (also known as refinement tokens or bins).

This becomes a problem when your refiners (e.g., tags, categories, metadata) exceed 100 values — because your script will simply never receive anything beyond the default limit. In this blog, we’ll break down why this happens, and more importantly, how to force SharePoint Search to return more than 100 refinement values using JavaScript and REST API.

Analysis:

SharePoint’s search engine applies an internal limit of 100 refinement results.

So even if your managed property (e.g., RefinableString01) contains 500 unique values, SharePoint will only send the first 100 — unless you explicitly override that limit. 

This behavior is by design to protect performance, but when developers need the complete refinement list (for filters, dropdowns, analytics, etc.), the default limit becomes restrictive.

Solution:

When calling the SharePoint REST Search API:

 /_api/search/query  

You must modify the refiners parameter by appending:

 (filter=1000/0/*)  

What these parameters mean

1. filter=1000 - Maximum number of refinement values to retrieve (use high numbers like 1000)
2. 0 - Threshold (0 = no threshold)
3. * - Sorting order (default)

This bypasses the default 100 results limit and allows SharePoint to return the full set of refinement bins — up to the platform’s internal max.

Below is code sample: 

 const refinerName = "RefinableString01";  
 // Syntax: ManagedProperty(filter=count/threshold/sort)  
 // 1000 = max refinement bins  
 const url = `/_api/search/query?querytext='*'&refiners='${refinerName}(filter=1000/0/*)'`;  
 fetch(url, {  
   headers: { "Accept": "application/json;odata=verbose" }  
 })  
 .then(response => response.json())  
 .then(data => {  
   // All refinement bins are available here  
   console.log(data.d.query.PrimaryQueryResult.RefinementResults);  
 });  

Reference:

1. GitHub – PnP Modern Search Issue #679

SharePoint Alerts Are Going Away: What You Need to Know About Microsoft's Retirement Timeline

Microsoft has announced the retirement of SharePoint Alerts, a feature that has been helping users stay informed about changes to their SharePoint content for years. If your organization relies on SharePoint Alerts to track document updates, list changes, or other site activities, it's time to start planning your transition strategy. Here's everything you need to know about the timeline, impact, and alternatives.

Why Is Microsoft Retiring SharePoint Alerts?

Microsoft's decision to retire SharePoint Alerts is part of their broader digital transformation strategy. As the company states, they're focused on delivering "modern, optimized, secure solutions" and believe customers will be "better served by modern notification solutions based upon the Power Automate platform or SharePoint Rules."

This move reflects Microsoft's commitment to consolidating features around their Power Platform ecosystem, providing more powerful and flexible automation capabilities than the legacy SharePoint Alerts system could offer.

The Retirement Timeline: What Happens When

Microsoft has laid out a detailed phase-out schedule that gives organizations over a year to prepare and migrate:

July 2025: New Tenants Affected First

Starting in July 2025, "the creation of new SharePoint Alerts will be gradually turned off for newly onboarding tenants." If your organization is new to Microsoft 365, you won't be able to create new SharePoint Alerts.

September 2025: All Tenants Lose Creation Ability

From September 2025, "the creation of new SharePoint Alerts will be gradually turned off for all tenants." This is when most organizations will first notice the change, as users will no longer be able to set up new alerts.

October 2025: Expiration Feature Kicks In

This is where things get more serious. Starting in October 2025, "any SharePoint Alert will have a validity of 30 days starting from its first run, then it will expire." Users can manually extend alerts for another 30 days, but this becomes an ongoing maintenance task.

July 2026: Complete Retirement

The final deadline arrives in July 2026, when "Microsoft will remove the ability to use SharePoint Alerts; existing SharePoint Alerts cannot be extended anymore and will not work anymore."

What Users Will Experience

Microsoft has designed the retirement process to be as transparent as possible:

Alert Creation Blocking: Users trying to create new alerts "will not be able to save the Alert plus they'll see a banner to make them aware of the SharePoint Alerts feature is retiring."

Email Notifications: Starting in October 2025, SharePoint Alert emails will include banners explaining the retirement and showing when specific alerts will expire.

Self-Service Extensions: Users can proactively extend their existing alerts or re-enable expired ones, but only for 30-day periods.

Recommended Alternatives

Microsoft is steering users toward two main replacement solutions:

Power Automate (Recommended Primary Option)

Power Automate offers significantly more flexibility than traditional SharePoint Alerts. You can:

1. Create complex conditional logic for notifications
2. Send notifications to multiple channels (email, Teams, mobile apps)
3. Integrate with other Microsoft 365 services
4. Set up automated workflows beyond just notifications

SharePoint Rules

For simpler notification needs, SharePoint Rules provide a lighter-weight alternative that can handle basic alert scenarios without the complexity of full Power Automate workflows.

What You Should Do Right Now

1. Assess Your Current Usage -
   Microsoft recommends that customers "run the Microsoft 365 Assessment tool to scan their tenants for SharePoint Alerts usage." This tool generates a Power BI report showing all SharePoint Alerts in your tenant, organized by site collection and web.
   
   
2. Update Training Materials - 
   Microsoft advises organizations to "update your user training content and prepare your help desk to support your organization with this retirement." Your support team needs to be ready to help users transition to new solutions.
   
   
3. Start Planning Your Migration Strategy - 
   Consider these factors when planning your transition:
• Volume: How many alerts does your organization currently use?
• Complexity: Are your current alerts simple notifications or do they serve more complex business processes?
• User Technical Skills: Can your users handle Power Automate, or do they need simpler SharePoint Rules?
• Timeline: Can you migrate everything before October 2025, or will you need to manage the 30-day extension process?
  
  
4. Begin Testing Alternatives - 
   Start experimenting with Power Automate and SharePoint Rules now. Create parallel systems for critical alerts to ensure the alternatives work as expected before you lose the original alerts.

Migration Strategies by Use Case

Simple File/Folder Change Notifications: SharePoint Rules can easily replace basic "notify me when this document changes" alerts.

Complex Business Processes: If your alerts are part of larger workflows (like approval processes), Power Automate is your best bet. It can handle multi-step processes, conditional logic, and integrations with other systems.

High-Volume Environments: For organizations with hundreds of alerts, consider creating standardized Power Automate templates that users can easily customize for their needs.

User-Managed vs. IT-Managed: Decide whether individual users will create their own Power Automate flows or if IT will create centralized solutions.

Key Considerations for IT Leaders

Training Requirements: Power Automate has a learning curve. Budget time and resources for user training, especially for users who currently rely heavily on SharePoint Alerts.

Governance: Power Automate is more powerful than SharePoint Alerts, which means you'll need governance policies around who can create flows and what they can do.

Licensing: While basic Power Automate functionality is included with most Microsoft 365 plans, advanced features may require additional licensing.

Support Model: Determine whether your help desk can support Power Automate issues or if you need specialized training.

The Bigger Picture

This retirement is part of Microsoft's broader platform consolidation strategy. Rather than maintaining separate, limited-functionality features like SharePoint Alerts, Microsoft is investing in comprehensive platforms like Power Automate that can handle simple notifications while also scaling to complex automation scenarios.

This approach aligns with the modern workplace trend toward low-code/no-code solutions that empower users to create their own business processes without heavy IT involvement.

Timeline for Action

• By September 2025: Complete your assessment and have a migration plan in place. Start creating replacement flows for critical alerts.
• By October 2025: Have most of your alerts migrated to avoid the ongoing 30-day extension management overhead.
• By July 2026: All alerts must be fully migrated to alternative solutions.

Getting Help

Microsoft offers several support options for this transition:

• The Microsoft 365 Assessment tool for analyzing current usage
• Power Automate reference samples (coming soon)
• Support tickets for technical assistance
• Partner programs for organizations needing migration help

Final Thoughts

While losing SharePoint Alerts might initially seem disruptive, this retirement actually presents an opportunity to modernize your notification and automation strategies. Power Automate and SharePoint Rules offer significantly more capabilities than the retiring alerts system.

The key to success is starting your planning now. With over a year until final retirement, organizations that begin preparing today will have plenty of time to create better, more powerful notification systems than what they're replacing. 

Don't wait until the last minute. Use the Microsoft 365 Assessment tool, start experimenting with Power Automate, and begin training your users on the new tools. Your future self (and your users) will thank you for making this transition proactively rather than reactively.

SharePoint Online Update: Major Changes to Custom Scripting and Classic Publishing Sites Coming September 2025

If you're managing SharePoint Online environments, there's a significant change on the horizon that you need to prepare for. Microsoft has announced important updates to custom scripting capabilities and Classic Publishing site creation that will take effect on September 15, 2025. Here's everything you need to know about these changes and how to prepare your organization.

What's Changing?

Microsoft is implementing three major changes that will fundamentally alter how custom scripting and Classic Publishing sites work in SharePoint Online.

1. Custom Scripting Gets Disabled by Default
   
   Starting September 15, 2025, custom scripting will be automatically disabled for several SharePoint Online templates. This means the DenyAddAndCustomizePages setting will be set to $true by default for:
   
   
• BLANKINTERNETCONTAINER#0 (Classic Publishing Portal Site)
• CMSPUBLISHING#0 (Classic Publishing Site)
• BLANKINTERNET#0 (Classic Publishing Site Blank)
• CSPCONTAINER#0 (SharePoint Embedded Site)
  
  This change is driven by security considerations around ungoverned scripting, as Microsoft continues to tighten security controls across its platform.


2. No More New Classic Publishing Sites
   
   Perhaps the most significant change is that users will no longer be able to create new Classic Publishing site collections or activate publishing features in existing sites. This restriction applies to both user interface interactions and API calls.
   
   The following templates will no longer be available for new site creation:
   
   
• Publishing Portal Site
• Publishing Site
• Publishing Site Blank
• Enterprise Wiki
• Enterprise Search Center
• Site Directory
• News Home Site
• Product Catalog
• Report Center
• Topic Area Template
  
  Important note: If you already have Classic Publishing sites, don't panic. Existing sites remain completely unaffected and can continue normal operations, including creating subsites.
  
  
3. Improved Property Bag Management
   
   There's some good news in these updates too. Microsoft has introduced a new feature that allows users to manage site property bag values without needing to enable custom scripting. The new

    AllowWebPropertyBagUpdateWhenDenyAddAndCustomizePagesIsEnabled  
   

   setting works at both tenant and site levels, making property bag management much more straightforward.

How This Impacts Your Organization

These changes will have different effects depending on how your organization currently uses SharePoint:

For Custom Scripting Users: 

When custom scripting is disabled, several features become unavailable:

1. Script editor web parts stop working
2. Custom master pages and page layouts can't be created or modified
3. Various other customization features are blocked

For SharePoint Administrators: 

You'll lose the ability to create new Classic Publishing site collections or enable publishing features at the site collection level through standard methods.

For End Users: 

The impact will primarily affect those who rely on custom scripts and Classic Publishing features for their daily work.

What You Need to Do Right Now

Microsoft recommends taking several proactive steps to prepare for these changes:

1. Communicate with Your Users
   Start informing owners of Classic Publishing sites about these upcoming changes immediately. This gives them time to plan and potentially migrate to Modern SharePoint sites, which Microsoft strongly recommends.
   
   
2. Consider Migration to Modern Sites
   Microsoft provides comprehensive guidance for modernizing SharePoint environments. Modern sites offer better performance, security, and user experience compared to Classic Publishing sites. Now is an excellent time to evaluate your current sites and plan migrations where appropriate.
   
   
3. Understand Your Temporary Options
   Microsoft has provided several PowerShell commands that offer temporary relief if you need more time:
   
   Delay enforcement for your entire tenant until March 15, 2026:
   

    Set-SPOTenant -DelayDenyAddAndCustomizePagesEnforcementOnClassicPublishingSites $true  

   Allow temporary custom scripting for a specific site (24-hour duration):
   

    Set-SPOSite <SiteURL> -DenyAddAndCustomizePages $false  

   Allow creation of new Classic Publishing sites (if absolutely necessary):
   

    Set-SPOTenant -AllowClassicPublishingSiteCreation $true  

   
   
4. Update Your Tools
   Make sure you're running the latest SharePoint Online Management Shell (version 16.0.26211.12010 or higher) to use these new commands.

The Bigger Picture

These changes are part of Microsoft's broader strategy to modernize SharePoint Online and enhance security. Classic Publishing sites were built for an earlier era of web development, and Modern SharePoint sites offer significant advantages:

1. Better mobile responsiveness
2. Improved performance and loading times
3. Enhanced security features
4. Better integration with Microsoft 365 services
5. More intuitive user interfaces

Planning Your Response

Here's a practical approach to handling these changes:

Short-term (Before September 2025):

1. Audit your current Classic Publishing sites
2. Identify which sites truly need custom scripting
3. Plan communications to affected users
4. Test Modern site alternatives for critical functionality

Medium-term (September 2025 - March 2026):

1. Use the temporary opt-out period to complete migrations
2. Train users on Modern SharePoint features
3. Update any automated processes that create Classic Publishing sites

Long-term (After March 2026):

1. Complete migration to Modern sites where possible
2. Maintain only essential Classic Publishing sites with proper governance
3. Regularly review and optimize your SharePoint environment

Final Thoughts

While these changes might seem disruptive, they represent Microsoft's commitment to providing a more secure and modern collaboration platform. The temporary opt-out options give organizations breathing room to plan and execute transitions thoughtfully.

The key is to start planning now rather than waiting until September. Use this time to evaluate your current SharePoint usage, communicate with stakeholders, and develop a migration strategy that works for your organization.

Remember, existing Classic Publishing sites will continue to work normally, so there's no immediate crisis. However, proactive planning will help ensure a smooth transition and might even lead to discovering better ways to accomplish your current tasks using Modern SharePoint features.

How to get started with Claude AI?

Until recently, I was like many of us here—using ChatGPT for everything. It was my daily productivity companion. But last week, I attended a free seminar from GrowthSchool, and it opened my eyes to another AI tool: Claude AI by Anthropic.

What is Claude AI?

Claude is a conversational AI assistant similar to ChatGPT but with a different approach and tone. It’s designed to help with:

• Writing and editing
  
• Summarizing long PDFs
  
• Brainstorming ideas
  
• Coding assistance

The tool is named after Claude Shannon, the father of information theory, and is built with a focus on safety and clarity in conversations.

How is it different from ChatGPT?

Here’s what I found interesting:

• Gentle and clarifying tone: Claude often asks clarifying questions before answering and responds carefully, which helps when you are structuring your thoughts.
  
• File upload even in the free version: You can upload PDFs and documents and ask it to summarize or extract insights without needing a paid plan.
  
• Great for reading and summarizing long documents: This is one area where Claude felt smoother compared to my experience with ChatGPT Free (which doesn’t allow file uploads).
  
• Different perspective: Using both Claude and ChatGPT together gives different angles when brainstorming content, strategies, or writing hooks.

Free Version Differences:

ChatGPT Free:

• Uses GPT-3.5 (GPT-4.0 available for limited use)
  
• No file upload in free plan
  
• Direct and flexible tone

Claude Free:

• Uses Claude 3 Haiku (lightweight model)
• Allows file uploads and chatting with documents
• Gentle, clarifying conversation style

How to get started with Claude AI?

If you want to try Claude AI, it’s simple:

• Go to claude.ai (the official website).
• Create a free account using your email.
• Start chatting or upload a PDF to experience how it handles document summarization and Q&A.
• Try using it side-by-side with ChatGPT for a week to see which tasks feel smoother on Claude.

Conclusion:

You don't necessarily need to choose one over the other. Many power users find that Claude and ChatGPT complement each other well:

• Use ChatGPT for quick answers, brainstorming, and when you need fast responses.
  
• Use Claude for complex analysis, creative work, research, and when you need more thoughtful, nuanced interactions.

Exploring Claude has been a small but valuable addition to my workflow, and it might be worth adding to yours too.

How to get CSV file content stored in SharePoint Online using Power Automate?

Issue:

Recently I was working with CSV file for automation process. The files were stored in SharePoint Online document library. I thought with “Get File Content” action, I will be able to get the CSV file content directly. But the issue was it was giving me outcome in some other format:

Analysis:

When you use “Get File Content” action with SharePoint online, this actually pass you the connect in Base64 string. To see the actual content, we need to convert the content from Base64string to string.

Solution:

To convert the content, I used a compose and in value, I passed below expression:

 base64tostring(outputs('Get_file_content')?['body']['$content'])  

Using this, I was able to see actual content of the file:

React Responsive Carousel auto play doesn't work in SPFx

Issue:

Recently, we were developing a carousal feature in SPFx webpart. We got react component code from UI Team which has used React Responsive Carousel with sample data, and it was working fine. We needed to make the carousal dynamic and fetch data from SharePoint list.

When we incorporated the changes, we faced a strange issue. When we provide the dynamic data, the carousal will load only last item and doesn’t rotate. But if we pass static data, it worked fine.

Analysis:

As the webpart working with static data, we were not sure it was issue from the component. It meant there was something missing from the implementation part. So we started looking in to online resources. One such link mentioned we needed to explicitly give the CSS path in the import as follow:

 import 'react-responsive-carousel/lib/styles/carousel.min.css'  

It didn’t change the output. So, we thought if dynamic loading might be causing the issue, then we can generate HTML first and directly pass it to the component. So, we changed our component code from below:

 public render(): React.ReactElement<IReactCarousalProps> {  
 const images = this.state.carousaldata;  
 return (  
 <div className='min-h-screen'>  
 <Carousel showArrows={true} showThumbs={true}>  
 {images.map((url, index) => {  
 <div key={index}>  
 <img src={url.name} />  
 </div>;  
 })}  
 </Carousel>  
 </div>  
 );  
 }  

And updated as below:

 public render(): React.ReactElement<IReactCarousalProps> {  
 var images = this.state.carousaldata;  
 var htmlBody = “”;  
 images.map((url, index) => {  
 htmlBody+=” <div key={index}><img src={url.name} /></div>”  
 })  
 return (  
 <div className='min-h-screen'>  
 <Carousel showArrows={true} showThumbs={true}>  
 {htmlBody}  
 </Carousel>  
 </div>  
 );  
 }  

But this completely hide the component and showcase nothing on the page (Though earlier code showcase at least last item😊). But this failure confirmed that fault is not within the implementation but is from component itself and after that we have gone through the repository issue and find out similar issue and found the resolution.

Resolution:

So, we found that it might be version issue. Many people have mentioned that downgrading the version to lower version (3.1.33) has resolved the issue for them.

But in one such comment we found that there is an alternative too. If the carousal is initialized with zero content, it will break. If it is initialized with proper data, it will work properly. So, the user has suggested that we need to check before binding component, it our data is not there, do not bind the component.

The sample code will look like:

 public render(): React.ReactElement<IReactCarousalProps> {  
 const images = this.state.carousaldata;  
 return (  
 <div className='min-h-screen'>  
 { images.length > 0 ? (  
 <Carousel showArrows={true} showThumbs={true}>  
 {images.map((url, index) => {  
 <div key={index}>  
 <img src={url.name} />  
 </div>;  
 })}  
 </Carousel>) : null}  
 </div>  
 );  
 }  

Though the user input was done on 2019, and the issue persist, I thought it would be helpful to someone with same issues.

References: 

1. React Responsive Carousel Sample - https://github.com/leandrowd/react-responsive-carousel
2. Issue resolution link - https://github.com/leandrowd/react-responsive-carousel/issues/321
3. CSS Reference - https://stackoverflow.com/questions/66554854/react-responsive-carousel-is-not-displaying-properly

How to back up Skype data?

As Microsoft has announced that Skype will be retiring in May 2025. This will impact free and paid skype users but not Skype for Business users.

Link - Skype is retiring in May 2025: What you need to know - Microsoft Support

So, with the end of Skype, Microsoft is asking you to use Teams for free with same credentials. You can start working with Teams with login into skype and clicking start using team:

But for future safety, we should keep our back up of files. To download all your shared files in Skype, you can visit below link:

https://go.skype.com/export

It will open new page where you have 2 options:

1. Conversations
2. File

You can select files or both and click submit request. Based on your data size the export will be available in .tar file.




This was quick blog about data backup. If you need any other details, you can visit below FAQ page link:

How do I export or delete my Skype data? - Microsoft Support

BaseDialog 'isBlocking' IDialogConfiguration override is not working.

Issue:

Recently, we were developing a SPFx webpart in which we needed to open a dialog. For that we decide to use Office Fabric UI Dialog control. For that we used this link as reference. The Microsoft blog explains the code well. We were able to open the dialog as expected. We needed one more functionality that if user clicks outside the dialog, it should not be closed.

For that we found we can set “IsBlocking” flag to true. We applied the code as mentioned below:

 export default class ColorPickerDialog extends BaseDialog {  
  public message: string;  
  public colorCode: IColor;  
  public render(): void {  
   ReactDOM.render(<ColorPickerDialogContent  
   close={ this.close }  
   message={ this.message }  
   defaultColor={ this.colorCode }  
   submit={ this._submit }  
   />, this.domElement);  
  }  
  public getConfig(): IDialogConfiguration {  
   return { isBlocking: false };  
  }  
  protected onAfterClose(): void {  
   super.onAfterClose();  
   // Clean up the element for the next dialog  
   ReactDOM.unmountComponentAtNode(this.domElement);  
  }  
  private _submit = (color: IColor) => {  
   this.colorCode = color;  
   this.close();  
  }  
 }  

But still, that does not work.

Analysis:

The blog was written in 2017. So, we thought with the updates in SPFx version, there might be change in the code. We tried to find online if we can get any updated code for the same. But we are not able to find it anywhere. So, we decide to put a query in GitHub for solution. We found an old issue there which provide us the resolution.

Resolution:

The issue was reported in Dec 2017 and was given resolution in Jan 2018. The code documented in the was missing the actual implementations for the “IsBlocking” flag. It needs to be passed when you call the dialog component as below:

 const dialog: ColorPickerDialog = new ColorPickerDialog({isBlocking: true});  

So, the full code for the button click will look something like below:

 @override  
 public onExecute(event: IListViewCommandSetExecuteEventParameters): void {  
  switch (event.itemId) {  
   case 'COMMAND_1':  
    Dialog.alert(`${this.properties.sampleTextOne}`);  
    // actual code provided in the code  
    //const dialog: ColorPickerDialog = new ColorPickerDialog();  
    //code that needs to be updated.  
    const dialog: ColorPickerDialog = new ColorPickerDialog({isBlocking: true});  
    dialog.message = 'Pick a color:';  
    // Use 'FFFFFF' as the default color for first usage  
    let defaultColor : IColor = { hex: 'FFFFFF', str: '', r: null, g: null, b: null, h: null, s: null, v: null };  
    dialog.colorCode = this._colorCode|| defaultColor;  
    dialog.show().then(() => {  
     this._colorCode = dialog.colorCode;  
     Dialog.alert(`Picked color: ${dialog.colorCode.hex}`);  
    });  
    break;  
   default:  
    throw new Error('Unknown command');  
  }  
 }  

You can remove getConfig() method from ColorPickerDialog class as it is of no use.

It has been 6 years since the posting of the issue and still the blog is not updated. There isn’t any other resource that mentioned this. So, I am writing this again to help anyone who is stuck in the issue.

References:

• https://learn.microsoft.com/en-us/sharepoint/dev/spfx/extensions/guidance/using-custom-dialogs-with-spfx
• https://github.com/SharePoint/sp-dev-docs/issues/1121