Thanks so much for responding!
Please forgive me for any typos in advance. I am preparing this response on my cell phone.image
First, let me say for the record, sounds like you are doing well with your project for a non-techny. So enjoy your digital growth. Thank you lol! :-)
Second, I haven't explored with Dynamics 365 recently, but I think my responses will be helpful and hope to put your mind at ease.
Q1: UPDATE DEPT IN D365
Please clarify that you created a Dyn365 app in the E3 Developer Sandox. Apologies, I don't really know what this means.
When you stated, you added users or updated users' details, are you using existing users that came with the E3 Developer Sandbox?
BE CAREFUL not to appear as if you are not designing, testing or developing which may caused MS to terminate your E3 developer PLAYGROUND. This is the bit that concerns me - I don't know what constitutes 'designing', 'testing' or 'developing'. I can tell you what I have done and maybe you can advise if it would satisfy the required activities: 1. Set up the sandbox and have the users that came with that 2. Haven't activated the sample data (Teams messages, emails etc) so I still need to do that - not sure if this would count 3. Added more detail to active users such as Job Title, Location etc. 4. Set up various Teams channels.
I will test if I can change the dept in the Admin. Center for my E3 Dev Sandbox tenant. With that being said, the response from the above user, may be absolutely correct about using Power Shell to make changes. I strongly suggest that you forward the article to your company's IT System Administrator. Unfortunately, I am my company's 'IT administrator'! I know slightly more about MS365 Admin Centre than MS Dynamics, but not much more, so I've really not got anyone to go to and I felt Power Shell is something I should avoid. When I was in the corp world, I worked closely with an IT System Admin. In all other organisations I always make a point of connecting with the team who manage the MS365 tenant when I'm joining a new Programme and setting up PMOs requiring SharePoints and Teams sites. I Do Not recommend you exploring with Power Shell if you are not with app and commands.
Q2. E3 DEVELOPER SANDBOX
Well, I can say you completed a thorough investigation on the service guidelines.Grinning. You are becoming an IT professional slowly but surely. Ha ha! Bit of a research/gather as much info as I can person - I'm a blue personality type, what can I tell you!
Again, if you created the Dyn365 app on the E3 dev Sandbox I really apologise but again, honestly, don't know what that means - I did get the E3 Developer licence and set up the sandbox so hopefully this is what you mean, you should be ok to an extend. I do remember reaching a limit of custom apps that I could create. I believe the limit was 5. And what happens then - would it just run on forever after that or would you need to delete one of the apps and develop a different one to keep the licence going? I'd be happy once I've gotten going a bit more, to be able to set up a chat bot or something like that but, it would all be v v new to me but I'm always happy to have a crack at things which have lowish chance of ruining things in a major way (unlike me messing with Power Shell!).
I downloaded the sandbox in December 2019 and still active today. But I use it for testing and training purposes almost daily. So I receive a quarterly renewal status by email from MS. For you, I recommend logging in and "do something" to keep your status active. You can design or run a report, add / remove columns, whatever relates to what your we're originally building. This is really helpful - this is what I've been doing - like adding detail for my active users, setting up Teams and so on - this quarter I can apply the sample data and hopefully, those kinds of activities will stick. I'm setting up a reminder every 3 months to go in and do something - although at a certain point it will settle into a more steady state scenario - then, I'd just be recording training and the odd bit of changes maybe to user details or whatever, so I'd still (it sounds like) possibly have to go in and do some other stuff like we mentioned about, as well, to keep meeting the reqs.
Remember MS wants to ensure you are not using the free sandbox to run your company. No, definitely not - I've got MS Business Standard as my company's system of choice, too used to using it, training on MS365 etc to use anything else!
Logging In:
I log into E3 dev app as Adele Vance (one of the given users) with onmicrosoft.com email. I have only 2 custom users in the Sandbox. I've not tried logging in as someone else.... I need to find and follow the instructions (I've got them somewhere) on how to make everyone have the same password so that's another task I can do to get my "she's using it!!" activity points! So I am little concern of your status since you had to log in using your org's credentials. I suggest sending an email or calling MS for.status clarity. I will see if I can raise a ticket via my MS Business Standard account as not sure otherwise how to obtain help from MS on this other than through that route but will see what I can do.
As before, a massive, super big thank you to you for your incredibly comprehensive reply - apologies if your thumbs are now suffering from RSI having tapped that all out on a phone!! What a trooper.