Latest / Microsoft Cloud IT Pro Podcast / Episode 331 – SharePoint 2013 Workflow retirement
Transcript
- 0:03Welcome to episode 331 of the Microsoft Cloud IT Pro
- 0:08podcast recorded live on April 21st, 2023.
- 0:12This is a show about Microsoft 365 and Azure from the perspective of it pros and
- 0:17end users where we discuss a topic or recent news and how it relates to you
- 0:21today,
- 0:22Ben and Scott go back to their SharePoint roots as they discuss the retirement
- 0:27of SharePoint 2013 workflows and SharePoint online,
- 0:30as well as the release of SharePoint Workflow manager to replace Microsoft
- 0:35Workflow Manager for SharePoint on-premises 2013 through SharePoint
- 0:40subscription edition.
- 0:43Did you watch the Starship launch? SpaceX's Starship?
- 0:48I watched the Starship have a sudden deconstruction event. The.
- 0:53Explosion when it started spinning out of control. Yes.
- 0:56Did you start watching it with the launch? The launch was impressive. I.
- 1:00Didn't watch the whole thing. I just watched the highlights.
- 1:02I think there's a couple videos out on YouTube,
- 1:04like this official SpaceX channel has one that's about an hour long.
- 1:08I think it's 52 53 minutes, something like that.
- 1:10Yeah, it is. And I watch it like the kids came in and watched it with me.
- 1:14It was, it was fascinating.
- 1:18It was way slower than I thought it would be. , because what,
- 1:22it's 33 engines, so the Falcon nine has the nine engines.
- 1:26Starship had 33 and I was talking to someone else about
- 1:31this and they,
- 1:33it's a slow liftoff because they slowly light all the engines.
- 1:37I don't want to ignite all 33 engines at once,
- 1:39so they like hold it down in the pad for longer while they slowly ignite all of
- 1:43'em and then they finally let it go. But I was sitting here watching it,
- 1:46I'm like, is it gonna go? Is it gonna go?
- 1:48And it was super slow to start going .
- 1:51It felt like this behemoth just, you slowly saw it start moving.
- 1:55Yeah, it's interesting. So it, it caused some damage to the pad.
- 2:00I mean like the thing's huge.
- 2:02It did. I was looking at the YouTube, like the crater,
- 2:04it literally made an like a new crater underneath the pad. Yeah.
- 2:08They also had a bunch of holding tanks.
- 2:10Looks like some of those got some pretty good dents in them like,
- 2:13like as whatever was,
- 2:15whatever pressurized gas was in them kind of suck things in almost like you get
- 2:19a dent on your car that you look like you could go back and pull out later.
- 2:22Uhhuh , but I mean these are massive holding tanks for, you know,
- 2:25whatever liquid nitrogen or, or you know, whatever gas they have in there.
- 2:29So yeah, it's impressive if you're into the space geek CRE thing,
- 2:34it's definitely, definitely worth catching up on if you haven't had a chance to,
- 2:38even if you just put it on in the background.
- 2:40It was the kids had fun watching it and the kids spotted right away too that
- 2:43something was wrong.
- 2:45Like it took off and it started going and they were saying everything was
- 2:48nominal looking great and then one of the kids was like, dad,
- 2:51is it supposed to be like upside down in the air? And it was like,
- 2:55I don't know if that's the camera angle.
- 2:56And then it was right set up and then it was upside down again and the kids were
- 3:00like, dad, I don't think it's supposed to be spinning like that. And then yeah,
- 3:04sure enough,
- 3:04a few minutes later there was no stage separation and everything went kalu.
- 3:09Yeah,
- 3:10I think the thing to keep in mind is the point of it was to see if they could
- 3:13get it off the ground and take off without destroying the entire pad.
- 3:18You know,
- 3:19it was never meant to go all the way to space or anything like that on that
- 3:22launch.
- 3:23So it really was a test and seeing what's viable and what they
- 3:28can learn from it.
- 3:29Kind of interesting that we have to blow things up at that scale to figure out
- 3:32what's gonna work and what's not gonna work and we can't just, you know,
- 3:35turn on one of these AI ml blah blah blah model things and have it figured out
- 3:40for us. But, uh, kind of fun that you get to see stuff blow up at that scale.
- 3:43Really fun for a pirates engineer.
- 3:46I was just disappointed at was down in Texas or over in Texas and that here in
- 3:49Florida so that I couldn't actually see it, but who knows,
- 3:53hopefully eventually maybe they'll launch them from Florida.
- 3:57I'm assuming that would be the goal eventually,
- 4:00but based on what it did to the launchpad,
- 4:01I don't know if they're gonna end up having to build new launchpads or how
- 4:04that's gonna work out,
- 4:05but it'll be interesting to watch as they continue on with it.
- 4:09Yeah, my understanding is the goal isn't necessarily to be able to launch from
- 4:13Florida. Like those likely always go from Texas and,
- 4:16and that from Texas facility. Okay. Because of the size of them. Like they're,
- 4:20there's a huge environmental impact and it's a real impact where it
- 4:25is now too.
- 4:26Like even the Texas facility is surrounded by protected lands and
- 4:31wildlife and all sorts of things that are being
- 4:36sacrificed along the way as well. So it,
- 4:39it's no good whether it launches from Texas or Florida, like really, or Florida.
- 4:43We shouldn't be launching it from the surface of the earth, but hey,
- 4:45that's where we are and what we've gotta do.
- 4:47With it's 10 million pounds of fuel. Yes.
- 4:51That was a number that blew me away when I heard that of like 10 million pounds
- 4:54of fu fuel. That is a lot of fuel. Yep.
- 4:58It's there. It's got it going on. So yeah, highly recommend anybody go watch it.
- 5:01Like I said, if you're th throw it up on the tv,
- 5:04like it's a good one to watch on like YouTube on your TV or if you can cast it
- 5:07over and just run the, you know,
- 5:10the 4K feed through and crank up the speakers.
- 5:13It's got some good rumble and things on it. Yes. Make.
- 5:15Sure you have a good sub too. Yeah, good subwoofer.
- 5:18Turn up the base and let it shake the house. .
- 5:22By the time it exploded though it was too far away that you're not gonna get any
- 5:25good audio from the explosion. It's gonna be the launch itself.
- 5:28Yes. I will put a link in the show notes to the
- 5:33official SpaceX YouTube channel where they've got it.
- 5:36You're gonna want to skip to about 44 minutes in if
- 5:41you're just looking for kind of lift off and not all the launch
- 5:46prep but other things that go with it.
- 5:48Yeah, definitely. So you know what else is happening Scott.
- 5:52What else is happening Ben.
- 5:54This is not happening today nor did it happen this week,
- 5:57although more news came out about it this week.
- 6:00I don't win know when all the blog posts were posted.
- 6:05Some of these were back in February 16.
- 6:07One of these I saw was by Laura Rogers just
- 6:12yesterday. But something near and dear to our hearts,
- 6:16Scott SharePoint 2013 workflows are
- 6:21being turned off for newly created tenants
- 6:26in Office 365 and this is happening on
- 6:30April 2nd, 2024.
- 6:32Apparently they did not want this to be on April 1st and people think it was an
- 6:35April Fool's joke maybe, I don't know.
- 6:38But April 2nd, 2024 SharePoint 2013 workflows will no longer
- 6:43be a thing in newly created tenants starting
- 6:46April 2nd, 2026.
- 6:49So you have some time here like three years timeframe. You.
- 6:53Have some time if you're in an existing tenant. If.
- 6:56You're in an existing tenant,
- 6:57that's when you're gonna just lose them all together in existing tenants.
- 7:02So three years from now, give or take a couple weeks,
- 7:07no more SharePoint 2013 workflows at all in any tenants in
- 7:12Microsoft 365.
- 7:13Yeah. I wonder if this changes you.
- 7:16We've talked a little bit in the past about merger and acquisition scenarios,
- 7:20particularly around tenants and merging tenants in SharePoint and Exchange and,
- 7:25and all these different things.
- 7:26I wonder if this impacts m and a at all in meaningful ways.
- 7:29Like if you acquire a company and you wanna spin up a whole new tenant to kind
- 7:34of converge everything in and now all of a sudden you're in a spot where oh you
- 7:38can't do that because you don't have this critical component that's in
- 7:42use.
- 7:43I think things like this always lead to interesting customer behaviors and that
- 7:47you have customers latch onto things like quote unquote legacy tenants, legacy,
- 7:51you know, big air quotes. Yeah.
- 7:53So that they can retain these features over time.
- 7:56It should be a fun one to watch but uh, it's time to migrate from your old,
- 8:01they would still be SharePoint designer workflows, right? Yes.
- 8:04Yeah, they are like this is one of those products.
- 8:07SharePoint Designer 2013 is the latest version of SharePoint
- 8:12Designer.
- 8:13I don't believe they ever did a SharePoint designer 2016
- 8:18or 2017 or anything after 2013.
- 8:21They just kind of kept extending the life of SharePoint designers so you could
- 8:26continue to run these workflows. I mean personally,
- 8:28I'm frankly I'm surprised it made it this long.
- 8:31Like you talk about mergers and acquisitions, you talk about people migrating,
- 8:36I mean all of my clients for quite a while now when they start talking
- 8:40about migrating to SharePoint online from SharePoint on premises,
- 8:45one of my questions is, do you have workflows And tell you what,
- 8:49let's not migrate those into SharePoint online.
- 8:52Let's actually rewrite them as power automate flows.
- 8:56And I've done a few of those where it's coming from SharePoint,
- 9:00whether it's a legacy or I don't know that I've actually done any like 2019
- 9:05to SharePoint online. Most of them are 20 13, 20 16 to SharePoint online.
- 9:09And it has been, let's break down these SharePoint designer workflows,
- 9:13let's rewrite them and power automate and go that way. And it's,
- 9:18it's interesting because there are definitely things you need to take into
- 9:22consideration when you start migrating these things that don't necessarily
- 9:28work in power Automate the same way they do in
- 9:32SharePoint Designer and even different ways like I think SharePoint Designer
- 9:37workflows, SharePoint workflows,
- 9:39you could do like a workflow that triggered another workflow. Um,
- 9:43power Automate that's not as easy to do. So again,
- 9:46just things you need to think about work through.
- 9:48So not something you necessarily wanna save until the last minute.
- 9:54If you do have a bunch of old SharePoint designer workflows running in your
- 9:58environment or I suppose you could write these in Visual Studio I suppose it's
- 10:03not just SharePoint Designer, right?
- 10:04You used to be able to crack open Visual Studio and actually compile these and
- 10:09write workflows that way. If I'm remembering right, yes.
- 10:12I used to make my living doing that it.
- 10:15It's something that can definitely be done.
- 10:19So this one's interesting in that there's not like a
- 10:24straight migration path like Microsoft doesn't have today
- 10:29unless I've completely missed it.
- 10:31Tooling to take a SharePoint 2013 workflow
- 10:36and migrate it over to something like Power Automate.
- 10:39Are you aware of anything that Microsoft has or are there
- 10:44ISVs that are filling this space?
- 10:45Is somebody maybe like Nitax coming in with their workflow engine and saying
- 10:49like, Hey we'll take your stuff on, come in, migrate to us and keep on running.
- 10:53I have not heard of anything like that.
- 10:57It wouldn't surprise me if maybe Nitax has something or some I S V has
- 11:02the ability, if you want to go from SharePoint,
- 11:05I dunno if we call 'em SharePoint classic, Microsoft tends to use SharePoint.
- 11:08Classic workflows like going to SharePoint classic workflows to Nitech would
- 11:14probably work.
- 11:15I don't know that any I S V has like use our tool
- 11:19as a proxy or a pass through to go from classic
- 11:24workflows to Power Automate.
- 11:26So it really is kind of a manual process if you're going from classic
- 11:31to power automate again there are others, there's nex, I'm trying to remember.
- 11:35I feel like there were a couple others and I can't remember what they are.
- 11:38NEX was always the big one.
- 11:40But even then I have not run across very many
- 11:44people that still do NEX with SharePoint online.
- 11:49I.
- 11:49Mean realtime follow up nex unveils workflow plan
- 11:54amid Microsoft retiring product.
- 11:57So they will offer a transition plan interesting including
- 12:02in gov clouds and dod. Oh which this stuff is very,
- 12:06is very prevalent over there. I can tell you that much. Yeah.
- 12:09And I wonder if that's why I don't encounter,
- 12:11I wonder if it's much more prevalent in some of those more regulated
- 12:15industries.
- 12:17I know for a long time power automate and power apps
- 12:22weren't even available in like Gov cloud and some of those.
- 12:26So I can see where yeah maybe you migrate some of these classic ones
- 12:31to nex or maybe there's people using NEX already in those and
- 12:36they're just gonna have to migrate some of these.
- 12:38The best thing I found in Microsoft,
- 12:40they do have an article here on guidance migrate from classic
- 12:45workflows to power automate flows and SharePoint and they
- 12:50walk through kind of how you should think about it,
- 12:53pain points you may encounter, modern approval stuff,
- 12:57authoring workflow concepts and how some of them
- 13:02are different for different, for example,
- 13:05something that causes your workflow to start in SharePoint workflow with start
- 13:09options and events, power automates triggers,
- 13:12both of 'em have ACT actions,
- 13:15things like conditions that are the same,
- 13:18but then different types of workflows, different SharePoint integrations,
- 13:22triggers, actions. It's quite an extensive list.
- 13:27Kind of more doing it compare and contrast in highlighting a few pain points
- 13:31that you may encounter as you start that transition from classic
- 13:36workflows to power automate flows, there's.
- 13:38Also some tooling out there.
- 13:39So Microsoft has the M 365 assessment tool that
- 13:44can kind of help you just figure out what's in use today
- 13:49because you, you might not know in your environment.
- 13:51So that's probably a good place for most customers to start is like what's the
- 13:55impact of this announcement on me? Do I have one of these?
- 13:58Do I have a thousand of these? Like what's going on? Where are they running?
- 14:02What sites site collections are they running in?
- 14:05And start to kind of wrap your head around just, you know,
- 14:09what's the blast radius for this announcement coming through so you can plan
- 14:12around it. Yeah.
- 14:13You mean there's people that have SharePoint environments that have no idea
- 14:15what's going on in it.
- 14:17isn't that like every SharePoint online administrator ,
- 14:21I dunno how anybody's keeping up with.
- 14:22SharePoint administrator anywhere.
- 14:26I think it was just as prevalent with SharePoint on-prem as it was with
- 14:29SharePoint online.
- 14:30Except there at least you had some control over like the WSPs and
- 14:35some of that maybe ish you're.
- 14:37Taking me back to the good old days when I used to maintain a code plex project
- 14:42for W S P extraction.
- 14:45I actually wrote one of those like it's like a WinForms app to go ahead and go
- 14:49into SharePoint farms and pull out WSPs from existing
- 14:54solutions that had been deployed and uh,
- 14:58yeah I used to be a developer in a past life .
- 15:00That was before we did this. I don't know that I ever put two and two together,
- 15:06although I don't know that I ever used your solution.
- 15:08I used a PowerShell script to extract WSPs from SharePoint on-prem.
- 15:12There was also a little PowerShell script out there that would do it.
- 15:15Yes. I used to deal with customers who, you know,
- 15:18didn't understand the complexities or want to run PowerShell so it was
- 15:24a nice little W S P downloader kind of thing. Got it.
- 15:28Yeah, I, excuse me,
- 15:31have very fond memories of pulling out WSPs before you do migrations.
- 15:35You could redeploy 'em or people that needed to rebuild a
- 15:40farm and didn't bother saving the WSPs and you needed
- 15:44to back them up somewhere.
- 15:47There was many a time I was extracting WSPs from SharePoint farms. Yeah.
- 15:53Oh it's a thing we used to do. Look at old days.
- 15:59Do you feel overwhelmed by trying to manage your Office 365 environment?
- 16:03Are you facing unexpected issues that disrupt your company's productivity?
- 16:07Intelligent is here to help much like you take your car to the mechanic that has
- 16:11specialized knowledge on how to best keep your car running Intelligent helps you
- 16:15with your Microsoft Cloud environment because that's their expertise.
- 16:18Intelligent keeps up with the latest updates in the Microsoft Cloud to help keep
- 16:22your business running smoothly and ahead of the curve.
- 16:25Whether you are a small organization with just a few users up to an organization
- 16:29of several thousand employees they want to partner with you to implement and
- 16:33administer your Microsoft Cloud technology,
- 16:37visit them at intelligent.com/podcast.
- 16:40That's I N T E L L I G I N
- 16:45k.com/podcast for more information or to schedule a 30 minute
- 16:50call to get started with them today.
- 16:52Remember Intelligent focuses on the Microsoft cloud so you can focus on your
- 16:57business.
- 17:00So along with SharePoint Farm,
- 17:02since we moved to SharePoint on-prem and WSPs and we're talking about
- 17:07workflows,
- 17:08there was also some guidance and this was a little bit older back
- 17:13in mid-February of this year.
- 17:15So about a month ago where there was an announcement from,
- 17:20it was on Steven Goner I think is how you pronounce his last name.
- 17:24His website Bill Bear also has like the official release
- 17:29announcement blog post of this is the release of SharePoint workflow manager
- 17:35for SharePoint Surfer and this is
- 17:40100% based on premises because
- 17:44obviously Power Automate can't run in on-premises
- 17:49farms cuz it's all cloud only.
- 17:51So you're still gonna have to support some form of workflows on-premises
- 17:56servers.
- 17:57So everything we just talked about around SharePoint designer
- 18:02workflows will still work as far as I can
- 18:07tell in SharePoint on premises.
- 18:09But the Microsoft workflow manager that we have known and loved and
- 18:14used alongside of Service Bus since the SharePoint
- 18:182013 days is going to go away
- 18:23on July 14th, 2026.
- 18:27So same rough three year-ish timeframe and be replaced
- 18:32with SharePoint Workflow Manager,
- 18:34a new workflow engine to Power SharePoint 2013
- 18:39workflows, 16 workflows 2019 workflows and SharePoint
- 18:44subscription edition workflows.
- 18:46All the workflows.
- 18:47All the workflows.
- 18:49I have my speculations on what this is,
- 18:53it doesn't say anywhere in here. I haven't seen any official documentation.
- 18:58My theory is is that they're kind of taking the micro soft workflow engine and
- 19:03service bus and kind of combining them into one product re-releasing as the
- 19:07SharePoint workflow manager.
- 19:08And this is gonna be maintained by the SharePoint team instead of
- 19:13Microsoft Workflow Manager,
- 19:14which could be used with SharePoint but was really a bigger Microsoft
- 19:19product that you could also use outside of it looks like maybe the
- 19:24SharePoint team has kind of taken this over similar to what happened with,
- 19:28is it distributed cash? One of those,
- 19:31there was another product that the SharePoint team was using that Microsoft
- 19:35discontinued but like the SharePoint team kind of picked it up and ran with it
- 19:39to keep it working in SharePoint. This feels very similar.
- 19:44Yes.
- 19:44So this one's not Service Bus at least going by the
- 19:49documentation so it can't be installed over the top of
- 19:54existing workflow manager. So workflow manager being service bus oriented,
- 19:59this one requires iass still but it also requires Azure
- 20:04Service Fabric and kind of the on-prem components of service fabric
- 20:09coming in.
- 20:09So it is a little bit of an underlying change but it gives
- 20:14you kind of warm fuzzies as you're moving forward.
- 20:18If you're still on prem today and you're running whatever version of SharePoint,
- 20:23like hopefully it's subscription edition,
- 20:25but if you're running subscription edition it gives you and and some of the
- 20:29older versions,
- 20:30it gives you that warm fuzzy about being able to move
- 20:34forward along the way.
- 20:36So I will put a link to the installation documentation
- 20:41in the show notes and everybody can go have a
- 20:46look at that.
- 20:47It's fairly comprehensive in what you need to do to potentially uninstall
- 20:53existing Microsoft Workflow Manager and then get the uh no,
- 20:58I'm sorry, existing what SharePoint Workflow manager and then get the new uh,
- 21:01workflow manager up and running.
- 21:03It doesn't help that one's Microsoft Workflow Manager and one SharePoint
- 21:06workflow manager like.
- 21:07Right, like you can't really just say workflow manager, it's both.
- 21:12I'm assuming, I was looking through some of this
- 21:18documentation.
- 21:20Is this set up and configure SharePoint Workflow Manager overview?
- 21:26I'm assuming you do still author these with SharePoint Designer? Yes.
- 21:31SharePoint Designer 2013 is a workflow authoring tool of
- 21:36choice for SharePoint workflows.
- 21:37Some advanced tasks require the intervention of a developer using Visual Studio.
- 21:43Yeah under the documentation for SharePoint workflow manager.
- 21:47It is still all Visual Studio in SharePoint Designer 2013.
- 21:51Yes,
- 21:51there's some underlying restrictions there like things have changed in the new
- 21:55workflow engines.
- 21:56So the setup account can't be used to create
- 22:01workflows which you shouldn't be doing anyway.
- 22:04I don't think that's too big a deal. S P D is still there and running I.
- 22:08Remember issues with triggering whenever you did it with that farm account or
- 22:12install account too. So anyways, sorry what else? No.
- 22:16I think that's the big one. So Azure Service Fabric is,
- 22:20it also requires that the SQL Server instance
- 22:25that hosts workflow manager databases,
- 22:28it does have to run the SQL browser service.
- 22:30So you know you might have restrictions or just kind of rules around whether you
- 22:35actually run the browser service within your org.
- 22:37Like it's a requirement for this.
- 22:39So maybe that kind of impacts topology or where you place it or or where it
- 22:44lives. But other than that it looks pretty
- 22:48straightforward along the way.
- 22:50Users that run workflows need to be in the user profile service and users that
- 22:54offer workflows like that all makes sense. Yeah. And then from there the,
- 22:59the tooling's the same.
- 23:00So if you haven't already just installed SharePoint Designer 2013 and go ahead
- 23:05and create a workflow based on the SharePoint 2013 workflow platform and you're
- 23:09up and running.
- 23:10Yeah, I wonder if SharePoint designers is ever gonna go away. one.
- 23:13Thinks it has to at some point but who, who really knows? You.
- 23:18Would think at this point in time though it's extended date has like its date
- 23:22keeps getting extended.
- 23:23It's extended end date is now 2026.
- 23:27So this now is up to a 13 year life cycle
- 23:32if you're gonna take extended support into account. It's interesting though,
- 23:37looking at the SharePoint designer lifecycle,
- 23:39that extended end date of July 14th, 2026 is the exact same
- 23:44date as the end date for Microsoft
- 23:49Workflow. I have no idea if anything new is coming or not,
- 23:53but interesting that they are the exact same date for that end of
- 23:58life. We'll see.
- 23:59Where it all goes.
- 24:00I think the other thing to remember is if you are an on-prem
- 24:04SharePoint customer today or maybe if you're a hybrid customer and
- 24:09you're kind of looking at what's going on on SharePoint in Office
- 24:13365 and the online versions of it versus what you're doing on-prem,
- 24:18like we talked about the whole transition from legacy workflows to Power
- 24:22automate earlier,
- 24:23you can run Power Automate on-prem as well but you're not really running it
- 24:27on-prem but you can integrate Power automate workflows into your power
- 24:32automate flows into your environment by using the on-prem data gateways
- 24:37and things like that.
- 24:38There might be licensing implications for you there like power apps Plan one
- 24:42licenses or higher.
- 24:44But uh yeah might be something that you want to take a look at.
- 24:48I think your decision is probably down to like the whole interactive versus non
- 24:52interactive workflow thing and what that's gonna look like for you.
- 24:56So I don't think Power Automate really works for like interactive workflows
- 25:00through a gateway like it's weird experience and pretty janky.
- 25:04You might just want to go with the older style workflow or I guess the older
- 25:08style workflow on the new workflow engine. They're making this really easy.
- 25:11Yeah and even if you're okay with data going up to the cloud, right,
- 25:16because if you start integrating Power Automate with SharePoint on-prem,
- 25:20I mean maybe you're still on-prem for licensing reasons but if you're on-prem
- 25:24for security reasons because you don't or you can't have your SharePoint data
- 25:29in the cloud,
- 25:30you probably don't want to integrate with Power Automate cuz it's gonna start
- 25:34sucking that data out of your on-premises environment into the cloud,
- 25:38run the workflow and maybe then shove it back into your on-premises environment.
- 25:41Yeah I think it's a niche thing, right?
- 25:42Like if you're a hybrid customer you meet the compliance,
- 25:46you know it's not gonna be something for regulated industry probably,
- 25:50but if you're somebody tinier it might be totally viable for you if anything
- 25:55cuz you don't have to train people on you know,
- 25:58two different tools versus just get me on the one stack and I'm kind of
- 26:02hopefully future-proofed for the foreseeable future.
- 26:05Yeah, I would be interested to hear from somebody doing this.
- 26:11I personally,
- 26:11I have not run into any customers using SharePoint
- 26:16on-prem and power automate or power apps in this
- 26:21hybrid type scenario. That data business data connector, that connection.
- 26:27I've seen it a little bit more from like a Power BI standpoint.
- 26:30They have a big data warehouse on premises,
- 26:32they don't want it migrate it up somewhere.
- 26:34They want to connect and do some reporting in their data on premises.
- 26:38I feel like most of the customers I've run into,
- 26:40if they're gonna be using Power automate and power apps,
- 26:42they're also just migrating up to SharePoint online.
- 26:45So if there is someone doing the whole, we have SharePoint on premises yet,
- 26:49but we're using power apps,
- 26:50power automate all these cloud tools for the data gateway,
- 26:53I would be really curious to know use case reasoning,
- 26:57like just learning about what those niche scenarios are
- 27:02that people find themselves in that situation.
- 27:04It would just be really interesting. Let me know cuz I'm curious. .
- 27:10You can hit Ben up on all the socials. Send 'em.
- 27:13An email. Yeah, go find me. Send me an email, send me a tweet,
- 27:16send me a what is it? If it's unmasked it on it's a toot. It's a toot.
- 27:21Yeah. See you asked but uh, you probably didn't want to know.
- 27:24I did not wanna know. I really don't want Toots being sent my way. .
- 27:28Yeah. Any who? Oh what else? Good stuff Scott.
- 27:32I learned a lot of good stuff this past week but I'm not allowed to talk about
- 27:35any of it. So sorry we sat down and I'm like,
- 27:38I don't know what to talk about cuz my brain's a whole jumble from this past
- 27:41week of NDA stuff. It.
- 27:42Took you what,
- 27:43less than a month to go around and start flaunting your MVP status.
- 27:47I see how it is. Yeah.
- 27:49See how that you just flaunt your Microsoft status.
- 27:51I don't have Microsoft status so I have to flut some status .
- 27:55Uh, I don't know that I flaunted, I I I live it day to day so I don't know.
- 27:59The struggle is real there sometimes. For sure.
- 28:02It is. I have found myself having to,
- 28:06every once in a while make sure I have the blog post or the public announcement
- 28:10in front of me so I know what's been talked about and what hasn't been. Yeah,
- 28:13it's, yeah, it's interesting. Any anywho anything else?
- 28:18Do you wanna talk about co-pilots? Nah.
- 28:20Co-pilots is probably gonna take us. Well why don't we do co-pilot next week?
- 28:24You said it not me. I did not do this. I did not commit.
- 28:29I want everybody to tweet Scott or Toot. Scott,
- 28:32do you wanna be tweeted or tooted? Um.
- 28:35, unlike you, I would prefer to be tooted.
- 28:37I don't support the lizard over Lord over on,
- 28:40over on the other platform that he burned to the ground.
- 28:43And remind him that he actually committed to something this week or next week
- 28:47and not me this time. Let's.
- 28:48Chat co-pilot next week.
- 28:49I think there's some interesting things there in the co-pilot service.
- 28:54Uh, I don't think we've talked about co-pilot Exia and we've got
- 28:59co-pilot coming to Viva, so come back next week to hear more.
- 29:02Yes, there are lots of co-pilots, lots of different places,
- 29:05so it will be interesting.
- 29:07I'm curious to learn more about your co-pilot thoughts next week. All right.
- 29:11Will do as always. Thanks Ben.
- 29:13All right, thanks Scott. We'll talk to you next week.
- 29:18If you enjoyed the podcast, go leave us a five star rating in iTunes.
- 29:21It helps to get the word out so more it pros can learn about Office 365 and
- 29:26Azure.
- 29:27If you have any questions you want us to address on the show or feedback about
- 29:31the show, feel free to reach out via our website, Twitter, or Facebook.
- 29:36Thanks again for listening and have a great day.