Author: rory-admin

Social engineering scams on Facebook, LinkedIn and Twitter are increasing: what to look out for
Some fraudsters have abandoned the awkward, obvious emails of the past decade in favor of a new gambit, this one focus on social media. Today, they operate where your business already lives: in your LinkedIn inbox, your Facebook admin panel, and your Twitter DMs. The scams are polished, convincing, and growing fast.

Social engineering attacks rely on manipulation rather than malware. Instead of breaking through your firewall, criminals exploit the one vulnerability no software patch can fix: human trust. In 2024 and into 2025, that manipulation has migrated aggressively onto social media platforms, targeting professionals, business owners, and marketing teams who use these networks as core business tools.

Understanding how these scams are constructed is the first line of defense. Here is a closer look at what is circulating on each major platform and what warning signs to watch for.

LinkedIn: fake job offers and recruiter impersonation

First, The fake job offer scam.One of the fastest-growing threat vectors on LinkedIn involves fraudulent job opportunities delivered via connection requests and direct messages. Attackers create convincing recruiter profiles, complete with employment histories, endorsements, and professional headshots, before reaching out to targets with lucrative-sounding roles at legitimate companies.

Once contact is established, the “recruiter” moves the conversation off-platform to WhatsApp or email and eventually asks for sensitive information under the guise of onboarding: copies of identification documents, bank account details for direct deposit setup, or payment for background checks and equipment deposits. In some cases, victims are sent fraudulent checks and asked to forward a portion of the funds before the check bounces.

Luckily there are a few common red flags you can look for to spot this one, such as:
- The recruiter’s profile was created recently and has few connections or activity.
- The job offer arrives unsolicited with an unusually high salary and vague responsibilities.
Also, a more targeted variant involves attackers creating near-duplicate profiles of a company’s senior executives or trusted colleagues. The impersonator connects with employees and then requests urgent wire transfers, gift card purchases, or credential resets, exploiting the authority of the mimicked identity. Because the message arrives through LinkedIn rather than email, many recipients lower their guard.

LinkedIn has acknowledged the scale of fake profile activity on its platform and introduced detection tools, but sophisticated actors continue to slip through. Treat any out-of-character financial or credential request from a connection with immediate skepticism, regardless of how authentic the profile appears.

Facebook: business account threats and fake admin messages

Businesses running Facebook Pages and advertising accounts have become prime targets for a scam that impersonates Meta support. The attack typically begins with a message, often arriving via Messenger or a business inbox, warning that the page violates community standards and faces imminent suspension. Targets are urged to click a link and “verify” their account to avoid action.

Those links lead to convincing phishing pages that harvest Facebook credentials, two-factor authentication codes, and in some cases payment information linked to the ad account. Once attackers gain access, they drain advertising budgets, lock out legitimate admins, or sell the established account to other bad actors.

Common red flags for this one are:
- Urgent language around page violations sent through Messenger rather than through Meta’s official support system.
- Links that route to domains that are not facebook.com or meta.com.
A related tactic involves fraudulent invitations to become a page or group administrator. Business owners receive what appears to be a legitimate Facebook notification asking them to accept an admin role for a page they do not recognize. Accepting grants the attacker reciprocal admin access to the victim’s own pages by exploiting Facebook’s cross-admin trust structure. The scammer can then post spam, remove the original owner, or use the page for further fraud.

Meta will never request login credentials or payment information through Messenger. Any urgent policy warning that arrives as a direct message, rather than through the official Meta Business Suite notification system, should be treated as fraudulent until verified directly through Meta’s help center.

Twitter (X): impersonation, verification badge scams, and crypto fraud

Since the overhaul of the platform’s verification program, bad actors have exploited user confusion around the blue checkmark by sending direct messages claiming the recipient’s account requires action to maintain its verified status or avoid suspension. These messages direct targets to external sites that steal credentials or payment details.

A parallel scam targets business accounts with messages purporting to be from the platform’s trust and safety team, warning of copyright violations or policy breaches and requesting immediate login through a provided link. The urgency and official-sounding language make these messages disproportionately effective against small business owners managing their own accounts.

Again, common red flags are:
- Direct messages claiming to be from platform support, since X does not use DMs for official account actions
- Requests to “re-verify” through a third-party link rather than within the native app settings
Also, we want to be clear, do not overlook email: phishing remains the dominant threat and it’s also always constantly evolving.

While social media scams command growing attention, it would be a significant mistake to treat email phishing as a solved problem. Email-based attacks remain by far the most prevalent form of social engineering, accounting for the majority of successful business data breaches year after year. Modern phishing emails have evolved far beyond the broken-English missives of the early 2000s: today’s attempts accurately mimic bank correspondence, software license renewal notices, internal HR communications, and delivery notifications, often using the target’s actual name, employer, and recent activity pulled from public or previously compromised data.

Business email compromise, a targeted phishing variant in which attackers impersonate executives or vendors to authorize fraudulent payments, cost U.S. businesses billions of dollars annually. The threat is consistent, scalable, and disproportionately effective against organizations that have not established clear verification procedures for financial requests.

Staff who know to question a suspicious LinkedIn message may still instinctively trust an email that appears to come from their bank or their own CEO. Awareness training must address both channels with equal rigor.

A local managed service provider like Valley Techlogic is your first line of defense.

Recognizing individual scam tactics is valuable, but the threat landscape shifts faster than most business owners can track. A local managed service provider like us brings dedicated security expertise, advanced email filtering and phishing simulation tools, and ongoing employee awareness training that keeps your team current with the latest social engineering techniques crossing every channel, from LinkedIn inboxes to email spoofing campaigns. We can also establish clear internal protocols for verifying unusual requests, configure multi-factor authentication across your accounts, and monitor for credential exposure before attackers can exploit it. Partnering with a trusted local provider means that when the next convincing scam lands in your inbox or your social feed, your business has both the technology and the training to recognize it before it does damage. Learn more today with a consultation.
- Five IT questions your MSP should be able to answer TODAY, and what it means if they can’t
- First Meta and then Claude, what does it mean when AI language models are leaked online
- Microsoft 365, Google Workspace and.. Apple Business ? What is Apple’s new entry into enterprise software and what does it mean for your business
- So long Sora, ChatGPT pulls the plug on AI video generation platform amidst a $1 billion dollar pull out by Disney
April 24, 2026
Five IT questions your MSP should be able to answer TODAY, and what it means if they can’t
Your managed service provider (or tech person) is supposed to be the safety net between your business and disaster. They monitor your systems, manage your backups, and promise to keep things running when everything else goes sideways. But how do you know they can actually deliver on that promise? The answer starts with five straightforward questions about business continuity. If your MSP stumbles on any of them, it is time to pay attention.

Question One: “What is our current recovery time objective, and how was it determined?”

Every business has a threshold for how long it can survive without its critical systems. That threshold is your recovery time. A capable MSP will not only know an estimate of your recovery time off the top of their head but will also be able to walk you through how they arrived at that number. It should reflect conversations about your` customer commitments, your compliance requirements, and the operational realities of your environment.

If your MSP gives you a blank stare or quotes a generic number that sounds like it came from a boilerplate contract, that is a problem. Your recovery time should be as specific to your business as your business plan. A provider who cannot articulate it has not done the foundational work required to actually protect you.

Question Two: “When was our disaster recovery plan last tested, and what were the results?”

A disaster recovery plan that has never been tested is not a plan. It is a guess. Testing reveals the gaps that documentation alone cannot uncover: the backup that restores slowly, the dependency nobody remembered, the credential that expired six months ago. Your MSP should be running tabletop exercises and full restoration tests on a regular cadence, and they should have documented results they can share with you.

If the last test was “a while ago” or “we have not gotten around to it,” you are operating on hope. Hope is not a business continuity strategy. A mature MSP treats testing as a recurring discipline, not a checkbox they tick once during onboarding.

Question Three: “If our primary systems went down right now, what is the exact sequence of events that follows?”

This question tests whether your MSP has a real, rehearsed incident response workflow or just a vague sense of what they would probably do. The answer should be specific. You want to hear about alerting protocols, escalation paths, communication plans for your team, the order in which systems get restored, and who is responsible for each step.

Vague answers like “we would get on it right away” or “our team would jump in” are not reassuring. They suggest a reactive culture rather than a prepared one. In a genuine outage, clarity and speed come from preparation. Every minute spent figuring out what to do next is a minute your business is losing money and trust.

The difference between a four-hour outage and a four-day outage often comes down to whether someone had to improvise or simply had to execute.

Question Four: “Where are our backups stored, and are they protected from the same threats as our primary environment?”

Backups that live in the same environment as your production systems are vulnerable to the same failures. A ransomware attack that encrypts your servers can just as easily encrypt your backups if they are sitting on the same network. Your MSP should be able to explain a layered backup strategy that includes offsite or cloud-based copies, immutable storage options, and air-gapped protections for your most critical data.

If your provider cannot clearly explain where your backups live, how they are isolated, and how often their integrity is verified, you are carrying more risk than you realize. This is not a technical footnote. It is the difference between recovering from an incident and starting over from scratch.

Question Five: “How do you ensure our business continuity plan evolves as our business changes?”

Businesses are not static. You add new applications, migrate workloads to the cloud, open new locations, onboard remote employees, and shift priorities quarter to quarter. Your continuity plan needs to keep pace with all of that. A strong MSP builds regular reviews into the relationship, reassessing your risk profile, updating recovery procedures, and adjusting priorities as your infrastructure and operations evolve.

If your MSP set up a plan two years ago and has not revisited it since, the plan is probably protecting a version of your business that no longer exists. Continuity planning is a living process, and a provider who treats it as a one-time project is not truly invested in your resilience.

Here are some warning signs your MSP (or tech person):

•             They cannot produce documentation for your disaster recovery plan on request

•             Backup reports are not shared with you proactively or on a regular schedule

•             You have never been invited to participate in a recovery test or tabletop exercise

•             Your last business continuity review predates a major change in your infrastructure

•             Incident response feels improvised rather than rehearsed when issues arise

•             They deflect technical questions with jargon instead of clear, direct answers

These five questions are not designed to be gotchas. They represent the bare minimum of what a competent managed service provider should know about your environment and your risk posture. The answers reveal whether your MSP is a genuine partner in protecting your business or simply a vendor collecting a monthly fee.

If your provider cannot answer these questions confidently and specifically, it’s time to find one that can. One that will have a serious conversation about expectations, accountability, and what business continuity actually looks like in practice. Your business deserves a partner who is ready before disaster strikes, not one who starts preparing after it does. Valley Techlogic can be that partner, learn more today.
- First Meta and then Claude, what does it mean when AI language models are leaked online
This article was powered by Valley Techlogic, leading provider of trouble free IT services for businesses in California including Merced, Fresno, Stockton & More. You can find more information at https://www.valleytechlogic.com/ or on Facebook at https://www.facebook.com/valleytechlogic/ . Follow us on X at https://x.com/valleytechlogic and LinkedIn at https://www.linkedin.com/company/valley-techlogic-inc/.
April 17, 2026
First Meta and then Claude, what does it mean when AI language models are leaked online
If you’ve paid attention to the news lately, you may have noticed some headlines around AI code leaks and it’s only going to get worse.

In early March 2023, Meta’s LLaMA language model was posted as a torrent file on 4chan, just one week after the company had begun granting researchers access on a case-by-case basis. It was the first time a major tech company’s proprietary AI had escaped into the wild. Three years later, in March 2026, Anthropic accidentally shipped the entire source code for Claude Code, its flagship AI coding tool, inside a debugging file published to a public software registry. Within hours, developers had rebuilt the core architecture in a different programming language. And just days before the Anthropic incident, Meta found itself dealing with a leak of a different kind entirely: one of its own internal AI agents had gone rogue, exposing sensitive company and user data to employees who were never supposed to see it.

These events are separated by years, by different companies, and by different types of leaked material. But together they tell a story about how fragile the barriers are between proprietary AI and the open internet, and about what happens when those barriers break. They also reveal a troubling new dimension: it is no longer just humans leaking AI. Now AI is leaking data too.

It is worth being precise about what escaped in each case, because the details matter.

Meta’s LLaMA leak in 2023 involved the model weights themselves. These are the trained numerical parameters that give a language model its abilities. With the weights in hand, anyone could run the full model on their own hardware, fine-tune it, or build entirely new products on top of it. Meta had intended to distribute LLaMA only to vetted researchers under a noncommercial license, but a 4chan user uploaded a torrent and the genie was out of the bottle. Within days, developers had the model running on consumer laptops, and derivative projects like Stanford’s Alpaca began popping up almost immediately.

Anthropic’s Claude Code leak in 2026 was a different animal. The model weights for Claude were not exposed. Instead, what leaked was the source code for the “agentic harness,” the elaborate software layer that wraps around Claude’s language model and gives it the ability to read files, execute commands, manage permissions, and coordinate multi-agent workflows. Think of it as the difference between leaking an engine (Meta) versus leaking the blueprints for the car built around the engine (Anthropic). Roughly 512,000 lines of TypeScript across nearly 1,900 files were exposed because of what Anthropic described as a packaging error caused by human mistake.”

Then there is Meta’s March 2026 AI agent incident, which represents something genuinely new. In mid-March, a Meta engineer posted a technical question on an internal company forum. Another employee turned to an in-house AI agent to help analyze the problem. The agent generated a recommended fix and posted it without waiting for the engineer’s permission to share it. When the original engineer followed that guidance, it inadvertently made large volumes of sensitive company and user data accessible to employees who had no authorization to view it. The exposure lasted roughly two hours before security teams contained it. Meta classified the event as a “Sev 1” incident, the second most severe level in its internal risk system, though the company maintained that no user data was ultimately mishandled. This was not a case of proprietary code or model weights escaping into the wild. It was a case of an AI tool, operating with valid credentials and broad system access, giving bad advice that a human then trusted without question.

The immediate concern with any AI leak is competition. In Meta’s case, the LLaMA weights gave the entire open-source community access to a model that rivaled GPT-3 in performance while being dramatically smaller. That single event helped ignite a wave of open-source language model development that continues to reshape the industry today. Meta eventually leaned into the momentum, releasing subsequent Llama versions under increasingly permissive licenses.

The Claude Code leak carries a different kind of competitive risk. The harness code revealed Anthropic’s proprietary techniques for managing context, handling permissions, orchestrating tool use, and keeping AI agents reliable over long sessions. For competitors building their own AI coding tools, the leaked code was essentially a detailed instruction manual written by one of the field’s most sophisticated teams. Some analysts described it as the most detailed public documentation ever available for building a production-grade AI agent.

Beyond competition, these leaks raise serious questions about security. The Claude Code leak exposed the exact logic behind the tool’s permission system and safety guardrails. Security researchers have noted that this knowledge could allow bad actors to craft targeted attacks against previously unknown vulnerabilities. When you know precisely how a lock works, picking it becomes much easier.

Meta’s AI agent incident introduces an even more unsettling concern. Security researchers describe what happened as a “confused deputy” problem, where a trusted system misuses its own authority. The AI agent had legitimate credentials and system access. It did not need to break through any security perimeter because it was already inside. When it generated flawed guidance and an employee followed it, the result was a data exposure that traditional identity and authentication controls never flagged. As companies deploy AI agents with increasingly broad permissions across their internal systems, the potential for a single bad instruction to cascade into a large-scale exposure grows dramatically.

Reports suggest that roughly 80 percent of organizations using AI agents have already observed them performing unauthorized actions, including accessing and sharing sensitive information. The Meta incident was not an edge case. It was a preview of a systemic problem.

What makes these leaks particularly striking is how mundane their causes were. Meta’s LLaMA weights leaked because the company’s access controls were loose enough that someone with researcher credentials could share the files freely. Anthropic’s source code leaked because a debugging file was accidentally included in a routine software update. Meta’s 2026 AI agent incident happened because an employee asked a question and a colleague let an AI tool answer it. Neither event involved a sophisticated hack or a disgruntled insider stealing secrets in the dead of night. They were, in the most deflating possible sense, ordinary mistakes, or in the case of the AI agent, ordinary trust placed in a tool that was not ready for it.

This points to a structural tension in how the AI industry operates. These companies are simultaneously trying to move at breakneck speed, ship products to millions of users, publish to public software registries, collaborate with external researchers, and maintain airtight control over their most valuable intellectual property. Something is bound to slip through the cracks, and it has, repeatedly.

Anthropic’s Claude Code leak was actually its second major data exposure in under a week. Days earlier, a draft blog post describing an unreleased model called Mythos had been discovered in a publicly accessible data cache, revealing details about capabilities that the company had not yet announced. The pattern suggests that as AI companies scale faster, the surface area for accidental exposure grows alongside them.

These leaks collectively reinforce a few emerging realities about the AI landscape.

First, the moat around proprietary AI is thinner than many investors and executives would like to believe. When a developer can rebuild leaked architecture overnight in a different programming language, it suggests that the real value in AI products may not sit where people assume it does. The models and the code are important, but they may be less defensible than the data, the distribution, and the speed of iteration that surround them.

Second, the open-source AI ecosystem is a force that grows stronger with every leak and every intentional release. The original LLaMA leak helped catalyze a movement that has since produced models competitive with the best proprietary offerings. By early 2026, open-weight models from multiple labs were matching or exceeding proprietary systems on standard benchmarks, at a fraction of the cost. Each leak adds fuel to an already roaring fire.

Third, safety and security conversations need to catch up with the pace of deployment. If the detailed inner workings of AI safety systems can leak through a packaging error, the industry needs to think harder about defense in depth. Security through obscurity has never been a reliable strategy, and AI tools with millions of users are high-value targets for anyone looking for weaknesses to exploit.

Fourth, the Meta AI agent incident signals that leaks are no longer exclusively a human problem. As organizations hand AI agents valid credentials and broad system access, they are creating a new category of insider risk. These agents can retrieve, surface, and redistribute sensitive information at machine speed, and they do not pause to consider whether their actions violate access policies. Governing AI agents with the same rigor applied to human employees, including role-based access controls enforced at the output level and mandatory human review before sensitive actions are taken, is quickly becoming a requirement rather than a best practice.

The AI industry is unlikely to stop leaking. The combination of rapid development cycles, massive codebases, public distribution channels, and intense competitive pressure creates an environment where accidental exposure is almost inevitable. The question is not whether more leaks will happen, but how companies and the broader ecosystem will respond when they do.

For AI companies, the lesson is that anything shipped externally should be treated as potentially public. For researchers and developers, each leak offers a window into how the most advanced AI systems actually work under the hood. And for everyone else, these events are a reminder that the AI tools shaping our world are built by humans, distributed through human systems, and subject to very human mistakes.

The walls around AI are not as high as they look from the outside. And every time one cracks, the landscape shifts a little further toward openness, whether anyone planned for it or not.

If your company is utilizing AI tools (which we do recommend) the first thing you need to address is guidelines for how it accesses your data, just like with Microsoft, you should consider any data you share with AI and within your company from a “shared responsibility” perspective. This means that your most sensitive data (think passwords, payment information etc) is kept under lock and key and the data you do wish to give AI access to has been properly evaluated and sanitized. Data hygiene should be the first step to any AI readiness plan and Valley Techlogic can assist with that planning. Learn more today with a consultation.
- Government backed cybersecurity agency CISA down to just 38% of its optimal staffing levels after funding cuts, what it means for your business
This article was powered by Valley Techlogic, leading provider of trouble free IT services for businesses in California including Merced, Fresno, Stockton & More. You can find more information at https://www.valleytechlogic.com/ or on Facebook at https://www.facebook.com/valleytechlogic/ . Follow us on X at https://x.com/valleytechlogic and LinkedIn at https://www.linkedin.com/company/valley-techlogic-inc/.
April 10, 2026
Microsoft 365, Google Workspace and.. Apple Business ? What is Apple’s new entry into enterprise software and what does it mean for your business
For years, the enterprise productivity conversation has been a two-horse race. You either ran your business on Microsoft 365 or you went with Google Workspace. Sure, there were niche players and industry-specific platforms, but when it came to the core suite of tools that kept your team communicating, collaborating, and managed, it was Microsoft or Google, full stop. That just changed.

On March 24, 2026, Apple announced Apple Business, a unified platform that rolls device management, business email with custom domains, calendar services, a company directory, and customer-facing brand tools into a single portal. It launches April 14, 2026, in over 200 countries. And here is the part that should really get your attention: the core platform is free.

Let’s break down what this means, what it includes, what it costs, and why your MSP partner should already be thinking about how it fits into your environment.

So, what exactly is Apple Business? Apple Business is the consolidation of three previously separate platforms: Apple Business Manager (device enrollment and app distribution), Apple Business Essentials (device management for small businesses), and Apple Business Connect (brand presence across Apple Maps and other services). Instead of juggling three portals with overlapping features and confusing boundaries, businesses now get one unified dashboard.
The platform is organized around two core pillars: Run and Grow.

Run is the IT and operations side. This is where you manage devices, deploy apps, configure security settings, and handle employee onboarding. The headline feature here is called Blueprints, which allows administrators to preconfigure device settings, apps, and security policies so that a new iPhone, iPad, or Mac is ready to go the moment an employee powers it on. Apple calls this “zero-touch deployment,” and if you have ever spent an afternoon manually setting up a batch of company phones, you already understand the appeal.

Built-in mobile device management (MDM) gives IT teams a single view of every Apple device in the organization, along with the ability to create user groups, assign roles, and distribute apps. For companies that previously needed a third-party MDM solution just to manage a handful of iPads, this is a significant shift. Apple has also included Managed Apple Accounts with cryptographic separation between personal and work data, so employees can use one device for both without the two worlds bleeding into each other. Account provisioning integrates with identity providers like Microsoft Entra ID and Google Workspace, which means Apple is not asking you to abandon your existing identity infrastructure.

The platform also introduces integrated email, calendar, and directory services. Businesses can bring their own custom domain or purchase one directly through Apple Business. Calendar delegation, a built-in company directory with personalized contact cards, and user groups round out the collaboration toolset. This is the piece that moves Apple Business from “device management tool” into territory that starts to overlap with what Microsoft 365 and Google Workspace offer.

Grow is the customer-facing side. This is where Apple gets creative. Businesses can manage how their brand appears across Apple Maps, Mail, Wallet, and Siri. Think customizable place cards in Maps with photos, hours, and action buttons for ordering or reservations. Branded communications in the Mail app. Custom Tap to Pay branding when customers pay with their iPhone. Location insights that show how customers discover and interact with your business. And coming this summer, businesses will be able to purchase advertising directly within Apple Maps to appear in search results.

So, you may be wondering, how does pricing work? This is where Apple Business gets genuinely interesting from a cost perspective.

The core platform is free. Device management, Blueprints, zero-touch deployment, email and calendar services, brand management tools, and the full Run and Grow feature set all come at no additional charge. Every user gets 5GB of iCloud storage included.

The paid add-ons are straightforward. Additional iCloud storage is available up to 2TB per user, starting at $0.99 per user per month in the US. If you want dedicated device support, AppleCare+ for Business starts at $6.99 per month per device or $13.99 per month per user (covering up to three devices).

To put this in context, here is how the base costs compare to the competition:
• Apple Business: Free for core features. Storage upgrades from $0.99/user/month. AppleCare+ from $6.99/device/month.
• Microsoft 365 Business Basic: $6.00/user/month. Includes Teams, SharePoint, OneDrive (1TB), and web versions of Office apps.
• Google Workspace Business Starter: $7.20/user/month. Includes Gmail, Drive (30GB), Meet, and the full Google Docs suite.

The comparison is not perfectly apples-to-apples (no pun intended). Microsoft 365 and Google Workspace include full productivity suites with word processing, spreadsheets, and presentation tools. Apple Business does not include equivalents to Word, Excel, Sheets, or Slides. If your team relies on those tools daily, you are still going to need a Microsoft or Google subscription alongside Apple Business.

However, for businesses that primarily need device management, business email, and basic collaboration, Apple Business at zero cost is a compelling proposition, especially for small and mid-sized organizations that were previously paying $2.99 to $24.99 per user per month for Apple Business Essentials.

If your organization runs on Microsoft 365 or Google Workspace today, Apple Business is not going to replace either of those platforms overnight. The productivity suite gap is too significant. You are not going to write proposals in Apple Business or build financial models there.

What Apple Business does change is the device management and identity layer. If your company issues iPhones, iPads, or Macs to employees, you may have been paying for a third-party MDM solution like Jamf, Mosyle, or Microsoft Intune to manage those devices. Apple is now offering that capability for free, built directly into the platform, with tighter integration than any third party can achieve.

For organizations with a mixed environment, the most likely scenario is a layered approach: Microsoft 365 or Google Workspace for productivity and collaboration, and Apple Business for device management, deployment, and the customer-facing brand tools that neither Microsoft nor Google offer.

The identity provider integration is key here. Because Apple Business works with Microsoft Entra ID and Google Workspace for account provisioning, it is designed to complement your existing stack rather than compete with it head-on.

What does this mean for your business? Small businesses stand to benefit the most from this announcement. If you are a company with 5 to 50 employees, all using iPhones and Macs, Apple Business gives you enterprise-grade device management, business email with your own domain, and a professional brand presence across Apple’s ecosystem for free. That is a package that would have cost hundreds of dollars per month just a year ago.

The zero-touch deployment feature alone could save hours of IT setup time per device. For a 20-person company that refreshes devices every three years, that adds up to meaningful labor savings on every cycle.

If you are a business owner or IT decision-maker, here are the questions worth discussing with your MSP:
• Is your current MDM redundant? If you are paying for a third-party MDM primarily to manage Apple devices, Apple Business may eliminate that cost entirely. However, if your MDM also manages Windows or Android devices, you will still need it for those platforms.
• Does your team need a full productivity suite? Apple Business does not replace Word, Excel, or Google Docs. If those tools are central to your workflow, Apple Business is an addition to your stack, not a replacement.
• Are you taking advantage of the brand tools? The Grow side of Apple Business is genuinely unique. Neither Microsoft nor Google offers anything comparable for managing your business presence across a consumer ecosystem. If your customers find you through Maps, pay with Apple Pay, or interact with your brand through Mail or Wallet, these tools are worth exploring.
• What does your device lifecycle look like? Zero-touch deployment through Apple Business requires devices purchased through Apple or Apple Authorized Resellers. If your company buys devices through other channels, you may not get the full benefit of Blueprints.

Apple Business is not a Microsoft 365 killer or a Google Workspace replacement. It is something different: a free, unified platform that makes managing Apple devices dramatically simpler while giving businesses tools to control their brand presence across Apple’s ecosystem. The fact that it includes business email and calendar services at no cost is a nice bonus, even if those tools are not as mature as what Microsoft and Google offer.

For an MSP like us, this is an opportunity to help our clients optimize their tech stack. Some will save money by dropping third-party MDM tools. Some will layer Apple Business underneath their existing Microsoft or Google environment for a more streamlined device management experience. And some small businesses that were cobbling together free tools and manual processes will finally have a professional, unified platform without the monthly subscription cost. In the world of business software, more options is a good thing.

Have questions about how Apple Business fits into your current IT environment? Reach out to our team for a complimentary assessment. We will help you understand where Apple Business adds value, where your existing tools still matter, and how to build a technology stack that works for your business without paying for overlap.
- So long Sora, ChatGPT pulls the plug on AI video generation platform amidst a $1 billion dollar pull out by Disney
- Anthropic’s AI product Claude experienced a surge in new subscribers after they told the government “no” to removing safeguards, a new look at AI ethics
- Government backed cybersecurity agency CISA down to just 38% of its optimal staffing levels after funding cuts, what it means for your business
- Cloud Waste and Other Technology Spending Snafu’s That Could Be Keeping Your Tech Spending Skyhigh
This article was powered by Valley Techlogic, leading provider of trouble free IT services for businesses in California including Merced, Fresno, Stockton & More. You can find more information at https://www.valleytechlogic.com/ or on Facebook at https://www.facebook.com/valleytechlogic/ . Follow us on X at https://x.com/valleytechlogic and LinkedIn at https://www.linkedin.com/company/valley-techlogic-inc/.
April 3, 2026
So long Sora, ChatGPT pulls the plug on AI video generation platform amidst a $1 billion dollar pull out by Disney
Yesterday, OpenAI officially pulled the plug on Sora, its AI video generation platform that launched to enormous fanfare just six months ago. The standalone app, the API, and all video generation features within ChatGPT are being shut down. At the same time, the billion-dollar licensing partnership with Disney has been dissolved. It is a dramatic reversal for a product that once topped the App Store charts and seemed poised to reshape digital content creation.

Meanwhile, on the other side of the world, ByteDance’s Seedance 2.0 continues to push the boundaries of what AI video can do. The contrast between these two trajectories tells us a great deal about the current state of AI, the pressures shaping the industry, and what businesses should be thinking about as they plan their technology strategies.

OpenAI’s Sora debuted its second-generation model in September 2025 with a dedicated consumer app that combined AI video creation with a social media feed for sharing content. The results were impressive. Downloads surpassed one million within ten days, outpacing even ChatGPT’s early adoption curve. The app quickly became the top free download in the App Store’s Photo and Video category.

But that momentum did not last. By January 2026, downloads had dropped by roughly 45%. Users experimented with the novelty, generated a wave of viral clips featuring copyrighted characters and public figures, and then largely moved on. The app generated only about $2.1 million in in-app purchases over its lifetime, a negligible figure for a company valued at $730 billion. More critically, Sora was consuming enormous amounts of computing power at a time when OpenAI is under pressure to consolidate resources ahead of an expected IPO and intensifying competition from rivals like Anthropic and Google.

An OpenAI spokesperson explained the decision by saying the company is narrowing its focus and redirecting compute toward robotics research and its core text and reasoning products. CEO Sam Altman reportedly told employees that ending Sora would free up resources for the company’s next-generation AI models. The message here is clear: when the runway is long but the burn rate is high, experiments that are not gaining traction get cut.

While Sora exits the stage, ByteDance’s Seedance 2.0 remains very much alive. Released in February 2026, the model quickly drew global attention for producing cinematic-quality video with synchronized audio from simple text and image prompts. Clips featuring hyperrealistic depictions of celebrities and well-known characters went viral almost immediately, prompting cease-and-desist letters from Disney, Paramount, Netflix, and Warner Bros., along with sharp criticism from SAG-AFTRA.

ByteDance responded by pledging to strengthen its intellectual property safeguards and suspending a controversial feature that could clone a person’s voice from a single photograph. The company also paused the planned global launch of Seedance 2.0 through its CapCut platform while it works through copyright compliance issues. Despite these setbacks, the underlying model continues to operate within China’s domestic ecosystem.

For users outside of China, accessing Seedance 2.0 is not straightforward. The full-featured version of the model is currently available only through ByteDance’s Chinese apps, including Jimeng and Doubao, which require a mainland Chinese phone number for registration. International users looking to try the model have been turning to VPN workarounds, typically setting their location to Hong Kong or mainland China and navigating Chinese-language interfaces. Some third-party platforms and API aggregators have also offered access, though availability has been inconsistent as ByteDance tightens controls. The international version of ByteDance’s creative platform, Dreamina, offers a limited version but has not yet rolled out full Seedance 2.0 capabilities to the general public.

One factor that may help explain why Seedance continues to thrive while Sora folds is the dramatically different public sentiment toward AI in China compared to the West. Multiple large-scale surveys conducted in 2024 and 2025 paint a consistent picture: Chinese citizens are far more accepting of and optimistic about artificial intelligence than their counterparts in North America and Europe.

Stanford’s 2025 AI Index Report found that 83% of people in China believe AI products and services offer more benefits than drawbacks. Compare that to just 39% in the United States and 40% in Canada. An Edelman survey from late 2025 reported that 87% of Chinese respondents said they trust AI, versus 32% in the U.S. and 36% in the U.K. A joint study by the University of Melbourne and KPMG, which surveyed over 48,000 people across 47 countries, found that 93% of employees in China are using AI for their work, far outpacing the global average of 58%. The same study noted that 54% of Chinese respondents actively embrace greater use of AI, compared to just 17% of Americans.

This cultural receptivity creates a very different operating environment for AI companies. In the United States, Sora was met with sustained backlash over deepfakes, copyright infringement, and the potential displacement of creative workers. Hollywood unions, family estates of public figures, and advocacy groups all pushed back forcefully. In China, while there are certainly regulatory constraints and some public concerns around privacy and consent, the broader population views AI development as a national priority and a source of opportunity rather than a threat. That kind of public goodwill gives companies like ByteDance more room to iterate, experiment, and build a user base for products like Seedance without facing the same intensity of cultural resistance.

At Valley Techlogic, we want to make sure these developments are on your radar. Here is what we think matters most:
- AI video tools are not going away. Sora’s shutdown does not signal the end of AI-generated video. It signals that the market is maturing and consolidating. The technology is real, and competitors from China and elsewhere are advancing rapidly.
- Copyright and compliance risks remain front and center. Both Sora and Seedance ran into serious intellectual property disputes. Any business exploring AI-generated content needs clear policies, legal review, and an understanding of where generated material comes from.
- VPN-dependent tools carry their own risks. If members of your team are experimenting with Seedance or similar tools through VPN workarounds, be aware of the security, compliance, and data privacy implications. Routing traffic through unfamiliar networks and registering on foreign platforms introduces risk that should be managed deliberately.
- Compute costs drive real business decisions. OpenAI shut down a product used by millions because the computing costs could not be justified. This is a reminder that AI infrastructure is expensive, and the tools you rely on today may not be available tomorrow if the economics do not work out (or they may become dramatically more expensive).
- Stay informed, stay cautious. The AI landscape is shifting fast. We recommend evaluating any AI tools your organization adopts with an eye toward longevity, data handling practices, and vendor stability.
The divergent paths of Sora and Seedance illustrate how quickly the AI industry is evolving. A product can go from record-breaking downloads to discontinuation in under a year. Meanwhile, cultural attitudes toward AI vary so dramatically across borders that a tool deemed too controversial in one market can find a welcoming audience in another.

For businesses, the lesson is not to chase every new AI tool that generates headlines. It is to build a thoughtful technology strategy with trusted partners who can help you navigate the noise, manage risk, and adopt the tools that will genuinely move your operations forward.

If you have questions about how any of these developments affect your organization, or if you want to talk through your AI adoption roadmap, we are here to help. Schedule a consultation today.
Cloud Waste and Other Technology Spending Snafu’s That Could Be Keeping Your Tech Spending Skyhigh
Anthropic’s AI product Claude experienced a surge in new subscribers after they told the government “no” to removing safeguards, a new look at AI ethics
Government backed cybersecurity agency CISA down to just 38% of its optimal staffing levels after funding cuts, what it means for your business

This article was powered by Valley Techlogic, leading provider of trouble free IT services for businesses in California including Merced, Fresno, Stockton & More. You can find more information at https://www.valleytechlogic.com/ or on Facebook at https://www.facebook.com/valleytechlogic/ . Follow us on X at https://x.com/valleytechlogic and LinkedIn at https://www.linkedin.com/company/valley-techlogic-inc/.

March 27, 2026

When most business owners think about security risks, they picture hackers, ransomware, or phishing emails. Those threats are real. But in many small and midsize businesses, the biggest exposure is much closer to home.

It is the former employee whose access was never fully removed.

Improper offboarding is one of the most common and most expensive security gaps we see at Valley Techlogic. A user account left active, a shared password that never changed, or a mobile device that still syncs company email can quietly create major risk months after someone leaves. If your offboarding process is informal or inconsistent, now is the time to fix it.

Why past employees are a real security risk

Most former staff are not malicious. The risk usually comes from oversight, not intent. However, the impact can be just as damaging.

Here is what commonly goes wrong:

Email accounts remain active and continue receiving sensitive information
Microsoft 365 or Google Workspace access is never fully revoked
Saved credentials remain on personal or unmanaged devices
Shared passwords are not rotated after departure
VPN or remote access tools stay enabled
File ownership and permissions are never reassigned

For IT staff and security teams, this is basic hygiene. But in the real world, especially in small business environments, offboarding often happens in a rush. HR processes the paperwork, IT is notified late or not at all, and access cleanup becomes partial at best. You only need one missed system to create a problem.

Many organizations assume that if the employee was trustworthy, there is little to worry about. That is a dangerous assumption. Former employee risk shows up in these five ways:

Data exposure Old accounts can still access client files, financial records, and internal communications.
Compliance violations For regulated industries, failure to revoke access can create audit findings or legal exposure.
License waste From a Microsoft 365 CSP perspective, which we deal with daily, inactive users often continue consuming paid licenses long after departure.
Operational confusion Emails, approvals, and system alerts may continue routing to someone who no longer works for you. The longer an account stays active, the more expensive the cleanup becomes.
Your offboarding checklist that actually works If you want an offboarding process that holds up under real world pressure, it needs to be standardized and repeatable. This is the baseline we recommend to clients across California.

Remediating these issues is as simple as a step by step process outlined below:

Identity and access

Disable the user in Entra ID or your directory immediately
Revoke all active sessions and tokens
Remove MFA methods tied to personal devices
Remove group memberships and admin roles
Convert mailbox or archive as needed

Email and collaboration

Set mailbox forwarding if business continuity requires it
Assign mailbox and OneDrive ownership
Remove from Teams, SharePoint, and distribution lists
Review inbox rules and external forwarding

Devices and endpoints

Collect company owned hardware
Remove device from Intune or MDM
Wipe or reset as appropriate
Verify no unmanaged personal devices retain access

Network and remote access

Disable VPN accounts
Remove remote management tools
Rotate any shared credentials
Review firewall and WiFi access lists

Licensing and billing

Remove or reassign Microsoft 365 licenses
Validate billing alignment in CSP or direct
Document the change for audit trail

If this feels like a lot, that is because it is. Mature environments automate most of this.

Timing matters more than you think

One of the biggest mistakes we see is delay. Offboarding should begin the moment HR confirms separation, not days later.

Best practice is:

Immediate access disable as soon as termination discussions are over
Same day device and license review
24 hour validation sweep across key systems

In environments using Entra ID, Conditional Access, and centralized device management, this can be largely automated. In fragmented environments, it becomes manual and error prone. This is where many SMBs get into trouble.

How to future proof your offboarding process

If you want this to stop being a fire drill every time someone leaves, focus on three structural improvements.

First, centralize identity. The more systems tied to Entra ID or your primary directory, the easier clean removal becomes.
Second, automate wherever possible. PowerShell, Graph automation, and lifecycle workflows dramatically reduce human error. This is exactly why many MSPs, including Valley Techlogic deployments, invest heavily in standardized offboarding runbooks.
Third, require HR and IT alignment. Offboarding failures are often communication failures. A simple, enforced workflow between departments eliminates most risk.

The bottom line is cybersecurity is not only about stopping outside attackers. It is about maintaining control of your own environment. A single overlooked account from a past employee can quietly undermine your security, your compliance posture, and your licensing costs. If your offboarding process lives in a checklist on someone’s desktop or depends on memory, it is time to tighten it up.

At Valley Techlogic, we help organizations across California turn offboarding into a controlled, repeatable process that closes risk instead of creating it. If you are not completely confident in your current process, now is the right time to review it. Learn more today through a consultation.