How to see late turn in info AFTER returning student work
As the title says. I recently returned some assignments and after doing so cannot now find out the turn in information anymore. It was really helpful to have a record of who turned in late but the insights wasn't giving me a summary of the student scores but did tell me how late the assignments were(It would not even tell me if they were late, everything just marked as returned). After returning them I get the scores but not how late they were. Is there a way to see both or should I just not return assignments?SharePoint Intranet Festival | May 21, 2025 | Virtual
Get ready for the second SharePoint Intranet Festival, taking place virtually on Wednesday, May 21, 2025. The event is produced by SWOOP Analytics and is packed with expert insights to support your employee engagement strategy and enterprise-wide communication efforts. What makes this event special? It’s grounded in real-world intranet use cases designed for all employees, not just head-office. You’ll hear directly from leading organizations like Citi, Comcast, Prologis, Syngenta, Bauer Media, VELUX, NRMA, AustralianSuper, and Services Australia, who will share practical experiences and outcomes. It’s a rich blend of perspectives from both the private and public sectors.
Migration from Workplace to Viva Engage
We are in the process of transitioning from Workplace to Viva Engage and have obtained JSON files from Workplace. How can we upload them while ensuring that all posts and pictures retain their original timestamps for a smooth migration experience for end users? Is there any documentation as how do we upload JSON to Microsoft sharepoint?Mastering Query Fields in Azure AI Document Intelligence with C#
Introduction Azure AI Document Intelligence simplifies document data extraction, with features like query fields enabling targeted data retrieval. However, using these features with the C# SDK can be tricky. This guide highlights a real-world issue, provides a corrected implementation, and shares best practices for efficient usage. Use case scenario During the cause of Azure AI Document Intelligence software engineering code tasks or review, many developers encountered an error while trying to extract fields like "FullName," "CompanyName," and "JobTitle" using `AnalyzeDocumentAsync`: The error might be similar to Inner Error: The parameter urlSource or base64Source is required. This is a challenge referred to as parameter errors and SDK changes. Most problematic code are looks like below in C#: BinaryData data = BinaryData.FromBytes(Content); var queryFields = new List<string> { "FullName", "CompanyName", "JobTitle" }; var operation = await client.AnalyzeDocumentAsync( WaitUntil.Completed, modelId, data, "1-2", queryFields: queryFields, features: new List<DocumentAnalysisFeature> { DocumentAnalysisFeature.QueryFields } ); One of the reasons this failed was that the developer was using `Azure.AI.DocumentIntelligence v1.0.0`, where `base64Source` and `urlSource` must be handled internally. Because the older examples using `AnalyzeDocumentContent` no longer apply and leading to errors. Practical Solution Using AnalyzeDocumentOptions. Alternative Method using manual JSON Payload. Using AnalyzeDocumentOptions The correct method involves using AnalyzeDocumentOptions, which streamlines the request construction using the below steps: Prepare the document content: BinaryData data = BinaryData.FromBytes(Content); reate AnalyzeDocumentOptions: var analyzeOptions = new AnalyzeDocumentOptions(modelId, data) { Pages = "1-2", Features = { DocumentAnalysisFeature.QueryFields }, QueryFields = { "FullName", "CompanyName", "JobTitle" } }; - `modelId`: Your trained model’s ID. - `Pages`: Specify pages to analyze (e.g., "1-2"). - `Features`: Enable `QueryFields`. - `QueryFields`: Define which fields to extract. Run the analysis: Operation<AnalyzeResult> operation = await client.AnalyzeDocumentAsync( WaitUntil.Completed, analyzeOptions ); AnalyzeResult result = operation.Value; The reason this works: The SDK manages `base64Source` automatically. This approach matches the latest SDK standards. It results in cleaner, more maintainable code. Alternative method using manual JSON payload For advanced use cases where more control over the request is needed, you can manually create the JSON payload. For an example: var queriesPayload = new { queryFields = new[] { new { key = "FullName" }, new { key = "CompanyName" }, new { key = "JobTitle" } } }; string jsonPayload = JsonSerializer.Serialize(queriesPayload); BinaryData requestData = BinaryData.FromString(jsonPayload); var operation = await client.AnalyzeDocumentAsync( WaitUntil.Completed, modelId, requestData, "1-2", features: new List<DocumentAnalysisFeature> { DocumentAnalysisFeature.QueryFields } ); When to use the above: Custom request formats Non-standard data source integration Key points to remember Breaking changes exist between preview versions and v1.0.0 by checking the SDK version. Prefer `AnalyzeDocumentOptions` for simpler, error-free integration by using built-In classes. Ensure your content is wrapped in `BinaryData` or use a direct URL for correct document input: Conclusion In this article, we have seen how you can use AnalyzeDocumentOptions to significantly improves how you integrate query fields with Azure AI Document Intelligence in C#. It ensures your solution is up-to-date, readable, and more reliable. Staying aware of SDK updates and evolving best practices will help you unlock deeper insights from your documents effortlessly. Reference Official AnalyzeDocumentAsync Documentation. Official Azure SDK documentation. Azure Document Intelligence C# SDK support add-on query field.
Where do I find the messages I sent through "Share to Outlook from Teams"
On 3/20 I forwarded a chat message to several people using the "Share to Outlook from Teams" feature available in the horizontal ellipse menu for that message. Today I was going through my notes and realized I never received a response from the person the message was directed to so I looked in my Outlook Sent box for the message to follow up on it. It was not there. Even more confusing, there is no indication in Teams that the message was sent. Embarrassingly I had to ask one of the "Cc" recipients to forward it back to me so I could follow up with the "To" person I needed to. This confirms the message did go out. Just to make sure this wasn't a one-time thing my buddy used the "Share to Outlook from Teams" feature on a Teams conversation we had. I received his email, and just like me he had no trace the message was sent. Where do you go to find your messages sent through the "Share to Outlook from Teams" feature?
Viva Amplify not allowing approvals
Hi there We are pilot testing Viva Amplify in our tenant and we are finding an issue when trying to send a campaign publication for approval. We are getting an error anytime we try to send something for approval from newly created campaigns. Campaigns that were created a month or so ago are not having this issue. Has anyone run into this and is there a simple setting to update? Thanks for the help. Error:Take these steps to enable your Firstline Workers today
Now more than ever, are we dependent on the heroes on the ground to keep our world moving, and we wanted to provide some tips to help scale Firstline Worker operations. Check out ways you can digitize environments for Firstline Workers, while maximizing on safety and wellbeing.5 ways to evolve your Firstline Workforce for the new normal
As organizations continue to refocus their operations to support and empower employees while maintaining business continuity, we have been working to create and improve capabilities in Microsoft Teams to support their efforts. These capabilities help you to better connect the Firstline Workforce with your corporate offices, digitize manual processes, equip them with the right devices and, accelerate their onboarding, all on a foundation of security that you expect from Microsoft 365.
Unable to resolve - A vulnerability assessment solution should be enabled on your virtual machines
We currently have a mix of approximately 45 Windows / Linux Servers and AVD machines which are not successfully being marked as compliant with the Defender recommendation "A vulnerability assessment solution should be enabled on your virtual machines". On the subscription level we have Defender for Servers Plan 2 enabled and Agentless Scanning CSPM enabled. Within a subscription some of the of these VMs are compliant and others are not. Their compliance state doesn't appear to have any relevance to if the Qualys or MDE extensions are installed. We have servers that are healthy that have Qualys, MDE, or none installed and are healthy. Our VMs are not using the full feature set of Defender Plan 2 as we use CrowdStrike so the Defender for Endpoint functionality of the Defender for Servers Plan 2 has been disabled, but to my knowledge this shouldn't impact Vulnerability assessments. In Security Portal it does seem that generally all the VMs that healthy for this recommendation are visible in the devices section. Whereas these 45 that are not, are either not searchable or have sensor health state "inactive". We have an Azure Policy generated to onboard devices to Vulnerability assessment using MDE.Tvm and it seems to be generally working but not for these 45 devices. The Microsoft Documentation is really unclear, what do we need to make these systems compliant?
